Offline 185.30.229.67:28015 checked 24d ago
TEST
Connect
srv = rust.server("185.30.229.67: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 bestTop 58% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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 2, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 4 Oct, 12:14 UTC24d ago | 2 | NaN | running | 0 |
| 1 | Sat 3 Oct, 17:41 UTC25d ago | 2 | NaN | 0.8 days | 1 |
| 2 | Fri 2 Oct, 15:15 UTC26d ago | 2 | NaN | 1.1 days | 0 |
| 3 | Tue 29 Sep, 17:13 UTC29d ago | 2 | held half | 2.9 days | 0 |
| 4 | Fri 25 Sep, 23:03 UTC33d ago | 2 | held half | 3.8 days | 0 |
| 5 | Mon 14 Sep, 18:55 UTC44d ago | 2 | held half | 11.2 days | 3 |
# 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
- 185.30.229.67:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Oct 2026, 12:43 UTC
- hostname
- –
- first seen
- 13 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 | RustForNoobs.com Primitive | Bow / Melee | Medieval | NA · groups of 16+ · biweekly · 1 on average | 1/50 |
| 1 | [US East] Facepunch Primitive 1 | NA · groups of 8+ · monthly · 21 on average | 20/400 |
| 2 | [EU] Facepunch Primitive 1 | EU · groups of 8+ · monthly · 16 on average | 8/400 |
| 3 | JumpRust.com - EU 3x|Primitive|Full PVP|Shop|Kits|TP|Clans| | EU · groups of 16+ · 3x · biweekly · 5 on average | 2/120 |
| 4 | JumpRust.com - US 3x|Primitive|Full PVP|Shop|Kits|TP|Clans| | NA · groups of 16+ · 3x · biweekly · 4 on average | 3/120 |
| 5 | Rust4Noobs | Solo/Duo | Primitive Monthly | No BP Wipe | EU · duo · monthly · 6 on average | 1/100 |
Quick answers
From the figures on this page.
Player counts
What position does TEST take in the server rankings?
Over the last seven days TEST sits at #13,191 on player hours, in the top 58% of ranked servers.
How full does TEST run?
The current row shows TEST offline; the last response was 24 days 16 hours ago.
Server facts
Which Rust version is TEST on?
Rust network protocol 2634 and build 166586 on Windows is what TEST runs. Steam updates your game for you, but the protocol must match to join.
Is TEST up, and what does its uptime show?
Offline now for TEST, last seen 24 days 16 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 13 September 2026.
Where does TEST sit?
For TEST, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 185.30.229.67:28015 is its address.
Settings and map
What rules and settings are recorded for TEST?
You will not find a gather rate in the string TEST. No custom cap; the default of 8 players per group stands. Recorded as primitive, guns are out, replaced by bows, spears and melee. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has TEST selected?
TEST runs a procedural map, which the game generates.
Wipe schedule
On what schedule does TEST wipe?
No next wipe can be predicted for TEST, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 24 days 18 hours ago.
On TEST, what happens on wipe day?
Recent wipes averaged 2 players at their peak. The crowd on the latest wipe topped out 0 hours after it began. Half the peak or more was held to the next wipe in 100% of recent wipes.
Tags, lists
Which lists on Rust Data hold TEST, and which filters?
The Rust Data lists that TEST fits are: Modded Rust servers and Primitive Rust servers. It appears under these filters on the server list: Type: Modded; Game mode: Primitive; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on TEST hold?
Read by the game's server browser, the tags TEST publishes are: gmprimitive (Game mode): No guns here; primitive rules mean bows, spears and melee; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166586 (Build): Build number: 166586; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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.
Connecting
What is the way into TEST?
Enter client.connect 185.30.229.67:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.