Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO C SRV11,870online PAX96,202playing OCC4,104with players WIPED 3H159
VANVanilla traffic
Callsign

CZR1270=

CZR.gg | Solo | Biweekly | Thursday

Online NA 104.143.2.43:28029 checked 7m ago

biweekly wipes vanillacarbon
Clearance · join
Players now 6/ 100 6% full
7-day average6peak 16
Rank#1,270top 6% · #185 in NA
Last wipe4d agobiweekly schedule
Next wipe9d 1hThu 5 Nov, 19:00 UTC FW
Track history

Players

AveragePeak
0510152018:0003:0012:0022:0007:0016:00

Hourly average and peak, UTC.

Server performance

02040608018:0003:0012:0022:0007:0016: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.

Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 6% of all ranked servers, top 10% 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 5 November, 19:00 UTC, in 9d 1h.

The force wipe · high confidence

usual gap13.9 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak14players, last three wipes
crowd held33%else halves by day 8

Coming wipes

  1. 9d 1hThu 5 Nov, 19:00 UTCFW
  2. 23d 0hThu 19 Nov, 18:07 UTC
  3. 37d 1hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

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

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

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 18:07 UTC4d ago 16 – running 2
Thu 15 Oct, 22:25 UTC11d ago 11 held half 6.8 days 5
Thu 1 Oct, 17:37 UTC FW26d ago 14 halved by day 11 14.2 days 1
Thu 17 Sep, 20:58 UTC39d ago 16 halved by day 5 13.9 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 · 122 on average Rustopia.gg - US Medium
    Players 33/200
  2. 02COM
    Callsign RST015NA · groups of 12+ · biweekly · 100 on average Rusty Moose |US Biweekly|
    Players 19/200
  3. 03COM
    Callsign RST015NA · groups of 12+ · biweekly · 57 on average Rustoria.co - US Medium Premium
    Players 27/200
  4. 04COM
    Callsign RST018NA · groups of 16+ · biweekly · 42 on average Rustafied.com - US Medium - Large
    Players 6/100
  5. 05COM
    Callsign RDD017NA · groups of 12+ · biweekly · 39 on average Reddit.com/r/PlayRust - US Biweekly
    Players 15/200
  6. 06COM
    Callsign GRN016NA · groups of 8+ · biweekly · 37 on average Gringers Solo Only | Noob Friendly Oct 22
    Players 37/100
ATIS · this server

Quick answers

From the figures on this page.

Filters

Where does CZR.gg | Solo | Biweekly | Thursday appear in Rust Tracker lists and filters?

On Rust Tracker, CZR.gg | Solo | Biweekly | Thursday sits in these lists: Community servers, no tags, North America: live server tracking and Vanilla Rust servers, tracked live. It comes up under these filters on the server list: Region: North America; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b, Vanilla ^v and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last week.

What do the tags mean that CZR.gg | Solo | Biweekly | Thursday is listed under?

These tags are published by CZR.gg | Solo | Biweekly | Thursday for the game's server browser to read: gmrust (Game mode): Survival as standard Rust plays; mp100 (Max players): 100 slots on this server; ts8 (Group limit): Team limit is 8, the game default; v2635 (Protocol): Your game must be on protocol 2635 to connect; cs168909 (Build): Build: 168909; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): No region code is set; ^b (Biweekly): Every two weeks it wipes; ^v (Vanilla): No changed rates, kits or rules — the game as Facepunch ships it; ^y (Carbon): Plugin framework: Carbon; NA (North America): In the server browser it is listed under North America; rustmaps (Custom tag): Set by the owner or a plugin; not a standard Rust tag. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.

Who operates CZR.gg | Solo | Biweekly | Thursday?

A czr.gg hostname is published by CZR.gg | Solo | Biweekly | Thursday, as it is by 6 other servers we track; same operator, most likely.

Wipe Schedule

What should you expect on CZR.gg | Solo | Biweekly | Thursday when wipe day lands?

