Station XX-15516 · no signal
perf-tests-local
Offline 91.1.111.20:28185 checked 62d ago
- Players now
- 0/ ?
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,516
- no region published
- Last wipe
- 62d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of ? 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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestWipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 1.6 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 5 Nov, 19:00 UTC FW15d ago | – | – | – | – | running | – |
| Thu 1 Oct, 18:00 UTC FW50d ago | – | – | – | – | – | – |
| Sun 20 Sep, 11:00 UTC62d ago | M0.0■steady | 0 | – | – | – | 0 |
| Sat 19 Sep, 13:35 UTC62d ago | M0.0■steady | 0 | – | 0.9 days | 0 | |
| Thu 17 Sep, 06:31 UTC65d ago | M0.0■steady | 0 | – | 2.3 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 pageServer rules
Which map is running on perf-tests-local?
The map on perf-tests-local is procedural, produced by the game.
Which settings and rules apply on perf-tests-local?
The name of perf-tests-local gives no gather rate. The group limit is 8 players, the game's default. In survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Under Community in the server browser, it runs as a community server. VAC, Valve's anti-cheat, is switched on.
Live population
What is the current population on perf-tests-local?
A reading taken now finds perf-tests-local offline; the most recent activity was 62 days 1 hours ago.
How does perf-tests-local rank against other Rust servers?
Over the last seven days, perf-tests-local recorded enough player hours to reach #15,516 worldwide, placing it in the top – of all ranked servers.
Server facts
How reliably does perf-tests-local stay online?
No contact with perf-tests-local right now, and the last recorded contact was 62 days 1 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 16 September 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is perf-tests-local hosted?
A region is not published by perf-tests-local. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 91.1.111.20:28185.
Which Rust version is perf-tests-local running?
perf-tests-local is running Rust network protocol 2633 and build 163493 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on perf-tests-local?
0 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 0 hours after the wipe.
On what timetable does perf-tests-local run its wipes?
There is no next wipe to predict at perf-tests-local, since its wipes fall at irregular times. On Thursday 3 December at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 62 days 2 hours is how long the current world has been running.
Lists and tags
What do the server tags on perf-tests-local mean?
These are the tags perf-tests-local publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp0 (Max players): 0 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs163493 (Build): It runs game build 163493; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does perf-tests-local appear?
These Rust Server Trends lists include perf-tests-local: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Connecting
How do you connect to perf-tests-local?
You can connect by pressing F1 in Rust and typing client.connect 91.1.111.20:28185 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects 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.