Offline 46.124.133.189:28015 checked 17d ago
TESTSERVER by EM$⌀
Connect
srv = rust.server("46.124.133.189: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 64% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 10 Oct, 02:21 UTC18d 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
- 46.124.133.189:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 10 Oct 2026, 02:21 UTC
- hostname
- –
- first seen
- 8 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 | 156/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 127 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 178/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 96/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 8/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 44/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does TESTSERVER by EM$⌀ rank?
Player hours over seven days put TESTSERVER by EM$⌀ at #14,067, in the top 64% of the ranked set.
What population does TESTSERVER by EM$⌀ carry?
TESTSERVER by EM$⌀ returns no live count at this refresh, having last been seen 17 days 7 hours ago.
Server facts
What is the Rust version on TESTSERVER by EM$⌀?
The build is Rust network protocol 2634 and build 167398 on Windows, run by TESTSERVER by EM$⌀. Steam updates your game for you, but the protocol must match to join.
Is TESTSERVER by EM$⌀ up, and what does its uptime show?
The latest sample has TESTSERVER by EM$⌀ offline, with a last sighting 17 days 7 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 8 October 2026.
Where does TESTSERVER by EM$⌀ sit?
For TESTSERVER by EM$⌀, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 46.124.133.189:28015.
Settings and map
Which rules apply on TESTSERVER by EM$⌀, and what settings?
The name TESTSERVER by EM$⌀ carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. The VAC field reads off.
Which map has TESTSERVER by EM$⌀ selected?
The game generates its map: procedural, on TESTSERVER by EM$⌀.
Wipe schedule
When does TESTSERVER by EM$⌀ wipe, and how often?
A rhythm cannot be read from the wipes of TESTSERVER by EM$⌀ on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 18 days 7 hours ago.
On TESTSERVER by EM$⌀, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in.
Lists and tags
Which Rust Data filters and lists contain TESTSERVER by EM$⌀?
The Rust Data lists that TESTSERVER by EM$⌀ fits are: 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 TESTSERVER by EM$⌀ hold?
Read by the game's server browser, the tags TESTSERVER by EM$⌀ publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 TESTSERVER by EM$⌀?
Enter client.connect 46.124.133.189:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.