On the class lists: D (50), with population over 48 hours and no performance mark.
Players now0/ 5000% full
7-day average0peak 4
Rank#8,834top 40%
Last wipe10d 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 500 on average. Plenty of space to grow.
Standingrank on player hours
60/ 100
C
Working its way up from the back of the class: #8,834 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 128 server fps on average.
Wipeskeeping the crowd after a wipe
80/ 100
B+
Holds its players well after a wipe: 80% of wipes kept half their crowd.
Momentumrank now against a week ago
14/ 100
F
Lost ground: down 6,443 places this week. A strong wipe could turn it round.
A fair term, with more to come.
Strongest in performance (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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 40% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
10 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
W···W··
W··F···
W··W···
W··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 gap3 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak15players, last three wipes
crowd held80%else halves by day 1
The first 48 hours of its last wipes
Sat 17 OctThu 15 OctMon 12 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 17 Oct, 19:12 UTC10d ago
1
–
running
0
Thu 15 Oct, 14:58 UTC12d ago
18
✓ held half
2.2 days
3
Mon 12 Oct, 14:59 UTC15d ago
25
✓ held half
3 days
0
Thu 8 Oct, 14:58 UTC19d ago
12
✓ held half
4 days
4
Mon 5 Oct, 15:00 UTC22d ago
24
✓ held half
3 days
2
Thu 1 Oct, 17:57 UTCFW26d ago
23
halved by day 1
3.9 days
1
Mon 28 Sep, 15:58 UTC29d ago
24
✓ held half
3.1 days
2
Fri 25 Sep, 17:03 UTC32d ago
22
✓ held half
3 days
2
Mon 21 Sep, 15:57 UTC36d ago
6
halved by day 1
4 days
0
Mon 14 Sep, 15:56 UTC43d ago
25
halved by day 2
7 days
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
TESTING 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 51.83.150.41:28015.
Is TESTING up, and how steady is its uptime?
The server is up: TESTING is online now. About 2 days 3 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 103 of 168 hours, or 61% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does TESTING run?
It averaged 128 server fps over the last 48 hours, with a low of 125. Buildings, deployables and everything else in the world added up to as many as 4,021 entities. At its highest, it used 1,054 MB of memory. Players feel lag when fps drops and entities pile up.
On what Rust version does TESTING sit?
The server TESTING is on Rust network protocol 2635 and build 168909 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does TESTING wipe, and how often?
No next wipe can be predicted for TESTING, which wipes at irregular times. 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 10 days 4 hours.
What should you expect from wipe day on TESTING?
Recent wipes have peaked at 15 players on average. Peak numbers came 0 hours into the latest wipe. Half the peak held until the next wipe in 80% of its recent wipes. In the other wipes it slipped under half by day 1.
Player numbers
Where does TESTING place in the wider field of Rust servers?
In the top 40% of all ranked servers, TESTING sits at #8,834 for player hours over the last seven days.
How many players does TESTING usually have?
Right now, 0 players are on TESTING, which has 500 slots. Averaging 0 players over seven days, it peaked at 4. Over the last 48 hours, the peak hour was 09:00 UTC, averaging 0 players.
Lists and filters
How should you read the tags on TESTING?
You'll see TESTING tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp500 (Max players): 500 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; 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): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Carbon provides the plugin framework here in the browser, which picks them up from the server. 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 TESTING appear in the Rust Server Score lists and filters?
Rust Server Score lists that include TESTING: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
How is TESTING set up, and what rules does it keep?
You will find no gather rate in the name of TESTING. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Carbon. You are covered by VAC, Valve's anti-cheat.
TESTING runs which map?
TESTING runs a game-generated procedural map at size 1,000, seed 612351. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
What is the way to join TESTING?
To connect, start Rust, press F1, and type client.connect 51.83.150.41:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp500,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp500
Max players500 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
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
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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).