On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 200% full
7-day average0peak –
Rank#15,341top 69%
Last wipe71d 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 20 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,341 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: 153 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
49/ 100
D
Slipped a little: down 216 places this week. Nothing a good wipe can't fix.
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 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
No region is published for Rust Tournaments | TEST. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 159.195.206.209:28015.
Is Rust Tournaments | TEST up, and how steady is its uptime?
The server is up: Rust Tournaments | TEST is online now. About 11 days 14 hours ago, it restarted, based on the uptime it reports. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Is Rust Tournaments | TEST smooth to play on?
It averaged 153 server fps over the last 48 hours, with a low of 113. Buildings, deployables and everything else in the world added up to as many as 50,368 entities. At its highest, it used 6,267 MB of memory. When fps is low and entities climb, that is lag to players.
On what Rust version does Rust Tournaments | TEST sit?
The server Rust Tournaments | TEST is on Rust network protocol 2632 and build 161125 under Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
When does Rust Tournaments | TEST wipe, and how often?
Rust Tournaments | TEST has not had enough wipes recorded to reveal its rhythm. 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 71 days 11 hours.
Player count
Where does Rust Tournaments | TEST place in the wider field of Rust servers?
Over the last seven days, Rust Tournaments | TEST has #15,341 for player hours, in the top 69% of all ranked servers.
Is Rust Tournaments | TEST a busy server?
With 20 slots available, Rust Tournaments | TEST currently has 0 players. A seven-day average of 0 players applies here.
Lists and filters
What is meant by the tags on Rust Tournaments | TEST?
You'll see Rust Tournaments | TEST tagged with gmrust (Game mode): Survival in the standard Rust style; mp20 (Max players): 20 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2632 (Protocol): Join only if your game runs protocol 2632; cs161125 (Build): This runs on build 161125; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^z (Modded): Because settings or plugins change how it plays, it is listed as 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.
Which lists and filters on Rust Server Score show Rust Tournaments | TEST?
These Rust Server Score lists count Rust Tournaments | TEST among them: 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.
Server rules
How is Rust Tournaments | TEST set up, and what rules does it keep?
The name of Rust Tournaments | TEST gives no gather rate. 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. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. The server runs Valve's anti-cheat, VAC.
Rust Tournaments | TEST runs which map?
Rust Tournaments | TEST runs a game-generated procedural map at size 3,000, seed 2147483647. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
What is the way to join Rust Tournaments | TEST?
To connect, start Rust, press F1, and type client.connect 159.195.206.209:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2632,gmrust,cs161125,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp20
Max players20 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2632
ProtocolJoin only if your game runs protocol 2632.
cs161125
BuildThis runs on build 161125.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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).