self-built-oxide test
Key statistics
the figures behind the quote- Players now
- 0/ 5 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,479 no region published
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 28d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 16 Sep 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestWipe schedule
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 126 on average | 200/300 | ▲+9+4.8% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 106 on average | 180/225 | ▼−18−9.0% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 10.10EU · groups of 8+ · weekly · 90 on average | 93/100 | ▲+2+2.4% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 86 on average | 52/1000 | ▼−51−49.6% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 13/1000 | ▼−20−60.1% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 72 on average | 69/700 | ▼−61−46.9% |
Quick answers
from the figures on this pageRules & Settings
What settings and rules are in place on self-built-oxide test?
No gather rate is given in the name of self-built-oxide test. Up to 8 players per group, which is the game's default. It runs survival, gather, build and raid in the standard game. PvP and raiding are enabled. In the server browser it appears under Modded, with plugins or settings that change the game. Oxide plugins are running. VAC is active.
Which map is played on self-built-oxide test?
self-built-oxide test uses a procedural map, which the game generates.
Activity
What position does self-built-oxide test hold in the server rankings?
In the top – of all ranked servers, self-built-oxide test is #15,479 on player hours over the last seven days.
How many players does self-built-oxide test have?
At present, self-built-oxide test is offline; the last sighting was 28 days 8 hours ago.
Wipe Schedule
When does self-built-oxide test schedule its wipes?
There are too few wipes on record for self-built-oxide test to reveal its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. This world has been running for 28 days 9 hours.
Server Overview
What is the location of self-built-oxide test?
There is no region published for self-built-oxide test. Rust Analytics reports the location a server claims, not the machine's actual location. You can reach it at 34.90.155.191:28015.
What Rust version is self-built-oxide test running?
Rust network protocol 2633 and build 163794 on Linux is what self-built-oxide test runs. Joining requires the same protocol on your game, which Steam updates.
Is self-built-oxide test up, and how consistent is its uptime?
Offline at this moment: self-built-oxide test. Last seen 28 days 8 hours ago. 7 full days have passed with 0% uptime, 0 of 168 hours. First sighting by Rust Analytics: 16 September 2026.
Server Tags
How should you interpret the tags on self-built-oxide test?
These tags are published by self-built-oxide test and read by the game's server browser: gmrust (Game mode): Rust's standard survival mode; mp5 (Max players): Slot count: 5; ts8 (Group limit): 8 per team: the default setting, unchanged; v2633 (Protocol): Protocol 2633: matching game versions are required to join; cs163794 (Build): Game build: 163794; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): The region code is absent; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): Modded listing: the game is changed by plugins or settings. Also in the tags and at the top of this page: current players, queue and world creation time.
Where does self-built-oxide test show up in Rust Analytics lists and filters?
The following Rust Analytics lists feature self-built-oxide test: 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 to Join
What is the process to join self-built-oxide test?
Type client.connect 34.90.155.191:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp5,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o^z
Game
gmrust
mp5
ts8
v2633
cs163794
ptrak
$r?
Mods and access
^o
^z
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.