Offline 186.208.153.100:28015 checked 14d ago
test - Procedural
Connect
srv = rust.server("186.208.153.100: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 best
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 14 Oct, 17:40 UTC14d ago | 1 | NaN | running | 1 |
| 1 | Wed 14 Oct, 06:41 UTC15d ago | 1 | NaN | 0.5 days | 0 |
# 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
- 186.208.153.100:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 14 Oct 2026, 17:40 UTC
- hostname
- –
- first seen
- 12 Oct 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.
Population
How does test - Procedural compare in the rankings?
Rank #14,840 on seven-day player hours for test - Procedural, within the top 69% of all ranked servers.
How full does test - Procedural run?
The current row shows test - Procedural offline; the last response was 14 days 14 hours ago.
Server facts
What Rust version does test - Procedural run?
The build is Rust network protocol 2634 and build 167781 on Windows, run by test - Procedural. Steam updates your game for you, but the protocol must match to join.
How reliable is test - Procedural, and is it up?
The latest sample has test - Procedural offline, with a last sighting 14 days 14 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 12 October 2026.
Where does test - Procedural sit?
No region is published by test - Procedural. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 186.208.153.100:28015 is its address.
Settings and map
Which rules apply on test - Procedural, and what settings?
You will not find a gather rate in the string test - Procedural. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC off.
What is the map on test - Procedural?
test - Procedural runs a procedural map, which the game generates.
Wipe data
When does test - Procedural wipe, and how often?
Too few wipes are on record for test - Procedural to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 14 days 16 hours ago, and that is the one in play.
On test - Procedural, what happens on wipe day?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in.
Tags and filters
Which lists on Rust Data hold test - Procedural, and which filters?
These Rust Data lists include test - Procedural: 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 test - Procedural?
The game's server browser reads these tags from test - Procedural: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): 2 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^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.
Join steps
What is the way to join test - Procedural?
The manual route: launch Rust, F1, then client.connect 186.208.153.100:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.