RUST METRICSFlight deck · live data
Data live Servers11,618 Players39,491 Populated2,997 Fresh wipes 3 h102 Scan5 min
‹ All servers46.172.22.10:28015
Offline Full Queue Fresh wipe Wipe due No query

nameserver+oxide.derictory

Offline 46.172.22.10:28015 checked 8d ago

moddedoxide
COM 1 · connect

Server instruments

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

Players now

7% 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#13,031top 59%
Last wipe16d 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
15k10k15k20k19 Oct20 Oct22 Oct23 Oct25 Oct26 Oct

Top 59% 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 schedule

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. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 16 days 16 hours ago.

Lists and filters

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

These are the tags nameserver+oxide.derictory publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp15 (Max players): Slots: 15; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): The server runs game build 167398; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

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

Rust Metrics lists featuring nameserver+oxide.derictory: 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.

Occupancy

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

Ranking for nameserver+oxide.derictory: #13,031 on seven-day player hours, top 59% of all ranked servers.

What is the population on nameserver+oxide.derictory?

Status for nameserver+oxide.derictory: offline. Last seen 8 days 15 hours ago.

Server details

What location is nameserver+oxide.derictory hosted in?

No region tag on nameserver+oxide.derictory. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 46.172.22.10: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. To get in, your game needs the same protocol; Steam applies the update.

How reliable is nameserver+oxide.derictory, and is it online now?

Check: connection. nameserver+oxide.derictory is offline at this moment. Last contact was 8 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 19 October 2026.

Map and rules

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

No gather rate appears in the name: nameserver+oxide.derictory. 8 players per group, the default value. survival, the normal game: build, gather, raid — 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. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on nameserver+oxide.derictory?

Procedural map on nameserver+oxide.derictory, made by the game's generator.

How to join

How do you connect to nameserver+oxide.derictory?

Press F1 in Rust and enter client.connect 46.172.22.10:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp15
Max players Slots: 15.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build The server runs game build 167398.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide It runs Oxide, also known as 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.