RUST METRICSFlight deck · live data
Data live Servers11,699 Players40,133 Populated2,984 Fresh wipes 3 h90 Scan5 min
‹ All servers66.51.99.87:28050
Online Full Queue Fresh wipe Wipe due No query

Old Dad's 2X Solo Only 2.0

Online NA 66.51.99.87:28050 checked 12m ago

2x solo monthly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Thu 00:00 UTC
0 12 25 38 50 PAX 6 /50

Players now

12% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 51 SERVER FPS

Server fps

48 h low 5 · below 20 is lag, below 10 is bad
0 100 200 300 400 ENT 211,639 ×1000

Entities

48 h range 188,078–217,869 · memory 5,331 MB
1239 ET SINCE RESTART 10:59

Uptime

10 h 59 min since its last restart, at the last reading
7-day average5peak 15
Rank#1,424top 6% · #209 in NA
Last wipe27d agomonthly schedule
Next wipe7d 16hThu 5 Nov, 19:00 UTC FW
Memory5,331MB48 h peak 9 players
REC 1

Players

AveragePeak
02.557.51003:0012:0021:0005:0014:0000:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608003:0012:0021:0005:0014:0000:00

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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15001k1.5k2k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 6% of all ranked servers, top 11% in NA, and #69 of the solo servers (top 31%). Ranked on player hours over the last seven days.

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 16h. The force wipe · high confidence

wipe-day peak25players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 16hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC35d 16hFW

The first 48 hours of its last wipes

010203040+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 25, 8 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 18:08 UTC FW27d ago 25 – running 4

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on Old Dad's 2X Solo Only 2.0?

An average of 25 players came at the busiest on its recent wipes. 8 hours after the wipe, the crowd peaked on the latest wipe.

When does Old Dad's 2X Solo Only 2.0 wipe?

With the force wipe, once a month, Old Dad's 2X Solo Only 2.0 wipes. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. 27 days 7 hours ago the current world was made. A monthly wipe schedule is published in its tags.

Tags

How should you read the tags on Old Dad's 2X Solo Only 2.0?

These are the tags Old Dad's 2X Solo Only 2.0 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts1 (Group limit): Teams are capped at 1; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; NA (North America): North America is the browser category it sits in. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Old Dad's 2X Solo Only 2.0 appear in Rust Metrics lists and filters?

On Rust Metrics, Old Dad's 2X Solo Only 2.0 sits in these lists: 2x Rust servers, checked live, Modded Rust servers, checked live, Solo-only Rust servers and North America: server readout. These filters bring it up on the server list: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: Solo; Wipe schedule: Monthly; Gather rate: 2x.

Population

What position does Old Dad's 2X Solo Only 2.0 hold among Rust servers?

Top 6% of all ranked servers: Old Dad's 2X Solo Only 2.0 takes #1,424 on seven-day player hours and #209 in North America. Check: group rank. #69 among solo servers.

How full does Old Dad's 2X Solo Only 2.0 get?

6 of 50 slots are filled on Old Dad's 2X Solo Only 2.0 right now. Seven-day check: 5 players on average. Peak reading: 15. Average at the busiest hour was 7 players, at 03:00 UTC over the last 48 hours.

Operator and location

Which location does Old Dad's 2X Solo Only 2.0 run from?

Old Dad's 2X Solo Only 2.0 gives North America as its location, with the NA tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 66.51.99.87:28050.

What Rust version is Old Dad's 2X Solo Only 2.0 on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by Old Dad's 2X Solo Only 2.0. To get in, your game needs the same protocol; Steam applies the update.

How does Old Dad's 2X Solo Only 2.0 perform?

Over the last 48 hours the average was 51 server fps; the floor was 5. Check: entities. The peak was 217,869, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 6,216 MB. Lag, as players feel it, is low fps plus a climbing entity count.

What is the uptime on Old Dad's 2X Solo Only 2.0, and is it online?

Old Dad's 2X Solo Only 2.0 reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 10 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Rules and settings

What rules does Old Dad's 2X Solo Only 2.0 enforce, and what are its settings?

The name carries the rate: 2x gather on Old Dad's 2X Solo Only 2.0. Solo play only. Teams are not allowed. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Old Dad's 2X Solo Only 2.0?

From seed 1441365713, the game generates the procedural map on Old Dad's 2X Solo Only 2.0. Its size is 4,400. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Join

How do you connect to Old Dad's 2X Solo Only 2.0?

Check: join. Open Rust, press F1, then enter client.connect 66.51.99.87:28050. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^m,NA,gmrust,cs168909,ts1,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts1
Group limit Teams are capped at 1.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build The server runs game build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Check: wipe cycle. Monthly, alongside Facepunch's force wipe.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Region

NA
North America North America is the browser category it sits in.

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.