Offline 46.124.143.158:28015 checked 14d ago
TESTSERVER by EM$⌀
Connect
srv = rust.server("46.124.143.158: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 63% 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 | Wed 14 Oct, 13:03 UTC14d ago | 1 | NaN | running | 1 |
| 1 | Wed 14 Oct, 02:17 UTC14d ago | 1 | NaN | 0.4 days | 1 |
| 2 | Tue 13 Oct, 08:29 UTC15d ago | 1 | NaN | 0.7 days | 1 |
| 3 | Tue 13 Oct, 00:44 UTC15d ago | 1 | NaN | 0.3 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.124.143.158:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 14 Oct 2026, 13:03 UTC
- hostname
- –
- first seen
- 11 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 · 157 on average | 89/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 91/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 77/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 23/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 16/1000 |
Quick answers
From the figures on this page.
Player counts
How does TESTSERVER by EM$⌀ compare in the rankings?
Over the last seven days TESTSERVER by EM$⌀ sits at #13,547 on player hours, in the top 63% of ranked servers.
How many players does TESTSERVER by EM$⌀ hold at once?
Offline now for TESTSERVER by EM$⌀, with the last sample 14 days 8 hours ago.
About the server
Which Rust version is TESTSERVER by EM$⌀ on?
Rust network protocol 2634 and build 167781 on Windows is what TESTSERVER by EM$⌀ runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is TESTSERVER by EM$⌀, and is it up?
TESTSERVER by EM$⌀ is offline at this refresh; the last response came 14 days 8 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 11 October 2026.
In which location is TESTSERVER by EM$⌀ hosted?
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. 46.124.143.158:28015 is its address.
Rules, settings, map
Which rules apply on TESTSERVER by EM$⌀, and what settings?
No gather rate appears in the name: TESTSERVER by EM$⌀. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: 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. Oxide plugins run on it. The VAC field reads off.
What is the map on TESTSERVER by EM$⌀?
A procedural map runs on TESTSERVER by EM$⌀, generated by the game.
Wipes and dates
On what schedule does TESTSERVER by EM$⌀ wipe?
Irregular wipe times on TESTSERVER by EM$⌀ leave no next wipe to forecast. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 14 days 9 hours ago.
What is wipe day on TESTSERVER by EM$⌀ like?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Which Rust Data filters and lists contain TESTSERVER by EM$⌀?
These Rust Data lists include TESTSERVER by EM$⌀: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on TESTSERVER by EM$⌀?
Read by the game's server browser, the tags TESTSERVER by EM$⌀ publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Build number: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: 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.
Connecting
How can I connect to TESTSERVER by EM$⌀?
In Rust, F1 opens the console: type client.connect 46.124.143.158:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.