On the class lists: F (31), with population over 48 hours and no performance mark.
Players now0/ 100% full
7-day average0peak –
Rank#15,420top 69%
Last wipe3d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 10 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,420 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (F); population 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 69% 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
No region is published for Server_217_DevBlog. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 176.59.136.86:28015.
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 2 days 12 hours ago. It was up 0% of the time over the last 2 full days, 0 of 48 hours. On 25 October 2026, Rust Server Score saw it for the first time.
What Rust version is Server_217_DevBlog on?
Rust network protocol 2183 on Windows is what Server_217_DevBlog runs. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does Server_217_DevBlog reset?
The record holds too few of Server_217_DevBlog's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 3 days 21 hours.
Player numbers
Where does Server_217_DevBlog sit among Rust servers?
Over the last seven days, Server_217_DevBlog has #15,420 for player hours, in the top 69% of all ranked servers.
What does the population on Server_217_DevBlog look like?
It has been 2 days 12 hours since Server_217_DevBlog was last seen, and it is offline right now. For the last seven days, the average number of players was 0.
Tags and filters
How should you read the tags on Server_217_DevBlog?
You'll see Server_217_DevBlog tagged with gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): 10 slots are available; v2183 (Protocol): To get in, your game needs to be on the same version: the protocol is 2183; oxide (Oxide): The plugin framework in use is Oxide (uMod); modded (Modded): Because settings or plugins change how it plays, it is listed as Modded; h5e7466bf (Custom tag): The owner or a plugin created this tag, so it is not standard Rust; stok (Custom tag): The owner or a plugin created this tag, so it is not standard Rust in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show Server_217_DevBlog?
These Rust Server Score lists count Server_217_DevBlog among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Last wipe: In the last week.
Server rules
Which rules does Server_217_DevBlog enforce, and what are its settings?
You will find no gather rate in the name of Server_217_DevBlog. No group limit is published. 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. You are not covered by VAC, Valve's anti-cheat.
Can you tell me which map Server_217_DevBlog uses?
Server_217_DevBlog runs a procedural map, which the game generates.
Connecting
What is the way to join Server_217_DevBlog?
Enter client.connect 176.59.136.86: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 asmp10,v2183,h5e7466bf,stok,gmrust,oxide,modded
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max players10 slots are available.
v2183
ProtocolTo get in, your game needs to be on the same version: the protocol is 2183.
Mods and access
oxide
OxideThe plugin framework in use is Oxide (uMod).
modded
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Other
h5e7466bf
Custom tagThe owner or a plugin created this tag, so it is not standard Rust.
stok
Custom tagThe owner or a plugin created this tag, so it is not standard Rust.
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 standing (F); population is the one to work on (F).