On the class lists: F (31), with population over 48 hours and no performance mark.
Players now0/ 100% full
7-day average0peak –
Rank#15,423top 69%
Last wipe2d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 10 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,423 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 69% 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
You'll find no region listed by Server_217_DevBlog. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 46.33.11.154:28015.
How dependable is Server_217_DevBlog, and is it online at the moment?
At this moment, Server_217_DevBlog is offline; the last time it was seen was 2 days 8 hours ago. For the last 2 full days, it was up 0 of 48 hours, or 0% of the time. The first sighting by Rust Server Score was on 25 October 2026.
What Rust version is Server_217_DevBlog on?
Rust network protocol 2183 on Windows is what Server_217_DevBlog runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does Server_217_DevBlog wipe, and how often?
The record holds too few of Server_217_DevBlog's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 2 days 9 hours have passed since this world was made.
Player count
Where does Server_217_DevBlog place in the wider field of Rust servers?
Over the last seven days, Server_217_DevBlog has #15,423 for player hours, in the top 69% of all ranked servers.
Is Server_217_DevBlog a busy server?
It has been 2 days 8 hours since Server_217_DevBlog was last seen, and it is offline right now. A seven-day average of 0 players applies here.
Tags and filters
What is meant by the tags on Server_217_DevBlog?
The game's browser takes its cue from the tags Server_217_DevBlog has set: 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): The plugin framework in use is Oxide (uMod); modded (Modded): Plugins or settings alter the game, so it sits under Modded; h5e7466bf (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. 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?
Rust Server Score lists that include Server_217_DevBlog: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Last wipe: In the last 3 days.
Server rules
How is Server_217_DevBlog set up, and what rules does it keep?
Nothing in the name of Server_217_DevBlog states a gather rate. No group limit is published. You get survival 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. The server does not run VAC, Valve's anti-cheat.
Can you tell me which map Server_217_DevBlog uses?
Server_217_DevBlog runs a procedural map, which the game generates.
Getting in
How should you connect to Server_217_DevBlog?
Enter client.connect 46.33.11.154: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
OxideThe plugin framework in use is Oxide (uMod).
modded
ModdedPlugins or settings alter the game, so it sits under Modded.
Other
h5e7466bf
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).