Working its way up from the back of the class: #15,426 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
52/ 100
D
Moving up: up 551 places this week.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is My Rust Devblog 133 Server on Version 1051.72 based in?
No region is published for My Rust Devblog 133 Server on Version 1051.72. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 45.187.111.216:28015.
How dependable is My Rust Devblog 133 Server on Version 1051.72, and is it online at the moment?
At this moment, My Rust Devblog 133 Server on Version 1051.72 is offline; the last time it was seen was 15 days 8 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 13 October 2026.
On what Rust version does My Rust Devblog 133 Server on Version 1051.72 sit?
Rust network protocol 1806 on Windows is what My Rust Devblog 133 Server on Version 1051.72 runs. To join, your game must use the same protocol; Steam handles the update.
Resets
When does My Rust Devblog 133 Server on Version 1051.72 wipe, and how often?
My Rust Devblog 133 Server on Version 1051.72 has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC.
Population
What position does My Rust Devblog 133 Server on Version 1051.72 hold in the rankings?
In the top 71% of all ranked servers, My Rust Devblog 133 Server on Version 1051.72 sits at #15,426 for player hours over the last seven days.
What does the population on My Rust Devblog 133 Server on Version 1051.72 look like?
It has been 15 days 8 hours since My Rust Devblog 133 Server on Version 1051.72 was last seen, and it is offline right now.
Lists and filters
What do My Rust Devblog 133 Server on Version 1051.72's tags stand for?
mp1 (Max players): Its slot count is 1; v1806 (Protocol): To get in, your game needs to be on the same version: the protocol is 1806; oxide (Oxide): Oxide (uMod) provides the plugin framework here; modded (Modded): The game is changed by plugins or settings; you will find it under Modded; h815a96ff (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one are the tags My Rust Devblog 133 Server on Version 1051.72 publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature My Rust Devblog 133 Server on Version 1051.72?
Rust Server Score lists that include My Rust Devblog 133 Server on Version 1051.72: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded.
Server rules
What settings and rules apply on My Rust Devblog 133 Server on Version 1051.72?
Nothing in the name of My Rust Devblog 133 Server on Version 1051.72 states a gather rate. It publishes no limit on group size. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. VAC, Valve's anti-cheat, is not enabled.
My Rust Devblog 133 Server on Version 1051.72 runs which map?
A procedural map, generated by the game, is what My Rust Devblog 133 Server on Version 1051.72 runs.
Getting in
How do you get onto My Rust Devblog 133 Server on Version 1051.72?
Enter client.connect 45.187.111.216:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asoxide,modded,mp1,v1806,h815a96ff
Game
mp1
Max playersIts slot count is 1.
v1806
ProtocolTo get in, your game needs to be on the same version: the protocol is 1806.
Mods and access
oxide
OxideOxide (uMod) provides the plugin framework here.
modded
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Other
h815a96ff
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).