RUST METRICSFlight deck · live data
Data live Servers11,615 Players36,329 Populated2,867 Fresh wipes 3 h57 Scan5 min
‹ All servers112.149.91.140:28125
Offline Full Queue Fresh wipe Wipe due No query

PVE2200 LOCAL CANDIDATE

Offline 112.149.91.140:28125 checked 11d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1 2 3 4 PAX 0 /4

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,102top 70%
Last wipe11d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k16 Oct17 Oct19 Oct20 Oct22 Oct23 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

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

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 13:02 UTC11d ago 0 – 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What should you expect from wipe day on PVE2200 LOCAL CANDIDATE?

The busiest point of its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does PVE2200 LOCAL CANDIDATE follow?

The rhythm of PVE2200 LOCAL CANDIDATE'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 it runs now was made 11 days 14 hours ago.

Lists and filters

How should you read the tags on PVE2200 LOCAL CANDIDATE?

Tags published by PVE2200 LOCAL CANDIDATE, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp4 (Max players): The server holds 4 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): The server runs game build 167781; 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 PVE2200 LOCAL CANDIDATE?

These Rust Metrics lists carry PVE2200 LOCAL CANDIDATE: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Occupancy

Where does PVE2200 LOCAL CANDIDATE sit in the rankings?

Ranking for PVE2200 LOCAL CANDIDATE: #15,102 on seven-day player hours, top 70% of all ranked servers.

What is the population on PVE2200 LOCAL CANDIDATE?

Reading for PVE2200 LOCAL CANDIDATE: offline at this moment; last seen 11 days 14 hours ago.

Operator and location

What location is PVE2200 LOCAL CANDIDATE hosted in?

No region comes from PVE2200 LOCAL CANDIDATE. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 112.149.91.140:28125.

What Rust version is PVE2200 LOCAL CANDIDATE on?

Reading: PVE2200 LOCAL CANDIDATE, Rust network protocol 2634 and build 167781, Windows. Matching protocol is required to join. Let Steam update your game.

Is PVE2200 LOCAL CANDIDATE up, and how often does it stay up?

PVE2200 LOCAL CANDIDATE reports offline. The last reading came 11 days 14 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 16 October 2026.

Map and rules

What rules does PVE2200 LOCAL CANDIDATE enforce, and what are its settings?

Reading the name gives no gather rate for PVE2200 LOCAL CANDIDATE. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is PVE2200 LOCAL CANDIDATE on?

Check: map. Procedural, generated by the game, on PVE2200 LOCAL CANDIDATE.

Connection

How do you connect to PVE2200 LOCAL CANDIDATE?

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

PLACARDS

Server tags

what each one means

Published as mp4,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp4
Max players The server holds 4 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build The server runs game build 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

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.