RUST METRICSFlight deck · live data
Data live Servers11,618 Players39,799 Populated2,961 Fresh wipes 3 h88 Scan5 min
‹ All servers91.1.111.20:28185
Offline Full Queue Fresh wipe Wipe due No query

perf-tests-local

Offline 91.1.111.20:28185 checked 38d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /?

Players now

no slots published 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,516no region published
Last wipe38d agono schedule published
Next wipe–no rhythm it keeps
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
15k10k15k20k20 Sep21 Sep23 Sep24 Sep26 Sep27 Sep
PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Sun 20 SepSat 19 SepThu 17 Sep
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 20 Sep, 11:00 UTC38d ago 0 – running 0
Sat 19 Sep, 13:35 UTC39d ago 0 – 0.9 days 0
Thu 17 Sep, 06:31 UTC42d ago 0 – 2.3 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.

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 timing

What should you expect from wipe day on perf-tests-local?

At their busiest, its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does perf-tests-local wipe, and when?

No next wipe can be predicted for perf-tests-local, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 38 days 20 hours ago the current world was made.

Tags

How should you read the tags on perf-tests-local?

Tags published by perf-tests-local, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp0 (Max players): 0 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163493 (Build): Game build reading: 163493; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is 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 perf-tests-local?

On Rust Metrics, perf-tests-local sits in these lists: 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.

Occupancy

What position does perf-tests-local hold among Rust servers?

Player hours over seven days put perf-tests-local at #15,516, in the top – of all ranked servers.

What player count does perf-tests-local carry?

Status for perf-tests-local: offline. Last seen 38 days 20 hours ago.

Server

Which location does perf-tests-local run from?

Reading: location. perf-tests-local gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 91.1.111.20:28185.

What Rust version is perf-tests-local on?

Version check: Rust network protocol 2633 and build 163493 on Windows, run by perf-tests-local. Matching protocol is required to join. Let Steam update your game.

Is perf-tests-local up, and how often does it stay up?

perf-tests-local reports offline. The last reading came 38 days 20 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 16 September 2026.

Rules and settings

How is perf-tests-local configured, and what rules are in force?

No gather rate appears in the name: perf-tests-local. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is perf-tests-local on?

Check: map. Procedural, generated by the game, on perf-tests-local.

Join

How can you get onto perf-tests-local?

To join: start Rust, press F1 and type client.connect 91.1.111.20:28185. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp0,ptrak,$r?,v2633,gmrust,cs163493,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp0
Max players 0 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163493
Build Game build reading: 163493.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is 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.