Offline 91.1.111.20:28185 checked 38d ago
perf-tests-local
Connect
srv = rust.server("91.1.111.20:28187")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestWipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 20 Sep, 11:00 UTC38d ago | 0 | NaN | running | 0 |
| 1 | Sat 19 Sep, 13:35 UTC39d ago | 0 | NaN | 0.9 days | 0 |
| 2 | Thu 17 Sep, 06:31 UTC41d ago | 0 | NaN | 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 91.1.111.20:28185
- region
- –
- max players
- –
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 20 Sep 2026, 11:00 UTC
- hostname
- –
- first seen
- 16 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 549 on average | 137/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 125/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 14/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 284 on average | 18/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 12/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 249 on average | 35/200 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does perf-tests-local rank?
Rank #15,516 on seven-day player hours for perf-tests-local, within the top – of all ranked servers.
How full does perf-tests-local run?
perf-tests-local returns no live count at this refresh, having last been seen 38 days 17 hours ago.
About the server
What Rust version does perf-tests-local run?
Rust network protocol 2633 and build 163493 on Windows is what perf-tests-local runs. Joining needs the same protocol on your game; Steam handles the update.
Is perf-tests-local up, and what does its uptime show?
Offline now for perf-tests-local, last seen 38 days 17 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 16 September 2026.
Which location does perf-tests-local run from?
There is no region published for perf-tests-local. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 91.1.111.20:28185.
Rules, settings, map
Which rules apply on perf-tests-local, and what settings?
No gather rate appears in the name: perf-tests-local. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Community is its browser category. Anti-cheat status: VAC on.
Which map has perf-tests-local loaded?
The game generates its map: procedural, on perf-tests-local.
Wipes and dates
On what schedule does perf-tests-local wipe?
No next wipe can be predicted for perf-tests-local, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 38 days 17 hours ago.
On perf-tests-local, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Which lists on Rust Data hold perf-tests-local, and which filters?
On Rust Data, perf-tests-local appears in these lists: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on perf-tests-local hold?
Read by the game's server browser, the tags perf-tests-local publishes are: gmrust (Game mode): Rust survival in its standard form; mp0 (Max players): Slot count: 0; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs163493 (Build): Recorded game build: 163493; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way into perf-tests-local?
Enter client.connect 91.1.111.20:28185 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.