RUST METRICSFlight deck · live data
Data live Servers11,828 Players91,106 Populated3,754 Fresh wipes 3 h433 Scan5 min
‹ All servers31.132.219.234:28015
Offline Full Queue Fresh wipe Wipe due No query

pavserv137

Offline 31.132.219.234:28015 checked 8d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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,432top 69%
Last wipe17d agono schedule published
Next wipe–no wipe 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k15 Oct18 Oct20 Oct23 Oct25 Oct28 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

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 wipe timing does pavserv137 follow?

The rhythm of pavserv137's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 17 days 4 hours ago the current world was made.

Tag meanings

Which tags does pavserv137 carry, and what do they mean?

Tags published by pavserv137, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; 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): Build 167398; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. 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?

On Rust Metrics, pavserv137 sits in these lists: 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

Where does pavserv137 sit in the rankings?

Player hours over seven days put pavserv137 at #15,432, in the top 69% of all ranked servers.

What player count does pavserv137 carry?

Status for pavserv137: offline. Last seen 8 days 8 hours ago.

Server

What location is pavserv137 hosted in?

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

What Rust version is pavserv137 on?

Version check: Rust network protocol 2634 and build 167398 on Windows, run by pavserv137. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on pavserv137, and is it online?

Check: connection. pavserv137 is offline at this moment. Last contact was 8 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 15 October 2026, recorded by Rust Metrics.

Rules and settings

What rules does pavserv137 enforce, and what are its settings?

Check: gather rate. The name pavserv137 does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC off, Valve's system.

Which map is live on pavserv137?

Procedural map on pavserv137, made by the game's generator.

Connection

How can you get onto pavserv137?

Check: join. Open Rust, press F1, then enter client.connect 31.132.219.234:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
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 Build 167398.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.