Station XX-15318 · no signal
_mod_retest_rust_oxide_ae3bdad7
Offline 167.114.157.40:41066 checked 6d ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,318
- top 69%
- Last wipe
- 6d ago
- monthly schedule
- Next wipe
- 7d 6h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 6h. The 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 _mod_retest_rust_oxide_ae3bdad7?
_mod_retest_rust_oxide_ae3bdad7 uses a procedural map, which the game generates.
Which settings and rules apply on _mod_retest_rust_oxide_ae3bdad7?
No gather rate appears in the name of _mod_retest_rust_oxide_ae3bdad7. 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 Community, as a community server. It describes itself as vanilla, which means unchanged from Facepunch's release: no altered rates, kits or rules. The server has VAC on, Valve's anti-cheat.
Population
How many players are recorded on _mod_retest_rust_oxide_ae3bdad7 right now?
_mod_retest_rust_oxide_ae3bdad7 is not responding at this moment and is offline, last seen 6 days 12 hours ago. The seven-day average for this server is 0 players.
How does _mod_retest_rust_oxide_ae3bdad7 rank against other Rust servers?
Over the last seven days, _mod_retest_rust_oxide_ae3bdad7 recorded enough player hours to reach #15,318 worldwide, placing it in the top 69% of all ranked servers.
Operator and location
How reliably does _mod_retest_rust_oxide_ae3bdad7 stay online?
_mod_retest_rust_oxide_ae3bdad7 is down at the moment; the last recorded contact was 6 days 12 hours ago. It was up 0% of the time across the last 6 full days: 0 of 144 hours. On 22 October 2026 it was recorded for the first time by Rust Server Trends.
Which region does _mod_retest_rust_oxide_ae3bdad7 run from?
A region is not published by _mod_retest_rust_oxide_ae3bdad7. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 167.114.157.40:41066.
What build of Rust does _mod_retest_rust_oxide_ae3bdad7 use?
_mod_retest_rust_oxide_ae3bdad7 is running Rust network protocol 2635 and build 168909 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
On what timetable does _mod_retest_rust_oxide_ae3bdad7 run its wipes?
An estimate from the force wipe gives _mod_retest_rust_oxide_ae3bdad7's next wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. It has run its current world for 6 days 12 hours. The tags it publishes carry a monthly wipe schedule.
Lists and tags
What do the server tags on _mod_retest_rust_oxide_ae3bdad7 mean?
These are the tags _mod_retest_rust_oxide_ae3bdad7 publishes for the browser to read: gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): Slots: 50; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^m (Monthly): Once a month it wipes, with the force wipe from Facepunch; ^v (Vanilla): Unchanged from Facepunch's release: no altered rates, kits or rules. 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 _mod_retest_rust_oxide_ae3bdad7 appear?
The Rust Server Trends lists that take in _mod_retest_rust_oxide_ae3bdad7 are: Rust community servers without the side modes and Vanilla Rust servers, recorded live. On the server list, the filters it matches are: Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Monthly ^m and Vanilla ^v; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last week.
Join the server
How do you connect to _mod_retest_rust_oxide_ae3bdad7?
You can connect by pressing F1 in Rust and typing client.connect 167.114.157.40:41066 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.