On the class lists: F (38), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak 1
Rank#13,577top 61%
Last wipe6d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
39/ 100
F
Working its way up from the back of the class: #13,577 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
36/ 100
F
Slipped a little: down 3,922 places this week. Nothing a good wipe can't fix.
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.
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.
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 18 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 61% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
20 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·WW·WWW
WWW···W
W·WWWWW
···WW··
W·W····
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap1.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Wed 21 OctMon 19 OctFri 16 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 21 Oct, 21:09 UTC6d ago
1
–
running
1
Mon 19 Oct, 14:41 UTC8d ago
1
–
2.3 days
1
Fri 16 Oct, 18:50 UTC11d ago
1
–
2.8 days
1
Thu 15 Oct, 15:23 UTC12d ago
1
–
1.1 days
1
Sun 11 Oct, 05:19 UTC17d ago
1
–
4.4 days
1
Sat 10 Oct, 09:28 UTC18d ago
1
–
0.8 days
1
Fri 9 Oct, 21:27 UTC18d ago
1
–
0.5 days
2
Thu 8 Oct, 00:11 UTC20d ago
2
–
1.9 days
0
Wed 7 Oct, 00:14 UTC21d ago
3
–
1 days
1
Mon 5 Oct, 23:13 UTC22d ago
3
–
1 days
1
Sun 4 Oct, 05:05 UTC24d ago
2
–
1.8 days
0
Wed 30 Sep, 14:59 UTC27d ago
1
✓ held half
3.6 days
0
Tue 29 Sep, 13:49 UTC28d ago
1
–
1 days
0
Mon 28 Sep, 08:55 UTC30d ago
2
–
1.2 days
0
Sun 27 Sep, 09:50 UTC31d ago
2
–
1 days
0
Sat 26 Sep, 07:17 UTC32d ago
1
–
1.1 days
1
Fri 25 Sep, 09:47 UTC33d ago
1
–
0.9 days
0
Wed 23 Sep, 07:09 UTC35d ago
1
–
2.1 days
0
Tue 22 Sep, 06:23 UTC36d ago
1
–
1 days
1
Sun 20 Sep, 14:37 UTC37d ago
1
–
1.7 days
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
ServerDevServer leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 91.245.44.75:28017.
How reliable is ServerDevServer, and is it up?
You cannot join now: ServerDevServer is offline, last seen 6 days 11 hours ago. It was up 2% of the time over the last 7 full days, 3 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
Which Rust version is ServerDevServer running?
The server ServerDevServer is on Rust network protocol 2634 and build 167781 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does ServerDevServer reset?
ServerDevServer wipes at times that vary, so no next wipe can be predicted. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 6 days 13 hours.
What happens on ServerDevServer when wipe day arrives?
The average peak on its recent wipes was 1 players. 1 hours after the latest wipe began, the crowd hit its peak.
Player count
Where does ServerDevServer place in the wider field of Rust servers?
In the top 61% of all ranked servers, ServerDevServer sits at #13,577 for player hours over the last seven days.
What does the population on ServerDevServer look like?
ServerDevServer is offline at the moment; the last time it was seen was 6 days 11 hours ago. Averaging 0 players over seven days, it peaked at 1.
Lists and filters
How should you read the tags on ServerDevServer?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): The server holds 100 slots; ts30 (Group limit): No team may go above 30; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags ServerDevServer publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show ServerDevServer?
Rust Server Score lists that include ServerDevServer: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Server rules
What settings and rules apply on ServerDevServer?
The name of ServerDevServer gives no gather rate. The limit for a group is 30 players. 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 as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server does not run VAC, Valve's anti-cheat.
Which map is in play on ServerDevServer?
The game generates the procedural map on ServerDevServer at size 5,000 with seed 543625. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: discord.gg/atlasrust.
How to join
How should you connect to ServerDevServer?
To connect, start Rust, press F1, and type client.connect 91.245.44.75:28017. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,gmrust,cs167781,ts30,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersThe server holds 100 slots.
ts30
Group limitNo team may go above 30.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
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).