RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h103 Scan5 min
‹ All servers46.172.22.117:28015
Offline Full Queue Fresh wipe Wipe due No query

nameserver+oxide.derictory

Offline 46.172.22.117:28015 checked 16d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 4 8 11 15 PAX 0 /15

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#14,756top 67%
Last wipe17d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k12 Oct13 Oct15 Oct16 Oct18 Oct19 Oct

Top 67% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What wipe timing does nameserver+oxide.derictory follow?

The rhythm of nameserver+oxide.derictory's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 17 days 4 hours ago.

Tag meanings

How should you read the tags on nameserver+oxide.derictory?

Tags published by nameserver+oxide.derictory, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp15 (Max players): Slots: 15; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167398 (Build): The server runs game build 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does nameserver+oxide.derictory appear in Rust Metrics lists and filters?

On Rust Metrics, nameserver+oxide.derictory sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

What position does nameserver+oxide.derictory hold among Rust servers?

Ranking for nameserver+oxide.derictory: #14,756 on seven-day player hours, top 67% of all ranked servers.

What player count does nameserver+oxide.derictory carry?

nameserver+oxide.derictory is not responding; status offline, last seen 16 days 4 hours ago.

Server details

Which location does nameserver+oxide.derictory run from?

No region comes from nameserver+oxide.derictory. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 46.172.22.117:28015.

What Rust version is nameserver+oxide.derictory on?

Version check: Rust network protocol 2634 and build 167398 on Windows, run by nameserver+oxide.derictory. Check: protocol. To join, your game must match; Steam handles the update.

Is nameserver+oxide.derictory up, and how often does it stay up?

Reading: offline. nameserver+oxide.derictory last answered 16 days 4 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 12 October 2026.

Rules and settings

What rules does nameserver+oxide.derictory enforce, and what are its settings?

Reading the name gives no gather rate for nameserver+oxide.derictory. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

What map is nameserver+oxide.derictory on?

The game generates a procedural map for nameserver+oxide.derictory.

Join

What do you do to join nameserver+oxide.derictory?

Check: join. Open Rust, press F1, then enter client.connect 46.172.22.117:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp15,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp15
Max players Slots: 15.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167398
Build The server runs game build 167398.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.