On the class lists: F (37), with population over 48 hours and no performance mark.
Players now0/ 20% full
7-day average1peak 2
Rank#8,019top 36%
Last wipe1d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
28/ 100
F
A quiet classroom so far: 1 of 2 on average. Plenty of space to grow.
Standingrank on player hours
64/ 100
C
Working its way up from the back of the class: #8,019 on player hours.
Uptimehours on the list, last 48
25/ 100
F
Attendance needs work: on the list only 12 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 159 server fps on average.
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 performance (A+); uptime 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.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 25 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 36% 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.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 26 Oct, 17:47 UTC1d ago
–
–
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
You'll find no region listed by [DEV] Server. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 89.93.3.136:12015.
Is [DEV] Server up, and how steady is its uptime?
You cannot join now: [DEV] Server is offline, last seen 8 hours ago. The uptime it reports puts the last restart at about 2 hours ago. For the last 2 full days, it was up 12 of 48 hours, or 25% of the time. On 25 October 2026, Rust Server Score saw it for the first time.
Is [DEV] Server smooth to play on?
The average over the last 48 hours was 159 server fps, and it never went below 117. Up to 66,413 entities were in the world, covering buildings, deployables and the rest. Up to 2,267 MB of memory was used. Players feel lag when fps drops and entities pile up.
Which Rust version is [DEV] Server running?
You will find [DEV] Server on Rust network protocol 2635 and build 168909, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does [DEV] Server wipe its map?
The record holds too few of [DEV] Server's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 37 hours have passed since this world was made.
Player count
Where does [DEV] Server sit among Rust servers?
In the top 36% of all ranked servers, [DEV] Server sits at #8,019 for player hours over the last seven days.
Is [DEV] Server a busy server?
It has been 8 hours since [DEV] Server was last seen, and it is offline right now. It peaked at 2 and averaged 1 players over the last seven days. The highest average in the last 48 hours came at 18:00 UTC, with 1 players.
Tags
How should you read the tags on [DEV] Server?
The game's browser takes its cue from the tags [DEV] Server has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Carbon provides the plugin framework here. 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 [DEV] Server appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [DEV] Server: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
Rules and settings
How is [DEV] Server set up, and what rules does it keep?
You will find no gather rate in the name of [DEV] Server. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: 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. The plugin count runs to Carbon. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map [DEV] Server uses?
[DEV] Server runs a game-generated procedural map at size 3,500, seed 799696644. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How should you connect to [DEV] Server?
To connect, start Rust, press F1, and type client.connect 89.93.3.136:12015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp2
Max playersThe server holds 2 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonCarbon provides the plugin framework here.
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 performance (A+); uptime is the one to work on (F).