RUST METRICSFlight deck · live data
Data live Servers11,891 Players102,658 Populated3,942 Fresh wipes 3 h337 Scan5 min
‹ All servers83.228.144.254:28015
Offline Full Queue Fresh wipe Wipe due No query

Oxide Self-Built Test

Offline 83.228.144.254:28015 checked 43d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 0 /2

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,468no region published
Last wipe43d 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
15k10k15k20k20 Sep21 Sep22 Sep23 Sep
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

How often does Oxide Self-Built Test wipe, and when?

To tell the rhythm of Oxide Self-Built Test, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 43 days 14 hours ago the current world was made.

Tag meanings

How should you read the tags on Oxide Self-Built Test?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Game build reading: 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from Oxide Self-Built Test. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Oxide Self-Built Test?

Rust Metrics lists featuring Oxide Self-Built Test: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

Where does Oxide Self-Built Test sit in the rankings?

Ranking for Oxide Self-Built Test: #15,468 on seven-day player hours, top – of all ranked servers.

How full does Oxide Self-Built Test get?

Oxide Self-Built Test is not responding; status offline, last seen 43 days 14 hours ago.

Server details

What location is Oxide Self-Built Test hosted in?

No region tag on Oxide Self-Built Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 83.228.144.254:28015.

What Rust version is Oxide Self-Built Test on?

Rust network protocol 2633 and build 163794 on Linux is the build Oxide Self-Built Test runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is Oxide Self-Built Test, and is it online now?

Oxide Self-Built Test reports offline. The last reading came 43 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 16 September 2026, recorded by Rust Metrics.

Map and rules

What rules does Oxide Self-Built Test enforce, and what are its settings?

No gather rate appears in the name: Oxide Self-Built Test. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

What map is Oxide Self-Built Test on?

The game generates a procedural map for Oxide Self-Built Test.

Join

How do you connect to Oxide Self-Built Test?

To join: start Rust, press F1 and type client.connect 83.228.144.254:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp2
Max players The server holds 2 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build Game build reading: 163794.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^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.