Working its way up from the back of the class: #15,090 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
52/ 100
D
Moving up: up 699 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
No daily history yet.
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% 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
Where in the world is Rust Debug Compatibility Test?
The region code for Rust Debug Compatibility Test is au1, but no region is published. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 42.117.242.54:28025.
How reliable is Rust Debug Compatibility Test, and is it up?
At this moment, Rust Debug Compatibility Test is offline; the last time it was seen was 13 days 6 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 16 October 2026.
What Rust version is Rust Debug Compatibility Test on?
Rust network protocol 2573 and build 110006 on Windows is what Rust Debug Compatibility Test runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does Rust Debug Compatibility Test reset?
There are too few wipes on record for Rust Debug Compatibility Test to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 13 days 6 hours have passed since this world was made.
Population
Where does Rust Debug Compatibility Test sit among Rust servers?
In the top 70% of all ranked servers, Rust Debug Compatibility Test sits at #15,090 for player hours over the last seven days.
What does the population on Rust Debug Compatibility Test look like?
The last sighting of Rust Debug Compatibility Test was 13 days 6 hours ago, and it is offline right now.
Tags
How should you read the tags on Rust Debug Compatibility Test?
gmrust (Game mode): Rust survival, played by the standard rules; mp5 (Max players): Its slot count is 5; v2573 (Protocol): To get in, your game needs to be on the same version: the protocol is 2573; cs110006 (Build): Build number: 110006; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $rau1 (Region code): It is filed under the region code au1 are the tags Rust Debug Compatibility Test 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 Rust Debug Compatibility Test?
These Rust Server Score lists count Rust Debug Compatibility Test among them: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Last wipe: In the last 2 weeks.
Map and rules
What settings and rules apply on Rust Debug Compatibility Test?
You will find no gather rate in the name of Rust Debug Compatibility Test. It publishes no limit on group size. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on Rust Debug Compatibility Test?
The game generates a procedural map for Rust Debug Compatibility Test.
How to join
How do you get onto Rust Debug Compatibility Test?
To connect, start Rust, press F1, and type client.connect 42.117.242.54:28025. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$rau1,v2573,gmrust,cs110006
Game
gmrust
Game modeRust survival, played by the standard rules.
mp5
Max playersIts slot count is 5.
v2573
ProtocolTo get in, your game needs to be on the same version: the protocol is 2573.
cs110006
BuildBuild number: 110006.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$rau1
Region codeIt is filed under the region code au1.
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 momentum (D); standing is the one to work on (F).