Rust Server TrendsSeismic network · station log
Recording Stations11,535 Players86,112 Active4,004 Wipes · 3 h131 48 h

Station XX-15470 · no signal

Parity check (local test)

Offline 77.21.168.254:28915 checked 11d ago

Connect
Players now
0/ 500
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,470
top 71%
Last wipe
11d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15470 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 500 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k10 Nov11 Nov13 Nov14 Nov16 Nov17 Nov

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

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak
0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 10 Nov, 03:59 UTC11d ago M0.0steady 0 – running 0

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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 403 on average
591/ 600
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 295 on average
591/ 600
Rusty Moose |US Monthly| NA · groups of 12+ · monthly · 275 on average
119/ 200
Rustoria.co - EU Long EU · groups of 14+ · monthly · 248 on average
252/ 250
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 233 on average
75/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 232 on average
580/ 600
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Parity check (local test)?

The map on Parity check (local test) is procedural, produced by the game.

Which settings and rules apply on Parity check (local test)?

No gather rate appears in the name of Parity check (local test). At the game's default, groups can have up to 8 players. survival is the game mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Under Community in the server browser, it runs as a community server. VAC, Valve's anti-cheat, is switched off.

Player counts

What is the current population on Parity check (local test)?

No players are recorded on Parity check (local test) at this moment; it is offline, and the last sighting was 11 days 8 hours ago.

How does Parity check (local test) rank against other Rust servers?

The last seven days of player hours place Parity check (local test) at #15,470, in the top 71% of all ranked servers.

Server details

How reliably does Parity check (local test) stay online?

Parity check (local test) is down at the moment; the last recorded contact was 11 days 8 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 10 November 2026 it was recorded for the first time by Rust Server Trends.

Which region does Parity check (local test) run from?

No region is published by Parity check (local test). Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 77.21.168.254:28915 is the address it uses.

What build of Rust does Parity check (local test) use?

Parity check (local test) is running Rust network protocol 2636 on a machine with macOS. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

What does wipe day look like on Parity check (local test)?

0 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 0 hours after the wipe.

On what timetable does Parity check (local test) run its wipes?

Too few wipes of Parity check (local test) are on record yet to show its rhythm. On Thursday 3 December at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 11 days 9 hours.

Server tags

What do the server tags on Parity check (local test) mean?

The game's server browser reads the tags Parity check (local test) publishes: gmrust (Game mode): The game mode is standard Rust survival; mp500 (Max players): The server has 500 slots; ts8 (Group limit): This uses the game default of 8 per team; v2636 (Protocol): To connect, your game must be on the same protocol, 2636; cs (Build): You won't find a published build number; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does Parity check (local test) appear?

You will find Parity check (local test) on the following Rust Server Trends lists: 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; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How to join

How do you connect to Parity check (local test)?

You can connect by pressing F1 in Rust and typing client.connect 77.21.168.254:28915 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp500,ptrak,$r?,v2636,gmrust,cs,ts8

Game

gmrust
Game mode The game mode is standard Rust survival.
mp500
Max players The server has 500 slots.
ts8
Group limit This uses the game default of 8 per team.
v2636
Protocol To connect, your game must be on the same protocol, 2636.
cs
Build You won't find a published build number.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is set for this server.

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.

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.