On the class lists: C− (56), with population over 48 hours and no performance mark.
Players now1/ 1010% full
7-day average1peak 2
Rank#9,403top 42%
Last wipe6d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
8/ 100
F
A quiet classroom so far: 1 of 10 on average. Plenty of space to grow.
Standingrank on player hours
58/ 100
C−
Working its way up from the back of the class: #9,403 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
54/ 100
D
Moving up: up 776 places this week.
A term to build on.
Strongest in standing (C−); 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 42% 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_210_DevBlog. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 194.48.218.212:28015.
How reliable is Server_210_DevBlog, and is it up?
At this moment, Server_210_DevBlog is offline; the last time it was seen was 5 days 15 hours ago. It was up 1 of 144 hours over the last 6 full days, which is 1% of the time. On 22 October 2026, Rust Server Score saw it for the first time.
On what Rust version does Server_210_DevBlog sit?
The server Server_210_DevBlog is on Rust network protocol 2201 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does Server_210_DevBlog reset?
Server_210_DevBlog has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 6 days 20 hours.
Population
Where does Server_210_DevBlog sit among Rust servers?
Over the last seven days, Server_210_DevBlog has #9,403 for player hours, in the top 42% of all ranked servers.
What does the population on Server_210_DevBlog look like?
It has been 5 days 15 hours since Server_210_DevBlog was last seen, and it is offline right now. It peaked at 2 and averaged 1 players over the last seven days.
Tags and filters
What do Server_210_DevBlog's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): The server holds 10 slots; v2201 (Protocol): The game protocol is 2201, so your game must match that version to join; 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; hd910d3d2 (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_210_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.
Where does Server_210_DevBlog appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Server_210_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.
Map and rules
How is Server_210_DevBlog set up, and what rules does it keep?
The name of Server_210_DevBlog gives no gather rate. You will find no published group limit. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. You are not covered by VAC, Valve's anti-cheat.
Can you tell me which map Server_210_DevBlog uses?
Server_210_DevBlog runs a procedural map, which the game generates.
Connecting
What is the way to join Server_210_DevBlog?
To connect, start Rust, press F1, and type client.connect 194.48.218.212:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,v2201,hd910d3d2,stok,gmrust,oxide,modded
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max playersThe server holds 10 slots.
v2201
ProtocolThe game protocol is 2201, so your game must match that version to join.
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
hd910d3d2
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 (C−); population is the one to work on (F).