Not ranked yet, so there is no place in the school to report.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 382 places this week. Nothing a good wipe can't fix.
A term to build on.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
RankRank in region
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W·WW
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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 UTC41d 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
classmates: the same kind of game, then region, group limit, rate and wipes
perf-tests-local leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 91.1.111.20:28185 is the address to use.
Is perf-tests-local up, and how steady is its uptime?
The server is down: perf-tests-local is offline now, with the last sighting 38 days 16 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 16 September 2026, Rust Server Score saw it for the first time.
Which Rust version is perf-tests-local running?
Rust network protocol 2633 and build 163493 on Windows is what perf-tests-local runs. Steam updates your game for you, but you need the same protocol to join.
Resets
When does perf-tests-local wipe, and how often?
No next wipe can be predicted for perf-tests-local, which wipes at irregular times. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 38 days 16 hours have passed since this world was made.
What happens on perf-tests-local when wipe day arrives?
The average peak on its recent wipes was 0 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does perf-tests-local sit among Rust servers?
In the top – of all ranked servers, perf-tests-local sits at #15,516 for player hours over the last seven days.
What does the population on perf-tests-local look like?
The last sighting of perf-tests-local was 38 days 16 hours ago, and it is offline right now.
Tags
What is meant by the tags on perf-tests-local?
You'll see perf-tests-local tagged with gmrust (Game mode): Survival in the standard Rust style; mp0 (Max players): Its slot count is 0; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs163493 (Build): Build number: 163493; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does perf-tests-local appear in the Rust Server Score lists and filters?
These Rust Server Score lists count perf-tests-local among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
What settings and rules apply on perf-tests-local?
You will find no gather rate in the name of perf-tests-local. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map perf-tests-local uses?
The game generates a procedural map for perf-tests-local.
Connecting
How do you get onto perf-tests-local?
To connect, start Rust, press F1, and type client.connect 91.1.111.20:28185. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp0,ptrak,$r?,v2633,gmrust,cs163493,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp0
Max playersIts slot count is 0.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163493
BuildBuild number: 163493.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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.
A term to build on.