Working its way up from the back of the class: #15,347 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
50/ 100
D
Holding steady: down 117 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.
AveragePeakWipe
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 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····WW
·W·····
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap1.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Tue 29 SepSun 27 SepSat 26 Sep
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 29 Sep, 11:00 UTC29d ago
0
–
running
0
Sun 27 Sep, 14:27 UTC31d ago
0
–
1.9 days
0
Sat 26 Sep, 13:24 UTC32d ago
0
–
1 days
0
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
You'll find no region listed by Server_217_DevBlog. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 212.110.152.61:28015 is the address to use.
How dependable is Server_217_DevBlog, and is it online at the moment?
The server is down: Server_217_DevBlog is offline now, with the last sighting 8 days 21 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 26 September 2026.
What Rust version is Server_217_DevBlog on?
The server Server_217_DevBlog is on Rust network protocol 2183 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does Server_217_DevBlog reset?
No next wipe can be predicted for Server_217_DevBlog, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 29 days 21 hours have passed since this world was made.
What happens on Server_217_DevBlog when wipe day arrives?
Recent wipes have peaked at 0 players on average. The crowd on the latest wipe was largest 0 hours after it began.
Player count
Where does Server_217_DevBlog sit among Rust servers?
Over the last seven days, Server_217_DevBlog has #15,347 for player hours, in the top 70% of all ranked servers.
What does the population on Server_217_DevBlog look like?
The last sighting of Server_217_DevBlog was 8 days 21 hours ago, and it is offline right now.
Tags
How should you read the tags on Server_217_DevBlog?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): 10 slots are available; v2183 (Protocol): Join only if your game runs protocol 2183; oxide (Oxide): The plugin framework in use is Oxide (uMod); modded (Modded): Plugins or settings alter the game, so it sits under Modded; h5e7466bf (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one; stok (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one are the tags Server_217_DevBlog 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 Server_217_DevBlog?
These Rust Server Score lists count Server_217_DevBlog among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded.
Map and rules
What settings and rules apply on Server_217_DevBlog?
The name of Server_217_DevBlog gives no gather rate. You will find no published group limit. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. VAC, Valve's anti-cheat, is not enabled.
Server_217_DevBlog runs which map?
A procedural map, generated by the game, is what Server_217_DevBlog runs.
Connecting
What is the way to join Server_217_DevBlog?
To connect, start Rust, press F1, and type client.connect 212.110.152.61:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,v2183,h5e7466bf,stok,gmrust,oxide,modded
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max players10 slots are available.
v2183
ProtocolJoin only if your game runs protocol 2183.
Mods and access
oxide
OxideThe plugin framework in use is Oxide (uMod).
modded
ModdedPlugins or settings alter the game, so it sits under Modded.
Other
h5e7466bf
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
stok
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).