Offline 46.172.42.76:28015 checked 30d ago
nameserver+oxide.derictory
Connect
srv = rust.server("46.172.42.76: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 best
Top 71% 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.76:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Jul 2026, 07:57 UTC
- hostname
- –
- first seen
- 27 Sep 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 · 163 on average | 28/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 59/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 54/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 12/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 14/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does nameserver+oxide.derictory rank?
Player hours over seven days put nameserver+oxide.derictory at #16,964, in the top 71% of the ranked set.
How full does nameserver+oxide.derictory run?
nameserver+oxide.derictory returns no live count at this refresh, having last been seen 30 days 11 hours ago.
Server facts
What Rust version does nameserver+oxide.derictory run?
Version Rust network protocol 2631 and build 157450 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 online now?
Offline now for nameserver+oxide.derictory, last seen 30 days 11 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 27 September 2026.
Which location does nameserver+oxide.derictory run from?
For nameserver+oxide.derictory, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 46.172.42.76:28015.
Settings and map
Which settings and rules does nameserver+oxide.derictory run?
No gather rate appears in the name: nameserver+oxide.derictory. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has nameserver+oxide.derictory selected?
The game generates its map: procedural, on nameserver+oxide.derictory.
Wipes and dates
When does nameserver+oxide.derictory wipe, and how often?
A rhythm cannot be read from the wipes of nameserver+oxide.derictory on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 103 days 16 hours ago.
Lists and tags
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.
Which meanings do the tags on nameserver+oxide.derictory hold?
The game's server browser reads these tags from nameserver+oxide.derictory: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): 5 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2631 (Protocol): Protocol 2631 is required; a different game version cannot connect; cs157450 (Build): Recorded game build: 157450; 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): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way into nameserver+oxide.derictory?
Enter client.connect 46.172.42.76:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.