Rust Data LabData lab · live
Live readings Servers11,695 Players53,611 Populated3,212 Fresh wipes · 3h134 Sampled every 5 min

Element card · group Community · atomic number 15,516, its rank

perf-tests-local

Offline 91.1.111.20:28185 checked 38d ago

Join the experiment
Atomic mass · players now 0/ ?
7-day average0peak –
Rank · atomic number#15,516no region published
Last wipe38d agono schedule published
Next wipe–no rhythm it keeps
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
No hourly history yet.

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k20 Sep21 Sep23 Sep24 Sep26 Sep27 Sep
Reaction kinetics

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.

Reaction 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Ru Rusty Moose |E… 361
    Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 519 on average 361/ 400
  2. 2 Ru Rustoria.co - … 336
    Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average 336/ 350
  3. 3 Ru Rusty Moose |E… 38
    Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average 38/ 250
  4. 4 Ru Rustoria.co - … 32
    Rustoria.co - EU Main EU · groups of 16+ · weekly · 276 on average 32/ 250
  5. 5 Ru Rustafied.com … 48
    Rustafied.com - EU Friday EU · groups of 16+ · weekly · 275 on average 48/ 100
  6. 6 Ru Rustoria.co - … 175
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 244 on average 175/ 200

Quick answers

from the figures on this page

Map and rules

What map is in play on perf-tests-local?

Generated by the game, the map on perf-tests-local is procedural.

How is perf-tests-local configured, and what rules apply?

Nothing in the name of perf-tests-local gives a gather rate. Groups top out at 8 players, the default for the game. survival is the game mode, gather, build and raid, as in the standard game. Raids and player fights are part of play here. You will find it under Community in the server browser. VAC is on, Valve's anti-cheat.

Server details

Which location is perf-tests-local based in?

No region is published by perf-tests-local. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. Connect at 91.1.111.20:28185.

On what Rust version does perf-tests-local operate?

On Windows, perf-tests-local is running Rust network protocol 2633 and build 163493. The protocol must match for you to join; Steam will update your game.

How reliably does perf-tests-local stay online?

Currently offline, perf-tests-local was last seen 38 days 22 hours ago. For the last 7 full days, 0 of 168 hours were online, giving 0% uptime. The first sighting by Rust Data Lab was on 16 September 2026.

Wipe schedule

What is the wiping pattern on perf-tests-local?

There is no next wipe to predict for perf-tests-local, which wipes at irregular times. A monthly force wipe happens on every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world it is running now dates from 38 days 23 hours ago.

How does perf-tests-local look on the day of a wipe?

Recent wipes on average reached 0 players at their busiest. The latest wipe's peak fell 0 hours after it began.

Lists and tags

What should you understand from the tags perf-tests-local carries?

These are the tags perf-tests-local makes public for the server browser to read: gmrust (Game mode): Standard Rust survival is the game here; mp0 (Max players): It has 0 slots; ts8 (Group limit): 8 per team, the default the game ships with; v2633 (Protocol): Protocol 2633 is required; join only if your game matches it; cs163493 (Build): Build number: 163493; ptrak (Networking): This runs on RakNet, the standard layer; $r? (Region code): No region code is set. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.

Where among the Rust Data Lab lists and filters does perf-tests-local come up?

The Rust Data Lab lists that include perf-tests-local are: Rust community servers, measured. You can find it on the server list by applying these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Against other Rust servers, where does perf-tests-local place?

Player hours over the last week put perf-tests-local at #15,516, inside the top – of ranked servers.

How many players does perf-tests-local have at the moment?

The last recorded sighting of perf-tests-local was 38 days 22 hours ago, and it is offline now.

Getting on

What steps get you onto perf-tests-local?

In Rust, press F1 and enter client.connect 91.1.111.20:28185. Or click Launch Rust here to open Rust via Steam and connect automatically.

Server tags

what each one means

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

Game

gmrust
Game mode Standard Rust survival is the game here.
mp0
Max players It has 0 slots.
ts8
Group limit 8 per team, the default the game ships with.
v2633
Protocol Protocol 2633 is required; join only if your game matches it.
cs163493
Build Build number: 163493.
ptrak
Networking This runs on RakNet, the standard layer.
$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.