pavserv137
Offline 31.132.219.207:28015 checked 15d ago
Server instruments
no direct query in 48 hoursPlayers now
20% 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, measured since 11 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 54% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot 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 2, 2 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 12 Oct, 16:30 UTC16d ago | 2 | – | running | 2 |
| Sun 11 Oct, 15:09 UTC17d ago | 2 | – | 1.1 days | 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- 513/525
- 409/450
- 52/250
- 55/250
- 57/100
- 153/200
Quick answers
from the figures on this pageWipe timing
What happens on pavserv137 when wipe day comes?
An average of 2 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 2 hours in.
How often does pavserv137 wipe, and when?
The rhythm of pavserv137'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. The world in play was created 16 days 20 hours ago.
Tags
How should you read the tags on pavserv137?
Tags published by pavserv137, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167398 (Build): Game build reading: 167398; ptrak (Networking): Network layer: RakNet, the standard for the game; $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 pavserv137?
Rust Metrics lists featuring pavserv137: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
What position does pavserv137 hold among Rust servers?
Ranking for pavserv137: #11,605 on seven-day player hours, top 54% of all ranked servers.
What is the population on pavserv137?
Reading for pavserv137: offline at this moment; last seen 15 days 16 hours ago.
Operator and location
What location is pavserv137 hosted in?
Reading: location. pavserv137 gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 31.132.219.207:28015.
What Rust version is pavserv137 on?
Version check: Rust network protocol 2634 and build 167398 on Windows, run by pavserv137. Matching protocol is required to join. Let Steam update your game.
How reliable is pavserv137, and is it online now?
pavserv137 reports offline. The last reading came 15 days 16 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 11 October 2026.
Rules and settings
How is pavserv137 configured, and what rules are in force?
No gather rate appears in the name: pavserv137. No limit is set beyond the default. Groups take up to 8 players. 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. VAC is on. That is Valve's anti-cheat.
Which map is live on pavserv137?
From seed 763952, the game generates the procedural map on pavserv137. Its size is 3,500. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
Connection
How do you connect to pavserv137?
Check: join. Open Rust, press F1, then enter client.connect 31.132.219.207:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.