Station XX-15082 · no signal
nameserver+oxide.derictory
Offline 46.172.42.186:28015 checked 12d ago
- Players now
- 0/ 15
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,082
- top 70%
- Last wipe
- 16d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 15 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 pageMap and rules
Which map is running on nameserver+oxide.derictory?
A procedural map runs on nameserver+oxide.derictory, generated by the game.
Which settings and rules apply on nameserver+oxide.derictory?
You will find no gather rate in the name of nameserver+oxide.derictory. At the game's default, groups can have up to 8 players. survival is the game mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Population
How many players are recorded on nameserver+oxide.derictory right now?
nameserver+oxide.derictory is not responding at this moment and is offline, last seen 12 days 6 hours ago.
How does nameserver+oxide.derictory rank against other Rust servers?
The last seven days of player hours place nameserver+oxide.derictory at #15,082, in the top 70% of all ranked servers.
Server facts
How reliably does nameserver+oxide.derictory stay online?
As recorded now, nameserver+oxide.derictory is not reachable, the last contact having been 12 days 6 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 15 October 2026.
Which region does nameserver+oxide.derictory run from?
A region is not published by nameserver+oxide.derictory. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 46.172.42.186:28015 is the address it uses.
What build of Rust does nameserver+oxide.derictory use?
nameserver+oxide.derictory is running Rust network protocol 2634 and build 167398 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
How often does nameserver+oxide.derictory wipe, and on which days?
Too few wipes of nameserver+oxide.derictory are on record yet to show its rhythm. 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 16 days 9 hours.
Lists and tags
What do the server tags on nameserver+oxide.derictory mean?
The game's server browser reads the tags nameserver+oxide.derictory publishes: gmrust (Game mode): Survival in standard Rust; mp15 (Max players): Slots: 15; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167398 (Build): Game build: 167398; ptrak (Networking): The network layer is RakNet, the game's standard; $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. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does nameserver+oxide.derictory appear?
The Rust Server Trends lists that take in nameserver+oxide.derictory are: 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.
Join the server
What steps get you onto nameserver+oxide.derictory?
Enter client.connect 46.172.42.186:28015 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.