Station XX-14545 · no signal
debug
Offline 103.45.128.10:48141 checked 31d ago
- Players now
- 1/ 1
- 100% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,545
- top 61%
- Last wipe
- 31d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 1 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 10.1 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 0%else halves by day 6
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 28 Sep, 09:38 UTC31d ago | M0.0▲rising | 1 | – | running | 0 | |
| Fri 18 Sep, 06:33 UTC41d ago | M0.0▲rising | 1 | halved by day 6 | 10.1 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on debug?
Generated by the game, the map on debug is procedural, size 4,750 with seed 1337. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on debug?
The name of debug gives no gather rate. At the game's default, groups can have up to 8 players. survival is the game mode, standard play, with gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Live population
What is the current population on debug?
A reading taken now finds debug offline; the most recent activity was 31 days 5 hours ago.
How does debug rank against other Rust servers?
On player hours for the past week, debug sits at #14,545, which puts it inside the top 61% of every ranked server.
Server facts
How reliably does debug stay online?
No contact with debug right now, and the last recorded contact was 31 days 5 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 13 September 2026 is when Rust Server Trends first recorded it.
Which region does debug run from?
Nothing about a region comes from debug. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 103.45.128.10:48141.
What build of Rust does debug use?
debug is running Rust network protocol 2633 and build 163207 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on debug?
On average, the busiest point of its recent wipes drew 1 players. 1 hours after the latest wipe, the crowd peaked. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 6.
On what timetable does debug run its wipes?
On record so far are too few of debug's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 31 days 6 hours.
Lists and tags
What do the server tags on debug mean?
Tags published by debug and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp1 (Max players): The server has 1 slots; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs163207 (Build): It runs game build 163207; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does debug appear?
The Rust Server Trends lists that take in debug are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Join the server
How do you connect to debug?
You can connect by pressing F1 in Rust and typing client.connect 103.45.128.10:48141 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.