Offline 82.22.20.131:28015 checked 9d ago
Glitch Guard
Connect
srv = rust.server("82.22.20.131:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 11 Oct, 16:45 UTC16d ago | 1 | NaN | 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.
display(srv.map, srv.info())Map
3000 · seed 12345
- map
- Procedural Map
- size
- 3000
- seed
- 12345
Server
srv.info()- address
- 82.22.20.131:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 11 Oct 2026, 16:45 UTC
- hostname
- –
- first seen
- 11 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 540 on average | 544/575 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 361/400 |
| 2 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 314 on average | 36/250 |
| 3 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 313 on average | 44/250 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 273 on average | 157/200 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 265 on average | 77/100 |
Quick answers
From the figures on this page.
Population data
How does Glitch Guard compare in the rankings?
Player hours over seven days put Glitch Guard at #15,310, in the top 70% of the ranked set.
What population does Glitch Guard carry?
Glitch Guard returns no live count at this refresh, having last been seen 9 days 1 hours ago.
Server facts
Which Rust version is Glitch Guard on?
Version Rust network protocol 2634 and build 167398 on Windows is reported by Glitch Guard. Steam updates your game for you, but the protocol must match to join.
Is Glitch Guard up, and what does its uptime show?
Glitch Guard is offline at this refresh; the last response came 9 days 1 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 11 October 2026.
In which location is Glitch Guard hosted?
There is no region published for Glitch Guard. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 82.22.20.131:28015 is its address.
Settings and map
Which settings and rules does Glitch Guard run?
No gather rate appears in the name: Glitch Guard. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Community is its browser category. Anti-cheat status: VAC on.
Which map has Glitch Guard selected?
Glitch Guard runs a procedural map of size 3,000 with seed 12345, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does Glitch Guard wipe, and on what schedule?
Too few wipes are on record for Glitch Guard to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 16 days 17 hours ago.
On Glitch Guard, what happens on wipe day?
Recent wipes averaged 1 players at their peak. 1 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Where does Glitch Guard appear among Rust Data lists and filters?
On Rust Data, Glitch Guard appears in these lists: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the server tags on Glitch Guard?
Read by the game's server browser, the tags Glitch Guard publishes are: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to Glitch Guard?
In Rust, F1 opens the console: type client.connect 82.22.20.131:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.