Working its way up from the back of the class: #14,600 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
46/ 100
D
Slipped a little: down 1,239 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing 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 68% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
·····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
No hourly players around its wipes yet.
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 15:05 UTC14d ago
1
–
running
1
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. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 194.48.218.124:28015 is the address to use.
Is Server_210_DevBlog up, and how steady is its uptime?
At this moment, Server_210_DevBlog is offline; the last time it was seen was 14 days 8 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 14 October 2026.
What Rust version is Server_210_DevBlog on?
You will find Server_210_DevBlog on Rust network protocol 2153, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
When does Server_210_DevBlog wipe, and how often?
There are too few wipes on record for Server_210_DevBlog to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 14 days 9 hours have passed since this world was made.
What happens on Server_210_DevBlog when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. 0 hours after the latest wipe began, the crowd hit its peak.
Population
Where does Server_210_DevBlog place in the wider field of Rust servers?
Over the last seven days, Server_210_DevBlog has #14,600 for player hours, in the top 68% of all ranked servers.
Is Server_210_DevBlog a busy server?
It has been 14 days 8 hours since Server_210_DevBlog was last seen, and it is offline right now.
Tags and filters
What do Server_210_DevBlog's tags stand for?
mp10 (Max players): Its slot count is 10; v2153 (Protocol): The game protocol is 2153, so your game must match that version to join; h29248c67 (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 are the tags Server_210_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.
Where does Server_210_DevBlog appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Server_210_DevBlog: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all.
Map and rules
Which rules does Server_210_DevBlog enforce, and what are its settings?
Nothing in the name of Server_210_DevBlog states a gather rate. It publishes no limit on group size. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is not enabled.
Server_210_DevBlog runs which map?
The game generates a procedural map for Server_210_DevBlog.
How to join
What is the way to join Server_210_DevBlog?
To connect, start Rust, press F1, and type client.connect 194.48.218.124:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,v2153,h29248c67,stok
Game
mp10
Max playersIts slot count is 10.
v2153
ProtocolThe game protocol is 2153, so your game must match that version to join.
Other
h29248c67
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 momentum (D); standing is the one to work on (F).