Parity check (local test)
Key statistics
the figures behind the quote- Players now
- 0/ 500 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #16,102 top 70%
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 2d ago no schedule published
- Next wipe
- – too few wipes seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 10 Nov 2026 no hostname published
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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yet- wipe-day peak
- 0 players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Tue 10 Nov, 03:59 UTC2d ago | 0 | – | running | 0 |
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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | Rusty Moose |EU Monthly|EU · groups of 12+ · monthly · 579 on average | 648/675 | ▼−146−18.4% | |
| 2 | Rusty Moose |US Monthly|NA · groups of 12+ · monthly · 567 on average | 213/200 | ▼−143−40.2% | |
| 3 | Rustoria.co - EU East LongEU · groups of 12+ · monthly · 527 on average | 580/600 | ▼−12−2.1% | |
| 4 | Rustoria.co - EU LongEU · groups of 14+ · monthly · 461 on average | 483/500 | ▼−49−9.3% | |
| 5 | Magic Rust — Long | Kлaccикa x1 | PyccкийEU · groups of 150+ · 1x · monthly · 447 on average | 464/480 | ▲+5+1.1% | |
| 6 | Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 401 on average | 460/525 | ▼−109−19.1% |
Quick answers
from the figures on this pageMap and Rules
How is Parity check (local test) configured in terms of rules and settings?
No gather rate is given in the name of Parity check (local test). The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. The server browser lists it under Community, as a community server. The server has VAC, Valve's anti-cheat, switched off.
What is the current map on Parity check (local test)?
Parity check (local test) uses a procedural map, which the game generates.
Population
Where does Parity check (local test) sit in the rankings?
In the top 70% of all ranked servers, Parity check (local test) is #16,102 on player hours over the last seven days.
How many players does Parity check (local test) have?
At present, Parity check (local test) is offline; the last sighting was 2 days 11 hours ago. Average players over the last seven days: 0.
Wipe Cycle
What can you expect on wipe day for Parity check (local test)?
An average of 0 players marked the busiest point of its recent wipes. 0 hours after the latest wipe, the crowd reached its peak.
On what cycle does Parity check (local test) wipe?
There are too few wipes on record for Parity check (local test) to reveal its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 3 December at 19:00 UTC. This world has been running for 2 days 12 hours.
Server Overview
What is the location of Parity check (local test)?
There is no region published for Parity check (local test). Rust Analytics reports the location a server claims, not the machine's actual location. You can reach it at 77.21.168.254:28915.
What Rust version is Parity check (local test) running?
Rust network protocol 2636 on macOS is what Parity check (local test) runs. Joining requires the same protocol on your game, which Steam updates.
How reliable is Parity check (local test) and is it currently online?
No response from Parity check (local test). It was last seen 2 days 11 hours ago. Availability of 0% over the last 1 full day: it was online for 0 of 24 hours. The earliest Rust Analytics saw it was 10 November 2026.
Tags and Rankings
How should you interpret the tags on Parity check (local test)?
Published by Parity check (local test) for the game's server browser to read: gmrust (Game mode): Rust's standard survival mode; mp500 (Max players): Slot count: 500; ts8 (Group limit): 8 per team: the default setting, unchanged; v2636 (Protocol): Protocol 2636: matching game versions are required to join; cs (Build): No build figure is given; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): The region code is absent. The top of this page and the tags both show its players now, its queue and when its world was made.
Parity check (local test) appears in which of the lists and filters on Rust Analytics?
These Rust Analytics lists include Parity check (local test): Rust community servers. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.
Connection
How can I connect to Parity check (local test)?
Type client.connect 77.21.168.254:28915 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp500,ptrak,$r?,v2636,gmrust,cs,ts8
Game
gmrust
mp500
ts8
v2636
cs
ptrak
$r?
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.