Station XX-12993 · no signal
TESTSERVER by EM$⌀
Offline 46.125.152.89:28015 checked 11d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #12,993
- top 60%
- Last wipe
- 12d 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 60% 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.5 daysbetween real wipes
- on rhythm
- 0%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 |
|---|---|---|---|---|---|---|
| Fri 16 Oct, 16:32 UTC12d ago | M0.0■steady | 1 | – | running | 1 | |
| Fri 16 Oct, 00:00 UTC12d ago | M0.0■steady | 1 | – | 0.7 days | 1 | |
| Thu 15 Oct, 15:16 UTC13d ago | M0.0■steady | 1 | – | 0.4 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$⌀?
The map on TESTSERVER by EM$⌀ is procedural, produced 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$⌀. Groups hold up to 8 players, which is the default for the game. In survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. Anti-cheat is off: VAC, from Valve.
Population
How many players are recorded on TESTSERVER by EM$⌀ right now?
A reading taken now finds TESTSERVER by EM$⌀ offline; the most recent activity was 11 days 19 hours ago.
How does TESTSERVER by EM$⌀ rank against other Rust servers?
The last seven days of player hours place TESTSERVER by EM$⌀ at #12,993, in the top 60% 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 11 days 19 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 15 October 2026.
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. The address it publishes is 46.125.152.89:28015.
Which Rust version is TESTSERVER by EM$⌀ running?
On Windows, TESTSERVER by EM$⌀ runs Rust network protocol 2634 and build 167781. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on TESTSERVER by EM$⌀?
1 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked.
On what timetable does TESTSERVER by EM$⌀ run its wipes?
No next wipe can be predicted for TESTSERVER by EM$⌀, which wipes at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 12 days 5 hours.
Server tags
What do the server tags on TESTSERVER by EM$⌀ mean?
The game's server browser reads the tags TESTSERVER by EM$⌀ publishes: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): 10 slots are available; 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): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear 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. You will find it 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.
Connecting
How do you connect to TESTSERVER by EM$⌀?
To join, enter client.connect 46.125.152.89:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for 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.