Offline 46.172.42.186:28015 checked 13d ago
nameserver+oxide.derictory
Connect
srv = rust.server("46.172.42.186:28016")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# Peak: the most players in the first 48 hours. 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 46.172.42.186:28015
- region
- –
- max players
- 15
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 11 Oct 2026, 14:14 UTC
- hostname
- –
- first seen
- 15 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 157 on average | 101/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 110/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 91/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 28/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 23/1000 |
Quick answers
From the figures on this page.
Population data
How does nameserver+oxide.derictory compare in the rankings?
Rank #15,082 on seven-day player hours for nameserver+oxide.derictory, within the top 70% of all ranked servers.
What population does nameserver+oxide.derictory carry?
The current row shows nameserver+oxide.derictory offline; the last response was 13 days 4 hours ago.
Server data
What Rust version does nameserver+oxide.derictory run?
Version Rust network protocol 2634 and build 167398 on Windows is reported by nameserver+oxide.derictory. Joining needs the same protocol on your game; Steam handles the update.
How reliable is nameserver+oxide.derictory, and is it up?
The latest sample has nameserver+oxide.derictory offline, with a last sighting 13 days 4 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 15 October 2026.
In which location is nameserver+oxide.derictory hosted?
No region is published by nameserver+oxide.derictory. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 46.172.42.186:28015.
Rules, settings, map
Which rules apply on nameserver+oxide.derictory, and what settings?
The name nameserver+oxide.derictory carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has nameserver+oxide.derictory selected?
nameserver+oxide.derictory runs a procedural map, which the game generates.
Wipe data
When does nameserver+oxide.derictory wipe, and on what schedule?
A rhythm cannot be read from the wipes of nameserver+oxide.derictory on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 17 days 7 hours ago.
Tags, lists
Where does nameserver+oxide.derictory appear among Rust Data lists and filters?
On Rust Data, nameserver+oxide.derictory appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on nameserver+oxide.derictory?
The game's server browser reads these tags from nameserver+oxide.derictory: gmrust (Game mode): Rust survival in its standard form; mp15 (Max players): 15 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into nameserver+oxide.derictory?
Enter client.connect 46.172.42.186:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.