RUST METRICSFlight deck · live data
Data live Servers11,649 Players42,065 Populated2,888 Fresh wipes 3 h106 Scan5 min
‹ All servers37.212.24.130:28015
Offline Full Queue Fresh wipe Wipe due No query

BrowserListNameServer - Oxide By - lox

Offline 37.212.24.130:28015 checked 17d ago

modded
COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

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#15,549top 71%
Last wipe138d 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 71% 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 BrowserListNameServer - Oxide By - lox follow?

The rhythm of BrowserListNameServer - Oxide By - lox'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 138 days 4 hours ago.

Lists and filters

Which tags does BrowserListNameServer - Oxide By - lox carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; v2293 (Protocol): Match the game version: protocol 2293 is required; ptrak (Networking): RakNet carries the traffic, as standard for Rust; oxide (Oxide): Plugin framework in use: Oxide (uMod); modded (Modded): Modded: plugins or settings depart from the stock game; h532c2936 (Custom tag): Owner or plugin definition: this tag is not a standard Rust one; stok (Custom tag): Owner or plugin definition: this tag is not a standard Rust one from BrowserListNameServer - Oxide By - lox. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does BrowserListNameServer - Oxide By - lox appear in Rust Metrics lists and filters?

These Rust Metrics lists carry BrowserListNameServer - Oxide By - lox: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded.

Population

Where does BrowserListNameServer - Oxide By - lox sit in the rankings?

Ranking for BrowserListNameServer - Oxide By - lox: #15,549 on seven-day player hours, top 71% of all ranked servers.

How full does BrowserListNameServer - Oxide By - lox get?

Status for BrowserListNameServer - Oxide By - lox: offline. Last seen 17 days 15 hours ago.

Operator and location

Where does BrowserListNameServer - Oxide By - lox sit?

No region comes from BrowserListNameServer - Oxide By - lox. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 37.212.24.130:28015.

What Rust version is BrowserListNameServer - Oxide By - lox on?

Reading: BrowserListNameServer - Oxide By - lox, Rust network protocol 2293, Windows. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is BrowserListNameServer - Oxide By - lox, and is it online now?

BrowserListNameServer - Oxide By - lox reports offline. The last reading came 17 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 12 October 2026, recorded by Rust Metrics.

Rules and settings

What rules does BrowserListNameServer - Oxide By - lox enforce, and what are its settings?

Check: gather rate. The name BrowserListNameServer - Oxide By - lox does not state one. Check: group limit. None published. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Check: anti-cheat. VAC, Valve's system, is off.

How to join

What do you do to join BrowserListNameServer - Oxide By - lox?

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

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,v2293,h532c2936,stok,gmrust,oxide,modded

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players The server holds 100 slots.
v2293
Protocol Match the game version: protocol 2293 is required.
ptrak
Networking RakNet carries the traffic, as standard for Rust.

Mods and access

oxide
Oxide Plugin framework in use: Oxide (uMod).
modded
Modded Modded: plugins or settings depart from the stock game.

Other

h532c2936
Custom tag Owner or plugin definition: this tag is not a standard Rust one.
stok
Custom tag Owner or plugin definition: this tag is not a standard Rust one.

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.