On the class lists: C− (57), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 2
Rank#5,812top 26%
Last wipe2d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
74/ 100
B−
Holds a respectable place: #5,812 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
51/ 100
D
Slows down under load at times: 31 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 fair term, with more to come.
Strongest in uptime (A+); 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 24 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 26% 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 peak2players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 23 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 24 Oct, 21:46 UTC2d ago
2
–
running
0
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 My Rust Server - Test. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 96.2.164.37:28015 is the address to use.
Is My Rust Server - Test up, and how steady is its uptime?
Right now, My Rust Server - Test is online. About 2 days 20 hours ago, it restarted, based on the uptime it reports. For the last 2 full days, it was up 48 of 48 hours, or 100% of the time. It was first seen by Rust Server Score on 24 October 2026.
How well does My Rust Server - Test run?
The average over the last 48 hours was 31 server fps, and it never went below 10. At its peak, it held 68,827 entities, including buildings, deployables and all else in the world. Memory use reached up to 3,169 MB. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is My Rust Server - Test running?
Rust network protocol 2635 and build 168909 on Windows is what My Rust Server - Test runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does My Rust Server - Test reset?
My Rust Server - Test has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 2 days 22 hours.
What should you expect from wipe day on My Rust Server - Test?
Recent wipes have peaked at 2 players on average. 23 hours after the latest wipe began, the crowd hit its peak.
Population
Where does My Rust Server - Test place in the wider field of Rust servers?
Over the last seven days, My Rust Server - Test has #5,812 for player hours, in the top 26% of all ranked servers.
What does the population on My Rust Server - Test look like?
My Rust Server - Test is showing 0 players right now, with 50 slots in total. Averaging 0 players over seven days, it peaked at 2. The highest average in the last 48 hours came at 21:00 UTC, with 1 players.
Tags and filters
What do My Rust Server - Test's tags stand for?
You'll see My Rust Server - Test tagged with gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature My Rust Server - Test?
These Rust Server Score lists count My Rust Server - Test among them: 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 My Rust Server - Test set up, and what rules does it keep?
Nothing in the name of My Rust Server - Test states a gather rate. The default of 8 players applies as the group cap. It runs survival, 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 Carbon. VAC, Valve's anti-cheat, is enabled.
Which map is in play on My Rust Server - Test?
My Rust Server - Test runs a game-generated procedural map at size 3,500, seed 352165132. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How do you get onto My Rust Server - Test?
To connect, start Rust, press F1, and type client.connect 96.2.164.37:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^z,^y
Game
gmvanilla
Game modeThis is vanilla survival.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonThe plugin framework in use is Carbon.
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 fair term, with more to come. Strongest in uptime (A+); population is the one to work on (F).