Offline 103.45.128.10:48141 checked 30d ago
debug
Connect
srv = rust.server("103.45.128.10:48143")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 28 Sep, 09:38 UTC30d ago | 1 | NaN | running | 0 |
| 1 | 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.
display(srv.map, srv.info())Map
4750 · seed 1337
- map
- Procedural Map
- size
- 4750
- seed
- 1337
Server
srv.info()- 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
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 108/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 147/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 45/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 18/1000 |
Quick answers
From the figures on this page.
Population
What position does debug take in the server rankings?
Player hours over seven days put debug at #14,545, in the top 61% of the ranked set.
What population does debug carry?
The current row shows debug offline; the last response was 30 days 21 hours ago.
Server data
Which Rust version is debug on?
Version Rust network protocol 2633 and build 163207 on Linux is reported by debug. Steam updates your game for you, but the protocol must match to join.
How reliable is debug, and is it up?
debug is offline at this refresh; the last response came 30 days 21 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 13 September 2026.
In which location is debug hosted?
No region is published by debug. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 103.45.128.10:48141 is its address.
Settings and map
What rules and settings are recorded for debug?
The name debug carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has debug loaded?
Size 4,750, seed 1337: the procedural map on debug, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
On what schedule does debug wipe?
The record for debug holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 30 days 22 hours ago, and that is the one in play.
On debug, what happens on wipe day?
The average peak over recent wipes is 1 players. 1 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. The drop under half arrived by day 6 in the other cases.
Tags, lists
Which lists on Rust Data hold debug, and which filters?
The Rust Data lists that debug fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on debug?
These tags are published by debug and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163207 (Build): Recorded game build: 163207; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way to join debug?
In Rust, F1 opens the console: type client.connect 103.45.128.10:48141. Launch Rust on this page does the same by opening the game through Steam and connecting.