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
37/ 100
F
Slipped a little: down 3,415 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.
AveragePeak
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
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
Next wipe Thursday 5 November, 19:00 UTC, in 6d 23h.
The 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
The NA tag on Old Dad's 2x Solo/Duo 3.0 puts it in North America. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 97.242.125.192:28015.
How reliable is Old Dad's 2x Solo/Duo 3.0, and is it up?
The server is down: Old Dad's 2x Solo/Duo 3.0 is offline now, with the last sighting 39 days 18 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 19 September 2026, Rust Server Score saw it for the first time.
On what Rust version does Old Dad's 2x Solo/Duo 3.0 sit?
Rust network protocol 2633 and build 163794 on Windows is what Old Dad's 2x Solo/Duo 3.0 runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does Old Dad's 2x Solo/Duo 3.0 wipe, and how often?
the force wipe gives the basis for estimating Old Dad's 2x Solo/Duo 3.0's next wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. It has been running its current world for 45 days 19 hours. Its tags list a monthly wipe schedule.
Population
What position does Old Dad's 2x Solo/Duo 3.0 hold in the rankings?
In North America, Old Dad's 2x Solo/Duo 3.0 is #1,463, and overall it is #13,319 on player hours over the last seven days, in the top – of all ranked servers.
What does the population on Old Dad's 2x Solo/Duo 3.0 look like?
Old Dad's 2x Solo/Duo 3.0 is offline at the moment; the last time it was seen was 39 days 18 hours ago.
Tags
How should you read the tags on Old Dad's 2x Solo/Duo 3.0?
The game's browser takes its cue from the tags Old Dad's 2x Solo/Duo 3.0 has set: gmvanilla (Game mode): Survival, vanilla style; mp50 (Max players): 50 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): Join only if your game runs protocol 2633; cs163794 (Build): Build number: 163794; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; NA (North America): You will find it under North America in the browser. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature Old Dad's 2x Solo/Duo 3.0?
Rust Server Score lists that include Old Dad's 2x Solo/Duo 3.0: 2x Rust servers, graded, Modded Rust servers, graded and North America Rust servers, graded. You can find it under these server-list filters: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 2x.
Server rules
Which rules does Old Dad's 2x Solo/Duo 3.0 enforce, and what are its settings?
Old Dad's 2x Solo/Duo 3.0 sets gather at 2x, as its name suggests. The default of 8 players applies as the group cap. survival is the mode here, 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. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Which map is in play on Old Dad's 2x Solo/Duo 3.0?
Old Dad's 2x Solo/Duo 3.0 runs a procedural map, which the game generates.
How to join
What is the way to join Old Dad's 2x Solo/Duo 3.0?
To connect, start Rust, press F1, and type client.connect 97.242.125.192:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,^m,NA,gmvanilla,cs163794,ts8,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp50
Max players50 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163794
BuildBuild number: 163794.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Region
NA
North AmericaYou will find it under North America in the browser.
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.