Working its way up from the back of the class: #15,471 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
51/ 100
D
Moving up: up 379 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.
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 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
No region is published for Old Dad's PVE Whitelist. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 64.87.39.225:25642.
Is Old Dad's PVE Whitelist up, and how steady is its uptime?
You cannot join now: Old Dad's PVE Whitelist is offline, last seen 42 days 16 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 15 September 2026, Rust Server Score saw it for the first time.
Which Rust version is Old Dad's PVE Whitelist running?
Rust network protocol 2633 and build 163493 on Linux is what Old Dad's PVE Whitelist runs. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does Old Dad's PVE Whitelist wipe its map?
There are too few wipes on record for Old Dad's PVE Whitelist to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 49 days 14 hours have passed since this world was made.
Player count
Where does Old Dad's PVE Whitelist place in the wider field of Rust servers?
In the top 71% of all ranked servers, Old Dad's PVE Whitelist sits at #15,471 for player hours over the last seven days.
What does the population on Old Dad's PVE Whitelist look like?
It has been 42 days 16 hours since Old Dad's PVE Whitelist was last seen, and it is offline right now.
Tags and filters
How should you read the tags on Old Dad's PVE Whitelist?
You'll see Old Dad's PVE Whitelist tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp500 (Max players): The server holds 500 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs163493 (Build): Build number: 163493; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded 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.
Which lists and filters on Rust Server Score show Old Dad's PVE Whitelist?
These Rust Server Score lists count Old Dad's PVE Whitelist among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
How is Old Dad's PVE Whitelist set up, and what rules does it keep?
You will find no gather rate in the name of Old Dad's PVE Whitelist. The group limit stays at the game's default of 8 players. You get survival 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.
Old Dad's PVE Whitelist runs which map?
A procedural map, generated by the game, is what Old Dad's PVE Whitelist runs.
Connecting
How do you get onto Old Dad's PVE Whitelist?
Enter client.connect 64.87.39.225:25642 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 asmp500,ptrak,$r?,v2633,gmrust,cs163493,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp500
Max playersThe server holds 500 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs163493
BuildBuild number: 163493.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits 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 momentum (D); standing is the one to work on (F).