On the class lists: F (31), with population over 48 hours and no performance mark.
Players now0/ 100% full
7-day average0peak –
Rank#15,351top 69%
Last wipe4d 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,351 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.
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 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
You'll find no region listed by Server_217_DevBlog. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 50.7.37.34:28015.
Is Server_217_DevBlog up, and how steady is its uptime?
At this moment, Server_217_DevBlog is offline; the last time it was seen was 3 days 20 hours ago. For the last 4 full days, it was up 5 of 96 hours, or 5% of the time. On 24 October 2026, Rust Server Score saw it for the first time.
Which Rust version is Server_217_DevBlog running?
You will find Server_217_DevBlog on Rust network protocol 2183, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does Server_217_DevBlog wipe its map?
The record holds too few of Server_217_DevBlog's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 4 days 22 hours have passed since this world was made.
Player numbers
Where does Server_217_DevBlog place in the wider field of Rust servers?
In the top 69% of all ranked servers, Server_217_DevBlog sits at #15,351 for player hours over the last seven days.
How many players does Server_217_DevBlog usually have?
The last sighting of Server_217_DevBlog was 3 days 20 hours ago, and it is offline right now. Over the past seven days, the average player count was 0.
Tags and filters
What do Server_217_DevBlog's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): 10 slots are available; v2183 (Protocol): Join only if your game runs protocol 2183; oxide (Oxide): Oxide (uMod) provides the plugin framework here; modded (Modded): Plugins or settings alter the game, so it sits under Modded; h5e7466bf (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner; stok (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner are the tags Server_217_DevBlog publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the 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. It shows under the following filters 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?
The name of Server_217_DevBlog gives no gather rate. It publishes no limit on group size. You get survival here, gather and build and raid: 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?
A procedural map, generated by the game, is what Server_217_DevBlog runs.
How to join
What is the way to join Server_217_DevBlog?
Enter client.connect 50.7.37.34: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 modeRust survival, played by the standard rules.
mp10
Max players10 slots are available.
v2183
ProtocolJoin only if your game runs protocol 2183.
Mods and access
oxide
OxideOxide (uMod) provides the plugin framework here.
modded
ModdedPlugins or settings alter the game, so it sits under Modded.
Other
h5e7466bf
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
stok
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
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).