Station XX-13547 · no signal
TESTSERVER by EM$⌀
Offline 46.124.143.158:28015 checked 13d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,547
- top 63%
- Last wipe
- 13d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 10 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 63% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 0.4 daysbetween real wipes
- on rhythm
- 33%of its recent wipes
- wipe-day peak
- 1players, last three wipes
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| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Wed 14 Oct, 13:03 UTC13d ago | M0.0■steady | 1 | – | – | running | 1 |
| Wed 14 Oct, 02:17 UTC14d ago | M0.0■steady | 1 | – | 0.4 days | 1 | |
| Tue 13 Oct, 08:29 UTC14d ago | M0.0■steady | 1 | – | 0.7 days | 1 | |
| Tue 13 Oct, 00:44 UTC15d ago | M0.0■steady | 1 | – | 0.3 days | 1 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on TESTSERVER by EM$⌀?
A procedural map runs on TESTSERVER by EM$⌀, generated by the game.
Which settings and rules apply on TESTSERVER by EM$⌀?
You will find no gather rate in the name of TESTSERVER by EM$⌀. The group limit is 8 players, the game's default. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. The server has VAC off, Valve's anti-cheat.
Player counts
What is the current population on TESTSERVER by EM$⌀?
TESTSERVER by EM$⌀ is not responding at this moment and is offline, last seen 13 days 18 hours ago.
How does TESTSERVER by EM$⌀ rank against other Rust servers?
The last seven days of player hours place TESTSERVER by EM$⌀ at #13,547, in the top 63% of all ranked servers.
Server details
How reliably does TESTSERVER by EM$⌀ stay online?
As recorded now, TESTSERVER by EM$⌀ is not reachable, the last contact having been 13 days 18 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 11 October 2026 is when Rust Server Trends first recorded it.
Which region does TESTSERVER by EM$⌀ run from?
No region is published by TESTSERVER by EM$⌀. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 46.124.143.158:28015.
What build of Rust does TESTSERVER by EM$⌀ use?
On Windows, TESTSERVER by EM$⌀ runs Rust network protocol 2634 and build 167781. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on TESTSERVER by EM$⌀?
The recent wipes averaged a busiest count of 1 players. 0 hours into the latest wipe, the crowd reached its peak.
How often does TESTSERVER by EM$⌀ wipe, and on which days?
There is no next wipe to predict at TESTSERVER by EM$⌀, since its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 13 days 18 hours.
Server tags
What do the server tags on TESTSERVER by EM$⌀ mean?
Tags published by TESTSERVER by EM$⌀ and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp10 (Max players): Slots: 10; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): It runs game build 167781; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does TESTSERVER by EM$⌀ appear?
These Rust Server Trends lists include TESTSERVER by EM$⌀: Modded Rust servers, tracked live. These filters bring it up 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 to join
How do you connect to TESTSERVER by EM$⌀?
You can connect by pressing F1 in Rust and typing client.connect 46.124.143.158:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.