RUST METRICSFlight deck · live data
Data live Servers11,679 Players48,756 Populated3,222 Fresh wipes 3 h127 Scan5 min
‹ All servers104.143.2.43:28020
Online Full Queue Fresh wipe Wipe due No query

CZR.gg | Solo/Duo/Trio | Biweekly | Thursday

Online NA 104.143.2.43:28020 checked 13m ago

biweekly wipes vanillacarbon
COM 1 · connect

Server instruments

last reading Tue 23:00 UTC
0 25 50 75 100 PAX 3 /100

Players now

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

Server fps

48 h low 41 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 96,946 ×1000

Entities

48 h range 76,207–96,946 · memory 3,263 MB
1239 ET SINCE RESTART 10:03

Uptime

10 h 3 min since its last restart, at the last reading
7-day average2peak 6
Rank#2,487top 11% · #390 in NA
Last wipe5d agobiweekly schedule
Next wipe8d 17hThu 5 Nov, 19:00 UTC FW
Memory3,263MB48 h peak 6 players
REC 1

Players

AveragePeak
0246802:0011:0020:0005:0014:0023:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608002:0011:0020:0005:0014:0023: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
12k4k6k8k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

PLAN

Wipe schedule

from its schedule tag

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

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

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC8d 17hFW
  2. WPT 2Thu 19 Nov, 18:07 UTC22d 16h
  3. WPT 3Thu 3 Dec, 19:00 UTC36d 17hFW

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 18:07 UTC5d ago 6 – running 1
Thu 15 Oct, 22:25 UTC12d ago 3 held half 6.8 days 1
Thu 1 Oct, 17:36 UTC FW26d ago 4 halved by day 13 14.2 days 0
Thu 17 Sep, 20:58 UTC40d ago 7 halved by day 1 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.

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 timing

What should you expect from wipe day on CZR.gg | Solo/Duo/Trio | Biweekly | Thursday?

At their busiest, its recent wipes drew 4 players on average. After the latest wipe, numbers topped out at 44 hours. Above half that peak the crowd stayed until the next wipe in 33% of recent wipes. When it didn't hold, by day 7 it fell below half.

How often does CZR.gg | Solo/Duo/Trio | Biweekly | Thursday wipe, and when?

Its tag guides the prediction: too few of CZR.gg | Solo/Duo/Trio | Biweekly | Thursday's wipes are on record to confirm its schedule. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world in play was created 5 days 7 hours ago. Its tags publish a wipe schedule of one wipe every two weeks.

Lists and filters

Which tags does CZR.gg | Solo/Duo/Trio | Biweekly | Thursday carry, and what do they mean?

Tags published by CZR.gg | Solo/Duo/Trio | Biweekly | Thursday, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^b (Biweekly): Two-week wipe schedule; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^y (Carbon): Check: framework. Carbon; NA (North America): The server browser files it under North America; rustmaps (Custom tag): Owner or plugin definition: this tag is not a standard Rust one. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which operator is behind CZR.gg | Solo/Duo/Trio | Biweekly | Thursday?

Most likely the same operator runs them: CZR.gg | Solo/Duo/Trio | Biweekly | Thursday publishes a czr.gg hostname, and so do 6 other servers we track.

Where does CZR.gg | Solo/Duo/Trio | Biweekly | Thursday appear in Rust Metrics lists and filters?

On Rust Metrics, CZR.gg | Solo/Duo/Trio | Biweekly | Thursday sits in these lists: Rust community servers: live readings, North America: server readout and Vanilla Rust servers, live. Reading: server list filters. It comes up under 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.

Population

What position does CZR.gg | Solo/Duo/Trio | Biweekly | Thursday hold among Rust servers?

Ranked by seven-day player hours, CZR.gg | Solo/Duo/Trio | Biweekly | Thursday sits at #2,487 and #390 in North America, inside the top 11%.

What player count does CZR.gg | Solo/Duo/Trio | Biweekly | Thursday carry?

Current headcount on CZR.gg | Solo/Duo/Trio | Biweekly | Thursday: 3 players, 100 slots available. Seven-day check: 2 players on average. Peak reading: 6. Check: 48-hour peak. 16:00 UTC, 5 players on average.

Operator and location

Where does CZR.gg | Solo/Duo/Trio | Biweekly | Thursday sit?

Reading: location. The NA tag puts CZR.gg | Solo/Duo/Trio | Biweekly | Thursday in North America. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 104.143.2.43:28020.

What Rust version is CZR.gg | Solo/Duo/Trio | Biweekly | Thursday on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by CZR.gg | Solo/Duo/Trio | Biweekly | Thursday. To get in, your game needs the same protocol; Steam applies the update.

What is the performance reading for CZR.gg | Solo/Duo/Trio | Biweekly | Thursday?

Over the last 48 hours the average was 60 server fps; the floor was 41. Peak entity count: 96,946. Buildings, deployables and all else included. Memory peak: 4,040 MB. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is CZR.gg | Solo/Duo/Trio | Biweekly | Thursday, and is it online now?

Check: connection. CZR.gg | Solo/Duo/Trio | Biweekly | Thursday is online at this moment. Check: restart. The uptime it reports puts the last restart about 10 hours ago. Reading: 93% uptime over the last 7 full days. It was up 156 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Map and rules

How is CZR.gg | Solo/Duo/Trio | Biweekly | Thursday configured, and what rules are in force?

Reading the name gives no gather rate for CZR.gg | Solo/Duo/Trio | Biweekly | Thursday. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. The server browser lists it under Community. Check: plugins. It runs Carbon of them. It describes itself as vanilla. The meaning given: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. Anti-cheat reading: VAC on, Valve's system.

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

Size 4,000, custom map, on CZR.gg | Solo/Duo/Trio | Biweekly | Thursday. The file is published and downloadable here.

Connection

How do you connect to CZR.gg | Solo/Duo/Trio | Biweekly | Thursday?

To join: start Rust, press F1 and type client.connect 104.143.2.43:28020. Or press Launch Rust here and Steam opens the game and connects you. You can find its website at https://discord.com/invite/WBuDvDaU2m.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players The server holds 100 slots.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly Two-week wipe schedule.

Difficulty

^v
Vanilla Unmodified from Facepunch's release: no altered rates, no kits, no extra rules.

Mods and access

^y
Carbon Check: framework. Carbon.

Region

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

Other

rustmaps
Custom tag Owner or plugin definition: this tag is not a standard Rust one.

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.