Offline 34.90.155.191:28015 checked 43d ago
self-built-oxide test
Connect
srv = rust.server("34.90.155.191:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestWipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 34.90.155.191:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Sep 2026, 05:49 UTC
- hostname
- –
- first seen
- 16 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 143/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 189/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 78/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 10/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 19/1000 |
Quick answers
From the figures on this page.
Player counts
What position does self-built-oxide test take in the server rankings?
Rank #15,479 on seven-day player hours for self-built-oxide test, within the top – of all ranked servers.
What population does self-built-oxide test carry?
Offline now for self-built-oxide test, with the last sample 43 days 4 hours ago.
Server facts
What Rust version does self-built-oxide test run?
The build is Rust network protocol 2633 and build 163794 on Linux, run by self-built-oxide test. Steam updates your game for you, but the protocol must match to join.
Is self-built-oxide test up, and what does its uptime show?
Offline now for self-built-oxide test, last seen 43 days 4 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 16 September 2026.
Which location does self-built-oxide test run from?
There is no region published for self-built-oxide test. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 34.90.155.191:28015.
Settings and map
Which settings and rules does self-built-oxide test run?
No gather rate appears in the name: self-built-oxide test. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has self-built-oxide test loaded?
self-built-oxide test runs a procedural map, which the game generates.
Wipe data
When does self-built-oxide test wipe, and how often?
Too few wipes are on record for self-built-oxide test to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 43 days 4 hours ago.
Tags, lists
Where does self-built-oxide test appear among Rust Data lists and filters?
The Rust Data lists that self-built-oxide test fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on self-built-oxide test?
The game's server browser reads these tags from self-built-oxide test: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): 5 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs163794 (Build): The server runs build 163794; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way into self-built-oxide test?
Enter client.connect 34.90.155.191:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.