On the class lists: F (41), with population over 48 hours and no performance mark.
Players now1/ 1010% full
7-day average1peak 2
Rank#13,106top 59%
Last wipe6d 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
41/ 100
F
Working its way up from the back of the class: #13,106 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 59% 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_210_DevBlog leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 146.70.82.20:28015 is the address to use.
Is Server_210_DevBlog up, and how steady is its uptime?
You cannot join now: Server_210_DevBlog is offline, last seen 5 days 5 hours ago. It was up 0 of 120 hours over the last 5 full days, which is 0% of the time. The first sighting by Rust Server Score was on 23 October 2026.
What Rust version is Server_210_DevBlog on?
Rust network protocol 2201 on Windows is what Server_210_DevBlog runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does Server_210_DevBlog reset?
There are too few wipes on record for Server_210_DevBlog to show a 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 6 days 10 hours.
Population
What position does Server_210_DevBlog hold in the rankings?
In the top 59% of all ranked servers, Server_210_DevBlog sits at #13,106 for player hours over the last seven days.
Is Server_210_DevBlog a busy server?
The last sighting of Server_210_DevBlog was 5 days 5 hours ago, and it is offline right now. Averaging 1 players over seven days, it peaked at 2.
Tags
What is meant by the tags on Server_210_DevBlog?
gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): 10 slots are available; 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.
Rules and settings
What settings and rules apply on Server_210_DevBlog?
You will find no gather rate in the name of Server_210_DevBlog. No group limit is published. You get survival here, 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?
The game generates a procedural map for Server_210_DevBlog.
Connecting
How should you connect to Server_210_DevBlog?
Enter client.connect 146.70.82.20: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,v2201,hd910d3d2,stok,gmrust,oxide,modded
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max players10 slots are available.
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 (F); population is the one to work on (F).