RUST METRICSFlight deck · live data
Data live Servers11,757 Players71,901 Populated3,470 Fresh wipes 3 h213 Scan5 min
‹ All servers38.15.45.224:28315
Online Full Queue Fresh wipe Wipe due No query

[10/29] BCR Vanilla 2x

Online NA 38.15.45.224:28315 checked 11m ago

2x biweekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Thu 21:00 UTC
0 31 62 94 125 PAX 0 /125

Players now

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

Server fps

48 h low 103 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 72,140 ×1000

Entities

48 h range 67,036–72,140 · memory 1,932 MB
1239 ET SINCE RESTART 03:00

Uptime

3 h 0 min since its last restart, at the last reading
7-day average0peak 1
Rank#9,007top 40% · #1224 in NA
Last wipe5h agobiweekly schedule
Next wipe6d 19hThu 5 Nov, 19:00 UTC FW
Memory1,932MB48 h peak 1 players
REC 1

Players

AveragePeakWipe
00.250.50.75100:0009:0019:0003:0012:0021:00Wiped Thu 29 Oct, 18:06 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
05010015020000:0009:0019:0003:0012:0021:00Wiped Thu 29 Oct, 18:06 UTCWIPE

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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

Wipe schedule

fixed weekdays

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

usual gap21 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 2

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC6d 19hFW
  2. WPT 2Thu 19 Nov, 18:06 UTC20d 18h
  3. WPT 3Thu 3 Dec, 19:00 UTC34d 19hFW
  4. WPT 4Thu 10 Dec, 18:06 UTC41d 18h

The first 48 hours of its last wipes

Thu 15 OctThu 1 OctThu 17 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 18:06 UTC5h ago – – running 1
Thu 15 Oct, 18:20 UTC14d ago 1 – – 0
Thu 1 Oct, 18:40 UTC FW28d ago 1 halved by day 1 14 days 0
Thu 17 Sep, 18:09 UTC42d ago 0 – 14 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 [10/29] BCR Vanilla 2x?

An average of 1 players came at the busiest on its recent wipes. 30 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. By day 2 it fell below half when it didn't.

How often does [10/29] BCR Vanilla 2x wipe, and when?

Wipes on [10/29] BCR Vanilla 2x come every 3 weeks on Thursday at 18:06 UTC. 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 hours ago. The tags carry an every-two-weeks wipe schedule.

Lists and filters

How should you read the tags on [10/29] BCR Vanilla 2x?

These are the tags [10/29] BCR Vanilla 2x publishes, and the server browser reads them: gmvanilla (Game mode): Survival on vanilla settings; mp125 (Max players): 125 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^b (Biweekly): It wipes once a fortnight; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game; NA (North America): Its browser listing: North America. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Who is in charge of [10/29] BCR Vanilla 2x?

The bluecollarrust.com hostname on [10/29] BCR Vanilla 2x also appears on 3 other servers we track, which points to one operator.

Where does [10/29] BCR Vanilla 2x appear in Rust Metrics lists and filters?

On Rust Metrics, [10/29] BCR Vanilla 2x sits in these lists: 2x Rust servers, checked live, Modded Rust servers, checked live and North America: server readout. Reading: server list filters. It comes up under Region: North America; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours; Gather rate: 2x.

Population

What position does [10/29] BCR Vanilla 2x hold among Rust servers?

Ranked by seven-day player hours, [10/29] BCR Vanilla 2x sits at #9,007 and #1,224 in North America, inside the top 40%.

How full does [10/29] BCR Vanilla 2x get?

Current headcount on [10/29] BCR Vanilla 2x: 0 players, 125 slots available. Check: players over seven days. Average 0, peak 1. Check: 48-hour peak. 19:00 UTC, 1 players on average.

Server

Where does [10/29] BCR Vanilla 2x sit?

Its NA tag places [10/29] BCR Vanilla 2x in North America. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 38.15.45.224:28315.

What Rust version is [10/29] BCR Vanilla 2x on?

Rust network protocol 2635 and build 168909 on Linux is the build [10/29] BCR Vanilla 2x runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for [10/29] BCR Vanilla 2x?

Check: fps. Average 145 server fps over the last 48 hours, low of 103. Within range. Reading: 72,140 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 2,908 MB. What players call lag comes from low fps and an entity count on the rise.

What is the uptime on [10/29] BCR Vanilla 2x, and is it online?

Check: connection. [10/29] BCR Vanilla 2x is online at this moment. Reading: uptime. About 3 hours ago it restarted, on its own count. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

What settings and rules apply on [10/29] BCR Vanilla 2x?

Gather rate check: 2x. That comes from the name [10/29] BCR Vanilla 2x. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is [10/29] BCR Vanilla 2x on?

Check: map. Procedural, size 3,500, seed 121315421, generated by the game on [10/29] BCR Vanilla 2x. View it on RustMaps from this page: matching size and seed give an identical map.

Join

What do you do to join [10/29] BCR Vanilla 2x?

Press F1 in Rust and enter client.connect 38.15.45.224:28315. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://www.bluecollarrust.com is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp125,ptrak,$r?,v2635,^b,NA,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode Survival on vanilla settings.
mp125
Max players 125 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly It wipes once a fortnight.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock game.

Region

NA
North America Its browser listing: 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.