RUST METRICSFlight deck · live data
Data live Servers11,721 Players61,329 Populated3,285 Fresh wipes 3 h177 Scan5 min
‹ All servers37.30.52.103:28015
Offline Full Queue Fresh wipe Wipe due No query

Stagging wipe test

Offline 37.30.52.103:28015 checked 8d ago

monthly wipes
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 1 /50

Players now

2% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#13,146top 59%
Last wipe8d agomonthly schedule
Next wipe6d 18hThu 5 Nov, 19:00 UTC FW
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k21 Oct22 Oct24 Oct25 Oct27 Oct28 Oct

Top 59% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 6d 18h. The force wipe

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

When does Stagging wipe test wipe?

An estimate from the force wipe gives Stagging wipe test's next wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world in play was created 8 days 12 hours ago. A monthly wipe schedule is published in its tags.

Lists and filters

Which tags does Stagging wipe test carry, and what do they mean?

Tags published by Stagging wipe test, read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168739 (Build): Game build reading: 168739; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; sc2 (Custom tag): This tag is non-standard, added by the owner or a plugin. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Stagging wipe test?

On Rust Metrics, Stagging wipe test sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: 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.

Population

What position does Stagging wipe test hold among Rust servers?

Ranking for Stagging wipe test: #13,146 on seven-day player hours, top 59% of all ranked servers.

How full does Stagging wipe test get?

Stagging wipe test is not responding; status offline, last seen 8 days 12 hours ago.

Server details

Which location does Stagging wipe test run from?

No region comes from Stagging wipe test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 37.30.52.103:28015.

What Rust version is Stagging wipe test on?

Version check: Rust network protocol 2635 and build 168739 on Windows, run by Stagging wipe test. To get in, your game needs the same protocol; Steam applies the update.

How reliable is Stagging wipe test, and is it online now?

Stagging wipe test reports offline. The last reading came 8 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 21 October 2026, recorded by Rust Metrics.

Map and rules

What rules does Stagging wipe test enforce, and what are its settings?

Check: gather rate. The name Stagging wipe test does not state one. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is Stagging wipe test on?

Check: map. Procedural, generated by the game, on Stagging wipe test.

How to join

How do you connect to Stagging wipe test?

Press F1 in Rust and enter client.connect 37.30.52.103:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^m,gmvanilla,cs168739,sc2,ts8

Game

gmvanilla
Game mode The mode is vanilla survival.
mp50
Max players 50 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168739
Build Game build reading: 168739.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Facepunch's force wipe sets the monthly cycle here.

Other

sc2
Custom tag This tag is non-standard, added by the owner or a plugin.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.