Station XX-15383 · no signal
TestServerRust - AgentRustService Monitor
Offline 46.181.239.168:27015 checked 8d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,383
- top 70%
- Last wipe
- 13d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
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 pageServer rules
Which map is running on TestServerRust - AgentRustService Monitor?
A procedural map runs on TestServerRust - AgentRustService Monitor, generated by the game.
Which settings and rules apply on TestServerRust - AgentRustService Monitor?
No gather rate appears in the name of TestServerRust - AgentRustService Monitor. At the game's default, groups can have up to 8 players. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Player counts
What is the current population on TestServerRust - AgentRustService Monitor?
No players are recorded on TestServerRust - AgentRustService Monitor at this moment; it is offline, and the last sighting was 8 days 6 hours ago.
How does TestServerRust - AgentRustService Monitor rank against other Rust servers?
The last seven days of player hours place TestServerRust - AgentRustService Monitor at #15,383, in the top 70% of all ranked servers.
Server facts
How reliably does TestServerRust - AgentRustService Monitor stay online?
TestServerRust - AgentRustService Monitor is down at the moment; the last recorded contact was 8 days 6 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 15 October 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is TestServerRust - AgentRustService Monitor hosted?
A region is not published by TestServerRust - AgentRustService Monitor. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 46.181.239.168:27015.
What build of Rust does TestServerRust - AgentRustService Monitor use?
Rust network protocol 2634 and build 167781 on Windows is what TestServerRust - AgentRustService Monitor runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
On what timetable does TestServerRust - AgentRustService Monitor run its wipes?
The rhythm of TestServerRust - AgentRustService Monitor cannot yet be told: too few of its wipes are on record. 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 13 days 16 hours.
Server tags
What do the server tags on TestServerRust - AgentRustService Monitor mean?
Tags published by TestServerRust - AgentRustService Monitor and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): Game build: 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; jp0 (Custom tag): The owner or a plugin applied this tag, which isn't part of standard Rust. 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 TestServerRust - AgentRustService Monitor appear?
You will find TestServerRust - AgentRustService Monitor on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: 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 TestServerRust - AgentRustService Monitor?
Enter client.connect 46.181.239.168:27015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust 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.