Station XX-13146 · no signal
Stagging wipe test
Offline 37.30.52.103:28015 checked 7d ago
- Players now
- 1/ 50
- 2% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 1
- peak 1
- Rank
- #13,146
- top 59%
- Last wipe
- 7d ago
- monthly schedule
- Next wipe
- 7d 20h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 50 slots
- Motion · 24 h
- M –not enough readings
Players
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 bestTop 59% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 20h. The force wipe
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageRules and settings
Which map is running on Stagging wipe test?
A procedural map runs on Stagging wipe test, generated by the game.
Which settings and rules apply on Stagging wipe test?
No gather rate appears in the name of Stagging wipe test. At the game's default, groups can have up to 8 players. In survival mode, gather, build and raid in the standard game. You can raid and fight other players here. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is switched on.
Player counts
What is the current population on Stagging wipe test?
A reading taken now finds Stagging wipe test offline; the most recent activity was 7 days 10 hours ago. The seven-day average is 1 players, with a peak of 1.
How does Stagging wipe test rank against other Rust servers?
On player hours for the past week, Stagging wipe test sits at #13,146, which puts it inside the top 59% of every ranked server.
Operator and location
How reliably does Stagging wipe test stay online?
As recorded now, Stagging wipe test is not reachable, the last contact having been 7 days 10 hours ago. It was up 0% of the time across the last 6 full days: 0 of 144 hours. Its earliest appearance in the records of Rust Server Trends dates to 21 October 2026.
Which region does Stagging wipe test run from?
Nothing about a region comes from Stagging wipe test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 37.30.52.103:28015.
Which Rust version is Stagging wipe test running?
Stagging wipe test is running Rust network protocol 2635 and build 168739 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
How often does Stagging wipe test wipe, and on which days?
An estimate from the force wipe gives Stagging wipe test's next wipe. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. The present world dates from 7 days 10 hours. A monthly wipe schedule is published in its tags.
Server tags
What do the server tags on Stagging wipe test mean?
The game's server browser reads the tags Stagging wipe test publishes: gmvanilla (Game mode): You'll find vanilla survival here; mp50 (Max players): 50 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168739 (Build): Game build: 168739; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^m (Monthly): Once a month it wipes, with the force wipe from Facepunch; sc2 (Custom tag): The owner or a plugin applied this tag, which isn't part of standard Rust. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Stagging wipe test appear?
These Rust Server Trends lists include Stagging wipe test: Rust community servers without the side modes. On the server list, the filters it matches are: 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 2 weeks.
Join the server
What steps get you onto Stagging wipe test?
You can connect by pressing F1 in Rust and typing client.connect 37.30.52.103:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.