A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
50/ 100
D
Working its way up from the back of the class: #11,137 on player hours.
Uptimehours on the list, last 48
88/ 100
A−
Good attendance: on the list 42 of the last 48 hours.
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
17/ 100
F
Lost ground: down 7,263 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in uptime (A−); population 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.
AveragePeak
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
Top 50% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
10 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
W····WW
WWWWWW·
·······
····
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 gap0.5 daysbetween real wipes
on rhythm75%of its recent wipes
wipe-day peak4players, last three wipes
The first 48 hours of its last wipes
Sat 17 OctSat 17 OctFri 16 Oct
Players each hour, from the hour of the wipe. The latest peaked at 4, 18 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 17 Oct, 12:00 UTC11d ago
4
–
running
0
Sat 17 Oct, 05:45 UTC11d ago
4
–
0.3 days
1
Fri 16 Oct, 16:50 UTC12d ago
4
–
0.5 days
1
Fri 16 Oct, 04:15 UTC12d ago
3
–
0.5 days
0
Thu 15 Oct, 04:48 UTC13d ago
3
–
1 days
0
Wed 14 Oct, 15:32 UTC14d ago
1
–
0.6 days
0
Wed 14 Oct, 02:55 UTC14d ago
3
–
0.5 days
0
Tue 13 Oct, 15:43 UTC15d ago
3
–
0.5 days
2
Tue 13 Oct, 03:21 UTC15d ago
6
–
0.5 days
0
Mon 12 Oct, 03:30 UTC16d ago
6
–
1 days
2
Sun 11 Oct, 07:42 UTC17d ago
4
–
0.8 days
0
Sat 10 Oct, 02:20 UTC18d ago
4
–
1.2 days
1
Mon 5 Oct, 08:21 UTC23d ago
1
–
4.7 days
1
Sun 4 Oct, 21:33 UTC24d ago
1
–
0.5 days
0
Sun 4 Oct, 07:41 UTC24d ago
1
–
0.6 days
1
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 Flooded Playtest based in?
No region is published for RetroPVE Flooded Playtest. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 123.50.149.73:28017 is the address to use.
How reliable is RetroPVE Flooded Playtest, and is it up?
The server is down: RetroPVE Flooded Playtest is offline now, with the last sighting 5 hours ago. It was up 164 of 168 hours over the last 7 full days, which is 98% of the time. On 4 October 2026, Rust Server Score saw it for the first time.
Which Rust version is RetroPVE Flooded Playtest running?
The server RetroPVE Flooded Playtest is on Rust network protocol 2635 and build 167781 under Linux. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does RetroPVE Flooded Playtest reset?
There is no next wipe to predict on RetroPVE Flooded Playtest, as it wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 11 days 13 hours.
What should you expect from wipe day on RetroPVE Flooded Playtest?
Across its recent wipes, the busiest moments averaged 4 players. Peak numbers came 18 hours into the latest wipe.
Player numbers
Where does RetroPVE Flooded Playtest place in the wider field of Rust servers?
In the top 50% of all ranked servers, RetroPVE Flooded Playtest sits at #11,137 for player hours over the last seven days.
What does the population on RetroPVE Flooded Playtest look like?
The last sighting of RetroPVE Flooded Playtest was 5 hours ago, and it is offline right now. It peaked at 2 and averaged 0 players over the last seven days.
Tags and filters
What is meant by the tags on RetroPVE Flooded Playtest?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): 100 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs167781 (Build): This runs on build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags RetroPVE Flooded Playtest publishes, and the game's server browser reads them. 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 RetroPVE Flooded Playtest appear in the Rust Server Score lists and filters?
Rust Server Score lists that include RetroPVE Flooded Playtest: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Rules and settings
What settings and rules apply on RetroPVE Flooded Playtest?
You will find no gather rate in the name of RetroPVE Flooded Playtest. With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Getting in
How do you get onto RetroPVE Flooded Playtest?
Enter client.connect 123.50.149.73:28017 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?,v2635,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max players100 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
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 uptime (A−); population is the one to work on (F).