self-built-oxide test
Offline 34.90.155.191:28015 checked 43d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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- 115/500
- 132/100
- 184/225
- 57/700
- 6/200
- 24/1000
Quick answers
from the figures on this pageWipe timing
When does self-built-oxide test wipe?
Its rhythm cannot be told from the wipes of self-built-oxide test on record: there are too few. 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 43 days 3 hours ago.
Lists and filters
Which tags does self-built-oxide test carry, and what do they mean?
These are the tags self-built-oxide test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): Slots: 5; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): The server runs game build 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does self-built-oxide test appear in Rust Metrics lists and filters?
These Rust Metrics lists carry self-built-oxide test: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Occupancy
Where does self-built-oxide test sit in the rankings?
Ranking for self-built-oxide test: #15,479 on seven-day player hours, top – of all ranked servers.
What player count does self-built-oxide test carry?
self-built-oxide test is not responding; status offline, last seen 43 days 3 hours ago.
Server details
Which location does self-built-oxide test run from?
Reading: location. self-built-oxide test gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 34.90.155.191:28015.
What Rust version is self-built-oxide test on?
Reading: self-built-oxide test, Rust network protocol 2633 and build 163794, Linux. Matching protocol is required to join. Let Steam update your game.
Is self-built-oxide test up, and how often does it stay up?
Reading: offline. self-built-oxide test last answered 43 days 3 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 16 September 2026, recorded by Rust Metrics.
Rules and settings
What rules does self-built-oxide test enforce, and what are its settings?
Reading the name gives no gather rate for self-built-oxide test. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.
Which map is live on self-built-oxide test?
The game generates a procedural map for self-built-oxide test.
Join
How do you connect to self-built-oxide test?
Press F1 in Rust and enter client.connect 34.90.155.191:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.