Recent wipes averaged a peak of 14 players. The peak on the latest wipe came 5 hours after it. Recent wipes kept the crowd above half the peak until the next wipe 33% of the time. By day 8 the crowd dropped below half where it did not hold.

Which wipe times are confirmed for CZR.gg | Solo | Biweekly | Thursday?

The schedule of CZR.gg | Solo | Biweekly | Thursday cannot be confirmed, with too few wipes on record: the prediction follows its tag. On Thursday 5 November at 19:00 UTC the force wipe lands, its next wipe, and every Rust server wipes with it. Its world went live 4 days 23 hours. A two-weekly wipe schedule is published in its tags.

Location and Status

Is CZR.gg | Solo | Biweekly | Thursday up, and how does its uptime hold?

CZR.gg | Solo | Biweekly | Thursday is up and online at this moment. The uptime it reports puts the last restart about 3 hours ago. Uptime stood at 100% for the last 7 full days, 168 of 168 hours online. Rust Tracker logged it first on 13 September 2026.

Which Rust build is CZR.gg | Solo | Biweekly | Thursday running?

Rust network protocol 2635 and build 168909 on Linux is what CZR.gg | Solo | Biweekly | Thursday runs. To join, your game must be on the same protocol; Steam handles the update.

Is CZR.gg | Solo | Biweekly | Thursday holding performance?

Server fps held an average of 59 across the last 48 hours, never below 22. Peak entity count: 107,738, covering buildings, deployables and all else in the world. Memory peaked at 4,869 MB. Players feel lag when fps drops and the entity count climbs.

What location is CZR.gg | Solo | Biweekly | Thursday hosted in?

In North America, under its NA tag, is where CZR.gg | Solo | Biweekly | Thursday lists itself. Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 104.143.2.43:28029.

Population

How many players are on CZR.gg | Solo | Biweekly | Thursday right now?

Tracking CZR.gg | Solo | Biweekly | Thursday: 6 of 100 slots filled. Seven-day average 6 players; peak 16. Busiest window in 48 hours: 20:00 UTC, 11 players on average.

What rank does CZR.gg | Solo | Biweekly | Thursday carry among Rust servers?

Seven-day player hours: #1,270 overall for CZR.gg | Solo | Biweekly | Thursday, top 6% of ranked servers, #185 in North America.

Map and Rules

Which settings and rules are confirmed on CZR.gg | Solo | Biweekly | Thursday?

No gather rate appears in CZR.gg | Solo | Biweekly | Thursday's name. The game's default applies: groups can have up to 8 players. survival is the game mode, gather, build, raid, as the game intends. Raiding and PvP are permitted between players. A community server: the server browser lists it under Community. Carbon plugins run on it. It uses the word vanilla for itself: no changed rates, kits or rules — the game as Facepunch ships it. On: VAC, Valve's anti-cheat.

What map is CZR.gg | Solo | Biweekly | Thursday on?

Custom map, size 4,000, on CZR.gg | Solo | Biweekly | Thursday: the file is published for download from this page.

Connect

What is the way to join CZR.gg | Solo | Biweekly | Thursday?

Open the console in Rust with F1 after starting the game, then type client.connect 104.143.2.43:28029. Alternatively, Launch Rust here opens Rust via Steam and connects you. The server's website: https://discord.com/invite/WBuDvDaU2m.

Transponder codes

Server tags

What each one means.

Published as mp100,ptrak,$r?,v2635,^y,^b,^v,NA,gmrust,cs168909,ts8,rustmaps

Game

gmrust
Game mode Survival as standard Rust plays.
mp100
Max players 100 slots on this server.
ts8
Group limit Team limit is 8, the game default.
v2635
Protocol Your game must be on protocol 2635 to connect.
cs168909
Build Build: 168909.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Difficulty

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

Mods and access

^y
Carbon Plugin framework: Carbon.

Region

NA
North America In the server browser it is listed under North America.

Other

rustmaps
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.