On the class lists: D (49), with population over 48 hours and no performance mark.
Players now1/ 1010% full
7-day average1peak 1
Rank#11,466top 51%
Last wipe46d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
10/ 100
F
A quiet classroom so far: 1 of 10 on average. Plenty of space to grow.
Standingrank on player hours
49/ 100
D
Working its way up from the back of the class: #11,466 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 (D); 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 51% 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
Server_216_DevBlog leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 31.135.199.171:28015 is the address to use.
How reliable is Server_216_DevBlog, and is it up?
You cannot join now: Server_216_DevBlog is offline, last seen 4 days 6 hours ago. It was up 2 of 168 hours over the last 7 full days, which is 1% of the time. The first sighting by Rust Server Score was on 15 September 2026.
Which Rust version is Server_216_DevBlog running?
Rust network protocol 2180 on Windows is what Server_216_DevBlog runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does Server_216_DevBlog wipe, and how often?
Server_216_DevBlog has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 46 days 23 hours.
Player count
Where does Server_216_DevBlog place in the wider field of Rust servers?
Over the last seven days, Server_216_DevBlog has #11,466 for player hours, in the top 51% of all ranked servers.
How many players does Server_216_DevBlog usually have?
It has been 4 days 6 hours since Server_216_DevBlog was last seen, and it is offline right now. Averaging 1 players over seven days, it peaked at 1.
Tags
What do Server_216_DevBlog's tags stand for?
You'll see Server_216_DevBlog tagged with gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): The server holds 10 slots; v2180 (Protocol): The game protocol is 2180, so your game must match that version to join; oxide (Oxide): The plugin framework in use is Oxide (uMod); modded (Modded): The game is changed by plugins or settings; you will find it under Modded; hdf93daba (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 in the browser, which picks them up from the server. 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_216_DevBlog?
Rust Server Score lists that include Server_216_DevBlog: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded.
Server rules
How is Server_216_DevBlog set up, and what rules does it keep?
You will find no gather rate in the name of Server_216_DevBlog. 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. Plugins or settings change the game here, and the server browser lists it under Modded. The server does not run VAC, Valve's anti-cheat.
Server_216_DevBlog runs which map?
A procedural map, generated by the game, is what Server_216_DevBlog runs.
How to join
What is the way to join Server_216_DevBlog?
To connect, start Rust, press F1, and type client.connect 31.135.199.171:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,v2180,hdf93daba,stok,gmrust,oxide,modded
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max playersThe server holds 10 slots.
v2180
ProtocolThe game protocol is 2180, so your game must match that version to join.
Mods and access
oxide
OxideThe plugin framework in use is Oxide (uMod).
modded
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Other
hdf93daba
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 standing (D); population is the one to work on (F).