pgm3
Offline 213.55.156.63:28015 checked 17d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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- 244/300
- 16/250
- 32/250
- 120/200
- 47/200
- 53/100
Quick answers
from the figures on this pageReset cycle
What wipe timing does pgm3 follow?
The rhythm of pgm3's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 17 days 4 hours ago the current world was made.
Lists and filters
Which tags does pgm3 carry, and what do they mean?
These are the tags pgm3 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): Slots: 500; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167398 (Build): Build 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show pgm3?
These Rust Metrics lists carry pgm3: 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.
Player count
What position does pgm3 hold among Rust servers?
Ranking for pgm3: #13,635 on seven-day player hours, top 62% of all ranked servers.
What is the population on pgm3?
Status for pgm3: offline. Last seen 17 days 2 hours ago.
Server details
Where does pgm3 sit?
No region comes from pgm3. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 213.55.156.63:28015.
What Rust version is pgm3 on?
Version check: Rust network protocol 2634 and build 167398 on Windows, run by pgm3. To get in, your game needs the same protocol; Steam applies the update.
How reliable is pgm3, and is it online now?
pgm3 reports offline. The last reading came 17 days 2 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 10 October 2026.
Map and rules
What rules does pgm3 enforce, and what are its settings?
No gather rate appears in the name: pgm3. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.
Which map is live on pgm3?
Check: map. Procedural, generated by the game, on pgm3.
Connection
How can you get onto pgm3?
Press F1 in Rust and enter client.connect 213.55.156.63:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.