Rust Data

rustdata.spaceservers66.51.99.75:28036.ipynb

Run all rust-data · live

‹ All servers

Online NA 66.51.99.75:28035 checked 10m ago

Dallas Rust Large | Biweekly

biweekly wipes vanillaoxidepremium

Connect

srv = rust.server("66.51.99.75:28036")
print(srv.connect_command)

Right now

srv.summary()
players now 1/100 # 1% full
7-day average 0 # peak 3
rank #4,232 # top 19% · #709 in NA
last wipe 13d ago # biweekly schedule
next wipe 20h # Thu 29 Oct, 20:51 UTC

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75101:0010:0019:0003:0012:0022:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
01020304001:0010:0019:0003:0012:0022: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 20 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
12.5k5k7.5k10k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 19% of all ranked servers, top 38% in NA. Ranked on player hours over the last seven days.

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Thursday 29 October, 20:51 UTC, in 20h. # Its biweekly schedule tag · low confidence

usual gap14.1 daysbetween real wipes
wipe-day peak4players, last three wipes
crowd held0%else halves by day 5

Coming wipes

inatkind
020hThu 29 Oct, 20:51 UTCwipe
17d 18hThu 5 Nov, 19:00 UTCFW force wipe
214d 20hThu 12 Nov, 20:51 UTCwipe
328d 20hThu 26 Nov, 20:51 UTCwipe
435d 18hThu 3 Dec, 19:00 UTCFW force wipe
542d 20hThu 10 Dec, 20:51 UTCwipe

The first 48 hours of its last wipes

Thu 15 OctThu 1 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 15 Oct, 20:51 UTC13d ago 3 NaN running 0
1 Thu 1 Oct, 17:57 UTC FW27d ago 5 halved by day 5 14.1 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

4200 · seed 1337
Map of Dallas Rust Large | Biweekly
map
Dallas Rust Large
size
4200
seed
1337

Server

srv.info()
address
66.51.99.75:28035
region
NA
max players
100
group limit
8, the default
wipe schedule
biweekly
last wipe
15 Oct 2026, 20:51 UTC
hostname
–
first seen
20 Sep 2026

About this server · in its own words

print(srv.description)
- Biweekly wipes every other Thursday at 4PM CDT - Force wipe at 1PM CDT on first Thursdays. - 50% Upkeep - No BP wipes unless Facepunch requires it - Join us on discord: https://discord.gg/4Hp3e9Hk7v

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

rust.similar(srv).head(6)
serverlike_thisplayers
0Rustopia.gg - US MediumNA · groups of 12+ · biweekly · 99 on average40/200
1Rusty Moose |US Biweekly|NA · groups of 12+ · biweekly · 68 on average40/200
2Rustoria.co - US Medium PremiumNA · groups of 12+ · biweekly · 41 on average25/200
3Gringers Solo Only | Noob Friendly Oct 22NA · groups of 8+ · biweekly · 40 on average48/100
4Reddit.com/r/PlayRust - US BiweeklyNA · groups of 12+ · biweekly · 29 on average8/200
5Rustafied.com - US Medium - LargeNA · groups of 16+ · biweekly · 27 on average7/100

Quick answers

From the figures on this page.

Player counts

How does Dallas Rust Large | Biweekly compare in the rankings?

On seven-day player hours Dallas Rust Large | Biweekly is #4,232 overall and #709 in North America, inside the top 19% of all ranked servers.

How many players does Dallas Rust Large | Biweekly hold at once?

Current row: 1 players on Dallas Rust Large | Biweekly, against 100 slots. Over the last seven days it averaged 0 players and peaked at 3. The 48-hour sample puts the busiest hour at 02:00 UTC, averaging 1 players.

Server data

How well does Dallas Rust Large | Biweekly perform?

The 48-hour average is 8 server fps, with a low of 5. The entity count peaked at 116,814, covering buildings, deployables and the rest of the world. The memory field tops out at 3,546 MB. Low fps plus an entity count on the way up is the lag players report.

What is the Rust version on Dallas Rust Large | Biweekly?

Version Rust network protocol 2635 and build 168909 on Linux is reported by Dallas Rust Large | Biweekly. The protocol has to match before you can join, and Steam does the updating.

Is Dallas Rust Large | Biweekly up, and what does its uptime show?

The current sample puts Dallas Rust Large | Biweekly online. A restart about 11 hours ago is what its reported uptime implies. 144 of 168 hours up over the last 7 full days, or 86%. The first row Rust Data holds for it is dated 20 September 2026.

Where does Dallas Rust Large | Biweekly sit?

With its NA tag, Dallas Rust Large | Biweekly lists itself in North America. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 66.51.99.75:28035 is its address.

Rules, settings, map

Which settings and rules does Dallas Rust Large | Biweekly run?

The name Dallas Rust Large | Biweekly carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Community is its browser category. Plugins installed: Oxide. The description says vanilla, which here means no changed rates, kits or rules: the game as Facepunch ships it. Only premium players get in. Anti-cheat status: VAC on.

What is the map on Dallas Rust Large | Biweekly?

Size 4,200, seed 1337: the procedural map on Dallas Rust Large | Biweekly, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Recorded under map name: Dallas Rust Large.

Wipes and dates

When does Dallas Rust Large | Biweekly wipe, and on what schedule?

Too few wipes are on record for Dallas Rust Large | Biweekly to confirm its schedule, so the tag drives the prediction. The schedule puts the next wipe on Thursday 29 October at 20:51 UTC. This world was created 13 days 3 hours ago. A fortnightly wipe schedule is published in its tags.

On Dallas Rust Large | Biweekly, what happens on wipe day?

Across recent wipes the busiest point averaged 4 players. Peak population on the latest wipe came 3 hours in. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. Otherwise the crowd fell below half by day 5.

Tags, lists

Where does Dallas Rust Large | Biweekly appear among Rust Data lists and filters?

On Rust Data, Dallas Rust Large | Biweekly appears in these lists: Rust community servers, unfiltered, North America Rust servers and Vanilla Rust servers. It appears under these filters on the server list: Region: North America; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Game mode: Premium; Server tag: Biweekly ^b, Vanilla ^v, Premium ^q and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

Which meanings do the tags on Dallas Rust Large | Biweekly hold?

These tags are published by Dallas Rust Large | Biweekly and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^b (Biweekly): Two weeks between wipes; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^q (Premium): Only premium players get in; ^o (Oxide): Plugin framework: Oxide (uMod); NA (North America): In the server browser it sits under North America; sc1 (Custom tag): A plugin or the owner added this; standard Rust does not define it. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way into Dallas Rust Large | Biweekly?

In Rust, F1 opens the console: type client.connect 66.51.99.75:28035. Launch Rust on this page does the same by opening the game through Steam and connecting. Only premium players get in. You will find its website at https://discord.com/invite/4Hp3e9Hk7v.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2635,^b,^v,NA,gmrust,cs168909,^q,sc1,ts8,^o

Game

gmrust
Game mode Rust survival in its standard form.
mp100
Max players 100 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build The server runs build 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

Wipe schedule

^b
Biweekly Two weeks between wipes.

Difficulty

^v
Vanilla No changed rates, kits or rules: the game as Facepunch ships it.

Mods and access

^q
Premium Only premium players get in.
^o
Oxide Plugin framework: Oxide (uMod).

Region

NA
North America In the server browser it sits under North America.

Other

sc1
Custom tag A plugin or the owner added this; standard Rust does not define it.

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 48,039 players 11,719 servers online