Working its way up from the back of the class: #15,980 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
53/ 100
D
Moving up: up 941 places this week.
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 71% 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_217_DevBlog leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 193.107.108.174:28015.
How reliable is Server_217_DevBlog, and is it up?
At this moment, Server_217_DevBlog is offline; the last time it was seen was 24 days 4 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 1 October 2026.
Which Rust version is Server_217_DevBlog running?
You will find Server_217_DevBlog on Rust network protocol 2183, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does Server_217_DevBlog wipe its map?
Server_217_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. The world it runs now was created 27 days 23 hours.
Player numbers
Where does Server_217_DevBlog place in the wider field of Rust servers?
Over the last seven days, Server_217_DevBlog has #15,980 for player hours, in the top 71% of all ranked servers.
What does the population on Server_217_DevBlog look like?
It has been 24 days 4 hours since Server_217_DevBlog was last seen, and it is offline right now.
Tags
How should you read the tags on Server_217_DevBlog?
gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): Its slot count is 10; v2183 (Protocol): The game protocol is 2183, so your game must match that version to join; oxide (Oxide): Oxide (uMod) provides the plugin framework here; modded (Modded): Because settings or plugins change how it plays, it is listed as 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.
Where does Server_217_DevBlog appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Server_217_DevBlog among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded.
Server rules
Which rules does Server_217_DevBlog enforce, and what are its settings?
Nothing in the name of Server_217_DevBlog states a gather rate. It publishes no limit on group size. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. 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.
Server_217_DevBlog runs which map?
A procedural map, generated by the game, is what Server_217_DevBlog runs.
How to join
How do you get onto Server_217_DevBlog?
Enter client.connect 193.107.108.174: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 playersIts slot count is 10.
v2183
ProtocolThe game protocol is 2183, so your game must match that version to join.
Mods and access
oxide
OxideOxide (uMod) provides the plugin framework here.
modded
ModdedBecause settings or plugins change how it plays, it is listed as 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 momentum (D); standing is the one to work on (F).