RUST METRICSFlight deck · live data
Data live Servers11,610 Players40,842 Populated2,876 Fresh wipes 3 h140 Scan5 min
‹ All servers82.22.20.131:28015
Offline Full Queue Fresh wipe Wipe due No query

Glitch Guard

Offline 82.22.20.131:28015 checked 10d ago

COM 1 · connect

Server instruments

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

Players now

0% 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#15,310top 70%
Last wipe18d agono schedule published
Next wipe–too few wipes seen yet
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, measured since 11 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k11 Oct14 Oct17 Oct20 Oct23 Oct26 Oct

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

PLAN

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 peak1players, 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 1, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 11 Oct, 16:45 UTC18d ago 1 – 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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on Glitch Guard?

An average of 1 players came at the busiest on its recent wipes. 1 hours after the wipe, the crowd peaked on the latest wipe.

When does Glitch Guard wipe?

Its rhythm cannot be told from the wipes of Glitch Guard on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 18 days 13 hours ago the current world was made.

Lists and filters

Which tags does Glitch Guard carry, and what do they mean?

These are the tags Glitch Guard publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): Build 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. 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 Glitch Guard?

These Rust Metrics lists carry Glitch Guard: 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; Group limit: 5 or more.

Occupancy

Where does Glitch Guard sit in the rankings?

Ranking for Glitch Guard: #15,310 on seven-day player hours, top 70% of all ranked servers.

What player count does Glitch Guard carry?

Reading for Glitch Guard: offline at this moment; last seen 10 days 21 hours ago.

Server details

Which location does Glitch Guard run from?

Reading: location. Glitch Guard gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 82.22.20.131:28015.

What Rust version is Glitch Guard on?

Version check: Rust network protocol 2634 and build 167398 on Windows, run by Glitch Guard. Matching protocol is required to join. Let Steam update your game.

How reliable is Glitch Guard, and is it online now?

Reading: offline. Glitch Guard last answered 10 days 21 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 11 October 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on Glitch Guard?

Reading the name gives no gather rate for Glitch Guard. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is Glitch Guard on?

Check: map. Procedural, size 3,000, seed 12345, generated by the game on Glitch Guard. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

What do you do to join Glitch Guard?

To join: start Rust, press F1 and type client.connect 82.22.20.131:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players The server holds 50 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build Build 167398.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.