wipeguard test
Key statistics
the figures behind the quote- Players now
- 0/ 2 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,966 top 71%
- Rank · 7d ago
- #16,921 ▲955 places up
- Last wipe
- 8d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 100 max players per team
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 5 Oct 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 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
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 | ShockRust | Blue | NoLimitno group limit · 127 on average | 111/300 | ▼−44−28.3% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 107 on average | 120/225 | ▲+40+50.2% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 10.10EU · groups of 8+ · weekly · 90 on average | 92/100 | ▲+2+2.0% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 86 on average | 32/1000 | ▼−37−53.5% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 10/1000 | ▼−14−57.7% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 73 on average | 28/700 | ▼−70−71.4% |
Quick answers
from the figures on this pageMap and Rules
What settings and rules are in place on wipeguard test?
No gather rate appears in the name of wipeguard test. Group size is capped at 100 players. It runs survival, gather, build and raid in the standard game. PvP and raiding are enabled. Modded is its category in the server browser; plugins or settings modify the game. Carbon plugins are running. VAC, Valve's anti-cheat, is enabled.
Which map is played on wipeguard test?
wipeguard test uses a procedural map, which the game generates.
Activity
What position does wipeguard test hold in the server rankings?
In the top 71% of all ranked servers, wipeguard test is #15,966 on player hours over the last seven days.
How many players does wipeguard test have?
At present, wipeguard test is offline; the last sighting was 8 days 17 hours ago.
Wipe Cycle
How often does wipeguard test wipe?
The record holds too few of wipeguard test's wipes to establish its rhythm. The monthly force wipe applies to every Rust server. The next one falls on Thursday 5 November at 19:00 UTC. 8 days 17 hours ago the current world was created.
Server Overview
What is the location of wipeguard test?
No region is published by wipeguard test. Rust Analytics reports the location a server claims, not the machine's actual location. You can reach it at 78.84.160.95:28135.
wipeguard test runs which version of Rust?
The version in use at wipeguard test: Rust network protocol 2633 and build 164530, on Windows. Your game needs the same protocol to get in; Steam takes care of the update.
How reliable is wipeguard test and is it currently online?
No response from wipeguard test. It was last seen 8 days 17 hours ago. 0% is its uptime for the last 7 full days, 0 of 168 hours. 5 October 2026 is when Rust Analytics first saw it.
Tags & Filters
How should you interpret the tags on wipeguard test?
The game's server browser reads gmrust (Game mode): Rust's standard survival mode; mp2 (Max players): Capacity: 2 slots; ts100 (Group limit): 100 is the maximum team size; v2633 (Protocol): To join, your game needs protocol 2633; cs164530 (Build): Game build: 164530; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): The region code is absent; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework here is Carbon, which wipeguard test publishes. The tags also carry its current players, queue and world creation time; this page shows them at the top.
On Rust Analytics, which lists and filters feature wipeguard test?
On Rust Analytics, wipeguard test matches these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Joining the Server
What is the process to join wipeguard test?
The console route: start Rust, press F1, enter client.connect 78.84.160.95:28135. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp2,ptrak,$r?,v2633,gmrust,cs164530,ts100,^z,^y
Game
gmrust
mp2
ts100
v2633
cs164530
ptrak
$r?
Mods and access
^z
^y
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.