Working its way up from the back of the class: #15,102 on player hours.
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
52/ 100
D
Moving up: up 687 places this week.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
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.
No daily history yet.
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
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
No hourly players around its wipes yet.
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
Fri 16 Oct, 13:02 UTC11d ago
0
–
running
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
PVE2200 LOCAL CANDIDATE leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 112.149.91.140:28125.
Is PVE2200 LOCAL CANDIDATE up, and how steady is its uptime?
At this moment, PVE2200 LOCAL CANDIDATE is offline; the last time it was seen was 11 days 5 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 16 October 2026, Rust Server Score saw it for the first time.
What Rust version is PVE2200 LOCAL CANDIDATE on?
The server PVE2200 LOCAL CANDIDATE is on Rust network protocol 2634 and build 167781 under Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
When does PVE2200 LOCAL CANDIDATE wipe, and how often?
PVE2200 LOCAL CANDIDATE has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 11 days 5 hours have passed since this world was made.
What happens on PVE2200 LOCAL CANDIDATE when wipe day arrives?
Recent wipes have peaked at 0 players on average. 0 hours after the latest wipe began, the crowd hit its peak.
Player numbers
What position does PVE2200 LOCAL CANDIDATE hold in the rankings?
In the top 70% of all ranked servers, PVE2200 LOCAL CANDIDATE sits at #15,102 for player hours over the last seven days.
How many players does PVE2200 LOCAL CANDIDATE usually have?
The last sighting of PVE2200 LOCAL CANDIDATE was 11 days 5 hours ago, and it is offline right now.
Lists and filters
What do PVE2200 LOCAL CANDIDATE's tags stand for?
The game's browser takes its cue from the tags PVE2200 LOCAL CANDIDATE has set: gmrust (Game mode): Survival in the standard Rust style; mp4 (Max players): The server holds 4 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): This runs on build 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set. 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 PVE2200 LOCAL CANDIDATE appear in the Rust Server Score lists and filters?
These Rust Server Score lists count PVE2200 LOCAL CANDIDATE among them: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Rules and settings
How is PVE2200 LOCAL CANDIDATE set up, and what rules does it keep?
Nothing in the name of PVE2200 LOCAL CANDIDATE states a gather rate. 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. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map PVE2200 LOCAL CANDIDATE uses?
PVE2200 LOCAL CANDIDATE runs a procedural map, which the game generates.
How to join
What is the way to join PVE2200 LOCAL CANDIDATE?
To connect, start Rust, press F1, and type client.connect 112.149.91.140:28125. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp4,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp4
Max playersThe server holds 4 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been 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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).