Offline 135.125.243.29:30002 checked 3d ago
[DEV] Test Server
Connect
srv = rust.server("135.125.243.29:27017")
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. 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 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 1h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 1h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 1h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 18:59 UTC FW27d ago | 1 | NaN | running | 1 |
# 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 135.125.243.29:30002
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 18:59 UTC
- hostname
- –
- first seen
- 29 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 · 151 on average | 144/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 196/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 90/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 88 on average | 226/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 348/350 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does [DEV] Test Server rank?
Player hours over seven days put [DEV] Test Server at #13,771, in the top 62% of the ranked set.
What population does [DEV] Test Server carry?
[DEV] Test Server returns no live count at this refresh, having last been seen 3 days 20 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
Server facts
What Rust version does [DEV] Test Server run?
Version Rust network protocol 2635 and build 167781 on Linux is reported by [DEV] Test Server. Steam updates your game for you, but the protocol must match to join.
Is [DEV] Test Server up, and what does its uptime show?
[DEV] Test Server is offline at this refresh; the last response came 3 days 20 hours ago. Uptime of 1% across the last 7 full days: 2 hours of 168. Rust Data logged it first on 29 September 2026.
Which location does [DEV] Test Server run from?
There is no region published for [DEV] Test Server. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 135.125.243.29:30002.
Map and rules
What rules and settings are recorded for [DEV] Test Server?
You will not find a gather rate in the string [DEV] Test Server. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is not running; Valve's anti-cheat is off.
What is the map on [DEV] Test Server?
[DEV] Test Server runs a procedural map, which the game generates.
Wipe schedule
On what schedule does [DEV] Test Server wipe?
A single wipe each month, the force wipe, is all [DEV] Test Server does. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 27 days 22 hours ago, and that is the one in play.
What is wipe day on [DEV] Test Server like?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 0 hours in.
Lists and tags
Which lists on Rust Data hold [DEV] Test Server, and which filters?
On Rust Data, [DEV] Test Server appears in these lists: Modded Rust servers. It appears under these filters 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 [DEV] Test Server?
These tags are published by [DEV] Test Server and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): 40 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs167781 (Build): The server runs build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into [DEV] Test Server?
In Rust, F1 opens the console: type client.connect 135.125.243.29:30002. Launch Rust on this page does the same by opening the game through Steam and connecting.