Offline 37.30.52.103:28015 checked 6d ago
Stagging wipe test
Connect
srv = rust.server("37.30.52.103:28016")
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 59% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 8d 22h. # The 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
- 37.30.52.103:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 21 Oct 2026, 12:11 UTC
- hostname
- –
- first seen
- 21 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 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 314 on average | 393/500 |
| 1 | Rusty Moose |EU Monthly| | EU · groups of 12+ · monthly · 209 on average | 294/325 |
| 2 | [EU East] Facepunch 4 | EU · groups of 8+ · monthly · 188 on average | 188/350 |
| 3 | [EU] Facepunch 1 | EU · groups of 8+ · monthly · 153 on average | 288/400 |
| 4 | Rustopia.gg - US Large | NA · groups of 16+ · monthly · 137 on average | 120/200 |
| 5 | Magic Rust — Long | Kлaccикa x1 | Pyccкий | EU · groups of 150+ · 1x · monthly · 132 on average | 162/300 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Stagging wipe test rank?
Over the last seven days Stagging wipe test sits at #13,079 on player hours, in the top 59% of ranked servers.
How many players does Stagging wipe test hold at once?
Stagging wipe test returns no live count at this refresh, having last been seen 6 days 7 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
Server facts
What Rust version does Stagging wipe test run?
Rust network protocol 2635 and build 168739 on Windows is what Stagging wipe test runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Stagging wipe test, and is it up?
The latest sample has Stagging wipe test offline, with a last sighting 6 days 7 hours ago. 0 of 120 hours up over the last 5 full days, or 0%. Rust Data logged it first on 21 October 2026.
Where does Stagging wipe test sit?
For Stagging wipe test, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 37.30.52.103:28015 is its address.
Map and rules
What rules and settings are recorded for Stagging wipe test?
The name Stagging wipe test carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.
What is the map on Stagging wipe test?
Stagging wipe test runs a procedural map, which the game generates.
Wipes and dates
When does Stagging wipe test wipe, and how often?
Expect an estimate: Stagging wipe test's next wipe is projected from the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 6 days 7 hours ago. A monthly wipe schedule is published in its tags.
Tags, lists
Where does Stagging wipe test appear among Rust Data lists and filters?
The Rust Data lists that Stagging wipe test fits are: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Server tag: Monthly ^m; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last week.
Which meanings do the tags on Stagging wipe test hold?
These tags are published by Stagging wipe test and read by the game's server browser: gmvanilla (Game mode): Game mode: vanilla survival; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168739 (Build): Build number: 168739; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; sc2 (Custom tag): A plugin or the owner added this; standard Rust does not define it. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into Stagging wipe test?
In Rust, F1 opens the console: type client.connect 37.30.52.103:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.