Statistical profileOffline
debug
103.45.128.10:48141 checked 31d ago
Connect to this server
1. Main points
Players now
1/ 1
100% full
7-day average
0
peak –
Rank
#14,545
top 61%
Last wipe
31d ago
no schedule published
Next wipe
–
too few wipes seen yet
Main points
- The server is offline; at its last check there were 1 players on it, 100% of its 1 slots.
- It ranks #14,545 of all ranked servers, the top 61%, on player hours over the last seven days.
- Its current map went up 31d ago.
2. Players
Figure 1: Players on debug
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 61% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patterntoo 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 gap
10.1 days
between real wipes
Wipe-day peak
1
players, last three wipes
Crowd held
0%
else halves by day 6
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| 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 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
8. Server characteristics
Table 3: Characteristics of debug
What the server publishes and what was recorded
| Address | 103.45.128.10:48141 |
|---|---|
| Region | – |
| Max players | 1 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 28 Sep 2026, 10:13 UTC |
| Hostname | – |
| First seen | 13 Sep 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 149 on average | 167 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 182 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 70 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 13 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 20 / 1000 |
10. Quick answers
From the figures on this page.
Wipe records
When does debug wipe, and how often?
With too few wipes of debug on record, its rhythm remains unclear. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. 31 days 1 hours have passed since this world was made.
On debug, what happens on wipe day?
Recent wipes drew an average peak of 1 players. The peak of the latest wipe's crowd came 1 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe in 0% of cases. If not, it dropped below half by day 6.
Server record
What does the record show for the uptime and current status of debug?
Last seen 31 days 1 hours ago, debug is offline in this release. A total of 0 of 168 hours were up over 7 full days, which is 0% of the time. It was first seen by Rust Census on 13 September 2026.
Which location does debug run from?
No region is given by debug. Rust Census does not look up where the machine stands; it shows where a server says it is. 103.45.128.10:48141 is its address.
Which Rust version is debug running?
This release lists debug on Rust network protocol 2633 and build 163207, running on Linux. To join, your game has to be on the same protocol; Steam handles the update.
Player figures
How many players does debug carry?
The last count for debug was 31 days 1 hours ago; it is offline at present.
How does debug compare with other servers in the rankings?
For seven-day player hours, debug is ranked #14,545, placing it in the top 61% of all ranked servers.
Lists and tags
On Rust Census, which lists and filters carry debug?
The Rust Census lists that debug fits are: Modded Rust servers, counted. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What is meant by each tag shown on debug?
These are the tags debug publishes for the game's server browser to read: gmrust (Game mode): Survival play, in the standard Rust format; mp1 (Max players): Slots: 1; ts8 (Group limit): This is the game default: 8 to a team; v2633 (Protocol): To connect, your game version must match protocol 2633; cs163207 (Build): Build 163207 is installed; ptrak (Networking): RakNet is used, the standard network layer of the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): This server is listed as modded, with plugins or settings that change the game. At the top of this page you will find the tags for current players, queue and world creation time.
Rules, map
Which map is in use on debug?
debug runs a procedural map of size 4,750 with seed 1337, generated by the game. The same size and seed produce the same map; RustMaps shows it from this page.
How is debug configured, and what rules does it keep?
The name of debug carries no gather rate. The default applies: groups are capped at 8 players. It runs survival, the standard game: gather, build, raid. Combat between players and raiding are both permitted. Modded is its section in the server browser, because plugins or settings change the game. Oxide plugins are recorded on it. Anti-cheat is active: VAC, Valve's system, is on.
Join details
What steps are needed to join debug?
You can open the console in Rust with F1 and enter client.connect 103.45.128.10:48141; or press Launch Rust and join on this page, and you are connected through Steam.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp1,ptrak,$r?,v2633,gmrust,cs163207,ts8,^o^z
Game
gmrust | Game mode Survival play, in the standard Rust format. |
|---|---|
mp1 | Max players Slots: 1. |
ts8 | Group limit This is the game default: 8 to a team. |
v2633 | Protocol To connect, your game version must match protocol 2633. |
cs163207 | Build Build 163207 is installed. |
ptrak | Networking RakNet is used, the standard network layer of the game. |
$r? | Region code No region code is set. |
Mods and access
^o | Oxide The plugin framework in use is Oxide (uMod). |
|---|---|
^z | Modded This server is listed as modded, with plugins or settings that change the game. |
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.