Offline 46.172.22.10:28015 checked 8d ago
nameserver+oxide.derictory
Connect
srv = rust.server("46.172.22.10: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 59% 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.22.10:28015
- region
- –
- max players
- 15
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 11 Oct 2026, 14:14 UTC
- hostname
- –
- first seen
- 19 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 · 163 on average | 185/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 111 on average | 147/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 31/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 85 on average | 147/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 51/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does nameserver+oxide.derictory rank?
Rank #13,031 on seven-day player hours for nameserver+oxide.derictory, within the top 59% of all ranked servers.
How full does nameserver+oxide.derictory run?
Offline now for nameserver+oxide.derictory, with the last sample 8 days 4 hours ago.
Server facts
Which Rust version is nameserver+oxide.derictory on?
Rust network protocol 2634 and build 167398 on Windows is what nameserver+oxide.derictory runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is nameserver+oxide.derictory, and is it up?
nameserver+oxide.derictory is offline at this refresh; the last response came 8 days 4 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 19 October 2026.
In which location is nameserver+oxide.derictory hosted?
There is no region published for nameserver+oxide.derictory. 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.22.10:28015.
Settings and map
What rules and settings are recorded for nameserver+oxide.derictory?
No gather rate appears in the name: nameserver+oxide.derictory. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. Anti-cheat status: VAC on.
What is the map on nameserver+oxide.derictory?
A procedural map runs on nameserver+oxide.derictory, generated by the game.
Wipe data
When does nameserver+oxide.derictory wipe, and on what schedule?
The record for nameserver+oxide.derictory holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 16 days 6 hours ago, and that is the one in play.
Tags and filters
Which lists on Rust Data hold nameserver+oxide.derictory, and which filters?
The Rust Data lists that nameserver+oxide.derictory fits are: Modded Rust servers. It appears under these filters on the server list: 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): Survival play, standard Rust; mp15 (Max players): Slot count: 15; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs167398 (Build): Build number: 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
How can I connect to nameserver+oxide.derictory?
The manual route: launch Rust, F1, then client.connect 46.172.22.10:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.