Working its way up from the back of the class: #15,106 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
32/ 100
F
Lost ground: down 5,575 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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.
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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 1 Oct. 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, top 87% in OC. 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
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 6d 22h.
The force wipe · high confidence
wipe-day peak2players, last three wipes
Coming wipes
6d 22hThu 5 Nov, 19:00 UTCFW
34d 22hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 3 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 16:48 UTC28d ago
2
–
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
Which region is RetroPVE (Testing Server) based in?
You'll see RetroPVE (Testing Server) listed in Oceania, tagged OC. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 123.50.149.73:28015.
Is RetroPVE (Testing Server) up, and how steady is its uptime?
The server is down: RetroPVE (Testing Server) is offline now, with the last sighting 13 days 2 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 28 September 2026.
On what Rust version does RetroPVE (Testing Server) sit?
The server RetroPVE (Testing Server) is on Rust network protocol 2634 and build 166494 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does RetroPVE (Testing Server) wipe its map?
Once a month, RetroPVE (Testing Server) wipes with the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. It has been running its current world for 28 days 2 hours. Its tags record that it wipes monthly.
What happens on RetroPVE (Testing Server) when wipe day arrives?
Recent wipes have peaked at 2 players on average. Peak numbers came 3 hours into the latest wipe.
Player numbers
What position does RetroPVE (Testing Server) hold in the rankings?
Over the last seven days, RetroPVE (Testing Server) has #15,106 for player hours, in the top 70% of all ranked servers and #186 in Oceania.
What does the population on RetroPVE (Testing Server) look like?
The last sighting of RetroPVE (Testing Server) was 13 days 2 hours ago, and it is offline right now.
Lists and filters
What is meant by the tags on RetroPVE (Testing Server)?
gmvanilla (Game mode): You play vanilla survival here; mp100 (Max players): Its slot count is 100; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): Join only if your game runs protocol 2634; cs166494 (Build): Build number: 166494; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: Carbon; OC (Oceania): The server browser lists it under Oceania are the tags RetroPVE (Testing Server) publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature RetroPVE (Testing Server)?
These Rust Server Score lists count RetroPVE (Testing Server) among them: Oceania Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Region: Oceania; Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.
Map and rules
How is RetroPVE (Testing Server) set up, and what rules does it keep?
The name of RetroPVE (Testing Server) gives no gather rate. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map RetroPVE (Testing Server) uses?
The game generates the procedural map on RetroPVE (Testing Server), at size 5,000.
Getting in
How should you connect to RetroPVE (Testing Server)?
Enter client.connect 123.50.149.73:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^z,^y,^m,OC,gmvanilla,cs166494,ts8
Game
gmvanilla
Game modeYou play vanilla survival here.
mp100
Max playersIts slot count is 100.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166494
BuildBuild number: 166494.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonPlugin framework: Carbon.
Region
OC
OceaniaThe server browser lists it under Oceania.
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. Even marks across the subjects, from F to F.