Station XX-11605 · no signal
pavserv137
Offline 31.132.219.207:28015 checked 15d ago
- Players now
- 2/ 10
- 20% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #11,605
- top 54%
- Last wipe
- 16d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 2of 10 slots
- Motion · 24 h
- M –not enough readings
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, 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.
- usual gap
- 1.1 daysbetween real wipes
- wipe-day peak
- 2players, last three wipes
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 12 Oct, 16:30 UTC16d ago | M0.0■steady | 2 | – | running | 2 | |
| Sun 11 Oct, 15:09 UTC17d ago | M0.3▲rising | 2 | – | 1.1 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which map is running on pavserv137?
pavserv137 runs a procedural map of size 3,500 with seed 763952, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on pavserv137?
The name of pavserv137 gives no gather rate. The group limit is 8 players, the game's default. survival is the game mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. It is a community server, and the browser lists it under Community. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on pavserv137 right now?
pavserv137 is not responding at this moment and is offline, last seen 15 days 15 hours ago.
How does pavserv137 rank against other Rust servers?
Over the last seven days, pavserv137 recorded enough player hours to reach #11,605 worldwide, placing it in the top 54% of all ranked servers.
Operator and location
How reliably does pavserv137 stay online?
pavserv137 is down at the moment; the last recorded contact was 15 days 15 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 11 October 2026 it was recorded for the first time by Rust Server Trends.
Which region does pavserv137 run from?
Nothing about a region comes from pavserv137. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 31.132.219.207:28015.
What build of Rust does pavserv137 use?
pavserv137 is running Rust network protocol 2634 and build 167398 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on pavserv137?
On average, the busiest point of its recent wipes drew 2 players. 2 hours after the latest wipe, the crowd peaked.
How often does pavserv137 wipe, and on which days?
The rhythm of pavserv137 cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 16 days 19 hours.
Tags
What do the server tags on pavserv137 mean?
The game's server browser reads the tags pavserv137 publishes: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): Slots: 10; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167398 (Build): It runs game build 167398; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does pavserv137 appear?
These Rust Server Trends lists include pavserv137: Rust community servers without the side modes. 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.
Join the server
What steps get you onto pavserv137?
To join, enter client.connect 31.132.219.207:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.