Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO V SRV11,799online PAX79,295playing OCC3,786with players WIPED 3H103
VANVanilla traffic
Callsign

DLL4138=

Dallas Rust Large | Biweekly

Online NA 66.51.99.75:28035 checked 10m ago

biweekly wipes vanillaoxidepremium
Clearance · join
Players now 0/ 100 0% full
7-day average0peak 3
Rank#4,138top 19% · #698 in NA
Last wipe12d agobiweekly schedule
Next wipe1d 0hThu 29 Oct, 20:51 UTC
Track history

Players

AveragePeak
00.250.50.75121:0006:0015:0000:0009:0019:00

Hourly average and peak, UTC.

Server performance

01020304021:0006:0015:0000:0009:0019: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
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.

Flight plan

Wipe schedule

from its schedule tag
ETD · next wipe

Next wipe Thursday 29 October, 20:51 UTC, in 1d 0h.

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

  1. 1d 0hThu 29 Oct, 20:51 UTC
  2. 7d 22hThu 5 Nov, 19:00 UTCFW
  3. 15d 0hThu 12 Nov, 20:51 UTC
  4. 29d 0hThu 26 Nov, 20:51 UTC
  5. 35d 22hThu 3 Dec, 19:00 UTCFW
  6. 43d 0hThu 10 Dec, 20:51 UTC

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
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 20:51 UTC12d ago 3 – running 0
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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01COM
    Callsign RST010NA · groups of 12+ · biweekly · 103 on average Rustopia.gg - US Medium
    Players 51/200
  2. 02COM
    Callsign RST015NA · groups of 12+ · biweekly · 72 on average Rusty Moose |US Biweekly|
    Players 23/200
  3. 03COM
    Callsign RST015NA · groups of 12+ · biweekly · 43 on average Rustoria.co - US Medium Premium
    Players 21/200
  4. 04COM
    Callsign GRN016NA · groups of 8+ · biweekly · 40 on average Gringers Solo Only | Noob Friendly Oct 22
    Players 43/100
  5. 05COM
    Callsign RDD017NA · groups of 12+ · biweekly · 30 on average Reddit.com/r/PlayRust - US Biweekly
    Players 9/200
  6. 06COM
    Callsign RST018NA · groups of 16+ · biweekly · 29 on average Rustafied.com - US Medium - Large
    Players 7/100
ATIS · this server

Quick answers

From the figures on this page.

Tags

Where does Dallas Rust Large | Biweekly appear in Rust Tracker lists and filters?

On Rust Tracker, Dallas Rust Large | Biweekly sits in these lists: Community servers, no tags, North America: live server tracking and Vanilla Rust servers, tracked live. These filters surface it 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 tags does Dallas Rust Large | Biweekly carry, and what do they mean?

The game's server browser reads these tags from Dallas Rust Large | Biweekly: gmrust (Game mode): Standard survival mode for Rust; mp100 (Max players): Slots: 100; ts8 (Group limit): Teams cap at 8; this is the game default; v2635 (Protocol): Your game must be on protocol 2635 to connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): The region code is unset; ^b (Biweekly): Two-week wipe cycle; ^v (Vanilla): As Facepunch ships it: rates, kits and rules are unchanged; ^q (Premium): Rust premium status is required to join; ^o (Oxide): Plugin framework confirmed: Oxide (uMod); NA (North America): The server browser lists it under North America; sc1 (Custom tag): Set by the owner or a plugin; not a standard Rust tag. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.

Wipe Schedule

What should you expect on Dallas Rust Large | Biweekly when wipe day lands?

At their busiest, recent wipes averaged 4 players. 3 hours after the latest wipe, the crowd peaked. Half the peak was held until the next wipe in 0% of its recent wipes. By day 5 the crowd dropped below half where it did not hold.

Which wipe times are confirmed for Dallas Rust Large | Biweekly?

Dallas Rust Large | Biweekly's schedule is unconfirmed, too few wipes being on record, so the prediction follows its tag. Thursday 29 October at 20:51 UTC is when the next wipe falls due. 12 days 23 hours since this world was made. Tags list a wipe schedule of every two weeks.

Location and Status

What is the uptime on Dallas Rust Large | Biweekly, and is it online?

Right now Dallas Rust Large | Biweekly is online. About 5 hours ago it restarted last, based on reported uptime. Uptime stood at 100% for the last 7 full days, 168 of 168 hours online. First contact for Rust Tracker: 20 September 2026.

What Rust version is Dallas Rust Large | Biweekly on?

Rust network protocol 2635 and build 168909 is the build on Dallas Rust Large | Biweekly; the platform is Linux. To join, your game must be on the same protocol; Steam handles the update.

How smoothly does Dallas Rust Large | Biweekly run?

For the last 48 hours it averaged 9 server fps; the floor was 5. Peak entity count: 116,814, covering buildings, deployables and all else in the world. Memory peaked at 3,546 MB. Players feel lag when fps drops and the entity count climbs.

What location is Dallas Rust Large | Biweekly hosted in?

In North America, under its NA tag, is where Dallas Rust Large | Biweekly lists itself. Rust Tracker displays the location a server claims; it does not verify where the machine sits. You connect at 66.51.99.75:28035.

Player Count

Is Dallas Rust Large | Biweekly busy?

Slots 100; players on board 0: that is Dallas Rust Large | Biweekly now. Peak of 3 in the last seven days, average 0 players. Peak traffic in the last 48 hours came at 02:00 UTC, averaging 1 players.

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

Dallas Rust Large | Biweekly places #4,138 on seven-day player hours, #698 in North America and in the top 19% of all ranked servers.

Map and Rules

Which settings and rules are confirmed on Dallas Rust Large | Biweekly?

Nothing in Dallas Rust Large | Biweekly's name states a gather rate. The game's default applies: groups can have up to 8 players. It runs survival, gather, build and raid: the standard game. Fighting and raiding between players are on. Listed under Community in the server browser, it is a community server. Plugins on it: Oxide. It uses the word vanilla for itself: as Facepunch ships it: rates, kits and rules are unchanged. Rust premium status is required to join. On: VAC, Valve's anti-cheat.

Which map is confirmed for Dallas Rust Large | Biweekly?

The map on Dallas Rust Large | Biweekly is procedural, size 4,200, seed 1337, generated by the game. Look at it on RustMaps from this page: equal size and seed return the same map. Its map goes by the name Dallas Rust Large.

Connect

What is the way to join Dallas Rust Large | Biweekly?

Open the console in Rust with F1 after starting the game, then type client.connect 66.51.99.75:28035. Alternatively, Launch Rust here opens Rust via Steam and connects you. Rust premium status is required to join. For the website, go to https://discord.com/invite/4Hp3e9Hk7v.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Standard survival mode for Rust.
mp100
Max players Slots: 100.
ts8
Group limit Teams cap at 8; this is the game default.
v2635
Protocol Your game must be on protocol 2635 to connect.
cs168909
Build This server runs game build 168909.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code The region code is unset.

Wipe schedule

^b
Biweekly Two-week wipe cycle.

Difficulty

^v
Vanilla As Facepunch ships it: rates, kits and rules are unchanged.

Mods and access

^q
Premium Rust premium status is required to join.
^o
Oxide Plugin framework confirmed: Oxide (uMod).

Region

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

Other

sc1
Custom tag Set by the owner or a plugin; not a standard Rust tag.

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.