Working its way up from the back of the class: #14,545 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
34/ 100
F
Lost ground: down 4,701 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); wipes are 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.
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.
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 61% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
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.
usual gap10.1 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 6
The first 48 hours of its last wipes
Mon 28 SepFri 18 Sep
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
Mon 28 Sep, 09:38 UTC31d ago
1
–
running
0
Fri 18 Sep, 06:33 UTC41d ago
1
halved by day 6
10.1 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
debug leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 103.45.128.10:48141.
Is debug up, and how steady is its uptime?
You cannot join now: debug is offline, last seen 31 days ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
What Rust version is debug on?
You will find debug on Rust network protocol 2633 and build 163207, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does debug wipe its map?
There are too few wipes on record for debug to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 31 days 1 hours.
What happens on debug when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. 1 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. The crowd dropped below half by day 6 in the wipes where it did not hold.
Player numbers
Where does debug place in the wider field of Rust servers?
In the top 61% of all ranked servers, debug sits at #14,545 for player hours over the last seven days.
How many players does debug usually have?
It has been 31 days since debug was last seen, and it is offline right now.
Tags
What do debug's tags stand for?
You'll see debug tagged with gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs163207 (Build): This runs on build 163207; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded 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 debug?
These Rust Server Score lists count debug among them: 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.
Map and rules
What settings and rules apply on debug?
You will find no gather rate in the name of debug. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on debug?
A procedural map of size 4,750 and seed 1337, generated by the game, is what debug runs. 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 debug?
To connect, start Rust, press F1, and type client.connect 103.45.128.10:48141. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2633,gmrust,cs163207,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp1
Max playersThe server holds 1 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs163207
BuildThis runs on build 163207.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under 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); wipes are the one to work on (F).