Offline 89.125.214.42:35001 checked 22d ago
TestServ12
Connect
srv = rust.server("89.125.214.42:35003")
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 30 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 72% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 13:29 UTC27d ago | 0 | NaN | running | 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
1000 · seed 352165132
- map
- Procedural Map
- size
- 1000
- seed
- 352165132
Server
srv.info()- address
- 89.125.214.42:35001
- region
- –
- max players
- 200
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 13:29 UTC
- hostname
- ^
- first seen
- 30 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 | 162/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 191/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 96/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 88 on average | 234/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 349/350 |
Quick answers
From the figures on this page.
Population
How does TestServ12 compare in the rankings?
Player hours over seven days put TestServ12 at #15,955, in the top 72% of the ranked set.
How full does TestServ12 run?
Offline now for TestServ12, with the last sample 22 days 4 hours ago.
Server data
What is the Rust version on TestServ12?
Rust network protocol 2634 and build 166586 on Windows is what TestServ12 runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is TestServ12, and is it up?
The latest sample has TestServ12 offline, with a last sighting 22 days 4 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 30 September 2026.
In which location is TestServ12 hosted?
No region is published by TestServ12. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 89.125.214.42:35001.
Rules, settings, map
Which settings and rules does TestServ12 run?
No gather rate appears in the name: TestServ12. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has TestServ12 loaded?
The game generates the map on TestServ12: procedural, size 1,000, seed 352165132. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
When does TestServ12 wipe, and how often?
A rhythm cannot be read from the wipes of TestServ12 on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 27 days 3 hours ago.
On TestServ12, what happens on wipe day?
The average peak over recent wipes is 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Where does TestServ12 appear among Rust Data lists and filters?
On Rust Data, TestServ12 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.
Which meanings do the tags on TestServ12 hold?
These tags are published by TestServ12 and read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp200 (Max players): The server lists 200 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166586 (Build): The server runs build 166586; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. 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.
Connecting
How can I connect to TestServ12?
The manual route: launch Rust, F1, then client.connect 89.125.214.42:35001. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.