Offline 46.125.152.89:28015 checked 11d ago
TESTSERVER by EM$⌀
Connect
srv = rust.server("46.125.152.89:28016")
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 60% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 16:32 UTC11d ago | 1 | NaN | running | 1 |
| 1 | Fri 16 Oct, 00:00 UTC12d ago | 1 | NaN | 0.7 days | 1 |
| 2 | Thu 15 Oct, 15:16 UTC12d ago | 1 | NaN | 0.4 days | 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
- 46.125.152.89:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 16:32 UTC
- hostname
- –
- first seen
- 15 Oct 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 · 155 on average | 176/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 189/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 131/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 15/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 51/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does TESTSERVER by EM$⌀ rank?
Player hours over seven days put TESTSERVER by EM$⌀ at #12,993, in the top 60% of the ranked set.
How full does TESTSERVER by EM$⌀ run?
TESTSERVER by EM$⌀ returns no live count at this refresh, having last been seen 11 days 7 hours ago.
About the server
What Rust version does TESTSERVER by EM$⌀ run?
Version Rust network protocol 2634 and build 167781 on Windows is reported by TESTSERVER by EM$⌀. Steam updates your game for you, but the protocol must match to join.
How reliable is TESTSERVER by EM$⌀, and is it up?
TESTSERVER by EM$⌀ is offline at this refresh; the last response came 11 days 7 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 15 October 2026.
In which location is TESTSERVER by EM$⌀ hosted?
For TESTSERVER by EM$⌀, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 46.125.152.89:28015.
Map and rules
Which settings and rules does TESTSERVER by EM$⌀ run?
No gather rate appears in the name: TESTSERVER by EM$⌀. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. Anti-cheat status: VAC off.
Which map has TESTSERVER by EM$⌀ loaded?
The game generates its map: procedural, on TESTSERVER by EM$⌀.
Wipes and dates
When does TESTSERVER by EM$⌀ wipe, and on what schedule?
No next wipe can be predicted for TESTSERVER by EM$⌀, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 11 days 18 hours ago.
What is wipe day on TESTSERVER by EM$⌀ like?
The average peak over recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Where does TESTSERVER by EM$⌀ appear among Rust Data lists and filters?
These Rust Data lists include TESTSERVER by EM$⌀: 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; Last wipe: In the last 2 weeks.
How should you read the server tags on TESTSERVER by EM$⌀?
The game's server browser reads these tags from TESTSERVER by EM$⌀: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to TESTSERVER by EM$⌀?
In Rust, F1 opens the console: type client.connect 46.125.152.89:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.