Rust Data

rustdata.spaceservers66.51.96.88:28001.ipynb

Run all rust-data · live

‹ All servers

Offline NA 66.51.96.88:28000 checked 2d ago

Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays

2x duo biweekly wipes moddedoxide

Connect

srv = rust.server("66.51.96.88:28001")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak 1
rank #12,922 # top 58% · #1394 in NA
last wipe 6d ago # biweekly schedule
next wipe 1h # Thu 29 Oct, 18:13 UTC

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 58% of all ranked servers, top 75% in NA, and #352 of the duo servers (top 84%). Ranked on player hours over the last seven days.

Wipe schedule · fixed weekdays

srv.wipe_schedule()

Next wipe Thursday 29 October, 18:13 UTC, in 1h. # Every Thursday at 18:13 UTC · high confidence

usual gap7 daysbetween real wipes
on rhythm83%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 1

Coming wipes

inatkind
01hThu 29 Oct, 18:13 UTCwipe
17d 2hThu 5 Nov, 19:00 UTCFW force wipe
214d 1hThu 12 Nov, 18:13 UTCwipe
321d 1hThu 19 Nov, 18:13 UTCwipe
428d 1hThu 26 Nov, 18:13 UTCwipe
535d 2hThu 3 Dec, 19:00 UTCFW force wipe
642d 1hThu 10 Dec, 18:13 UTCwipe

The first 48 hours of its last wipes

Thu 22 OctSat 17 OctThu 15 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 28 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 22 Oct, 18:13 UTC6d ago 1 NaN running 0
1 Sat 17 Oct, 18:12 UTC11d ago 1 halved by day 1 5 days 0
2 Thu 15 Oct, 18:12 UTC13d ago 1 held half 2 days 0
3 Thu 8 Oct, 18:12 UTC20d ago 0 NaN 7 days 0
4 Thu 1 Oct, 18:15 UTC FW27d ago 0 NaN 7 days 0
5 Thu 24 Sep, 18:12 UTC34d ago 0 NaN 7 days 0
6 Thu 17 Sep, 18:12 UTC41d ago 0 NaN 7 days 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.

display(srv.map, srv.info())

Map

3500 · seed 1435462537
Map of Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays
map
Procedural Map
size
3500
seed
1435462537
Open on RustMaps

Server

srv.info()
address
66.51.96.88:28000
region
NA
max players
50
group limit
duo
wipe schedule
biweekly
last wipe
22 Oct 2026, 18:13 UTC
hostname
–
first seen
13 Sep 2026

About this server · in its own words

print(srv.description)
- Wipe schedule: Full wipe every other Thursday @ 1pm CDT | monthly @ force wipe - 50% upkeep - Shorter nights - Chill, low pop server. New players are welcome. - Rules: no racist/toxic/abusive behavior; no cheating/hacking/scripting - PVP outside monuments is discouraged

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |NA · duo · 2x · biweekly · 3 on average2/20
1WARBANDITS.GG 2X |Solo/Duo|X2 JUST FULLWIPEDNA · duo · 2x · weekly · 144 on average169/200
2US Limitless 2x Monthly Solo/Duo|No BP Wipes|Noob FriendlyNA · duo · 2x · monthly · 56 on average30/200
3US RENEGADE 2x Monthly | Solo Duo | 50% Upkeep | No BP WipeNA · duo · 2x · monthly · 25 on average12/150
4HollowServers.co 2x Solo/Duo |X2 JUST FULL WIPEDNA · trio · 2x · biweekly · 11 on average6/150
5US Limitless 2x Solo/Duo | No BP Wipes|Noob Friendly|Just WipedNA · duo · 2x · weekly · 8 on average3/100

Quick answers

From the figures on this page.

Population

How does Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays compare in the rankings?

Player hours over the last seven days: #12,922 for Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays, #1,394 in North America, within the top 58% of the ranked set. The duo group places it at #352.

What population does Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays carry?

Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays returns no live count at this refresh, having last been seen 2 days 23 hours ago. Over the last seven days it averaged 0 players and peaked at 1.

About the server

What Rust version does Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays run?

Rust network protocol 2635 and build 168909 on Linux is what Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays runs. Steam updates your game for you, but the protocol must match to join.

Is Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays up, and what does its uptime show?

Offline now for Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays, last seen 2 days 23 hours ago. Uptime of 67% across the last 7 full days: 113 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.

Where does Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays sit?

The NA tag is what Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays uses to list itself in North America. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 66.51.96.88:28000.

Map and rules

Which rules apply on Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays, and what settings?

Gather sits at 2x, read from the server's own name: Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays. duo sets the cap: 2 players per group. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.

Which map has Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays loaded?

Size 3,500, seed 1435462537: the procedural map on Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

When does Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays wipe, and how often?

every Thursday at 18:13 UTC is how Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays wipes. The schedule puts the next wipe on Thursday 29 October at 18:13 UTC. The world it runs now was generated 6 days 22 hours ago. A fortnightly wipe schedule is published in its tags.

On Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays, what happens on wipe day?

Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 28 hours in. The crowd stayed above half that peak until the next wipe in 50% of recent wipes. Otherwise the crowd fell below half by day 1.

Lists and tags

Which lists on Rust Data hold Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays, and which filters?

The Rust Data lists that Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays fits are: Rust servers with a duo group limit, Modded Rust servers, 2x Rust servers and North America Rust servers. These filters bring it up on the server list: Region: North America; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: Duo; Wipe schedule: Every two weeks; Last wipe: In the last week; Gather rate: 2x.

How should you read the server tags on Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays?

These tags are published by Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts2 (Group limit): Team size tops out at 2; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^b (Biweekly): Two weeks between wipes; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings; NA (North America): The server browser files it under North America. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

What is the way to join Fox River Rust | Low Pop 2x Solo/Duo | Bi-Weekly Thursdays?

Enter client.connect 66.51.96.88:28000 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp50,ptrak,$r?,v2635,^b,NA,gmrust,cs168909,ts2,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp50
Max players The server lists 50 slots.
ts2
Group limit Team size tops out at 2.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Two weeks between wipes.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

Region

NA
North America The server browser files it under North America.

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.

Rust Data 98,401 players 11,879 servers online