RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h108 Scan5 min
‹ All servers66.51.99.162:28125
Online Full Queue Fresh wipe Wipe due No query

CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY

Online NA 66.51.99.162:28125 checked 1h ago

biweekly wipes vanillamoddedoxidepve
COM 1 · connect

Server instruments

last reading Wed 17:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

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

Server fps

48 h low 51 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 122,782 ×1000

Entities

48 h range 117,712–126,152 · memory 4,140 MB
1239 ET SINCE RESTART 05:17

Uptime

5 h 17 min since its last restart, at the last reading
7-day average0peak 4
Rank#4,323top 19% · #732 in NA
Last wipe16d agobiweekly schedule
Next wipe8d 0hThu 5 Nov, 19:00 UTC FW
Memory4,140MB48 h peak 2 players
REC 1

Players

AveragePeak
00.511.5219:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020019:0004:0013:0023:0008:0017: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 9 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k9 Oct13 Oct17 Oct20 Oct24 Oct28 Oct

Top 19% of all ranked servers, top 39% 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 0h. The force wipe · high confidence

wipe-day peak7players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC8d 0hFW
  2. WPT 2Mon 9 Nov, 01:13 UTC11d 7h
  3. WPT 3Mon 23 Nov, 01:13 UTC25d 7h
  4. WPT 4Thu 3 Dec, 19:00 UTC36d 0hFW
  5. WPT 5Mon 7 Dec, 01:13 UTC39d 7h

The first 48 hours of its last wipes

02468+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 12 Oct, 01:13 UTC16d ago 7 – running 5

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

Reset cycle

What happens on CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY when wipe day comes?

An average of 7 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY wipe?

The prediction follows its tag, because too few of CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY's wipes are on record to confirm its schedule. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 16 days 16 hours ago the current world was made. Its tags publish a wipe schedule of one wipe every two weeks.

Tags

How should you read the tags on CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY?

Tags published by CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): 100 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^b (Biweekly): It wipes once a fortnight; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^p (PvE): No fighting between players: the world itself is the hazard; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game; NA (North America): The server browser files it under North America. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Who operates CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY?

Most likely the same operator runs them: CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY publishes a creedrustservers.com hostname, and so do 12 other servers we track.

Where does CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY appear in Rust Metrics lists and filters?

Rust Metrics lists featuring CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY: Modded Rust servers, checked live, Rust PvE servers and North America: server readout. Reading: server list filters. It comes up under Region: North America; Type: Vanilla and Modded; Game mode: PvE; Server tag: Biweekly ^b, Vanilla ^v, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.

Occupancy

Where does CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY sit in the rankings?

Top 19% of all ranked servers: CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY takes #4,323 on seven-day player hours and #732 in North America.

What is the population on CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY?

Current headcount on CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY: 0 players, 100 slots available. Check: players over seven days. Average 0, peak 4. Check: 48-hour peak. 23:00 UTC, 1 players on average.

Server

Which location does CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY run from?

CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY gives North America as its location, with the NA tag. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 66.51.99.162:28125.

What Rust version is CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY. To get in, your game needs the same protocol; Steam applies the update.

What is the performance reading for CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY?

Over the last 48 hours the average was 76 server fps; the floor was 51. Reading: 126,152 entities at the highest. That covers buildings, deployables and everything else. Reading: 4,862 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

What is the uptime on CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY, and is it online?

CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY reports online. Status: normal. Reading: uptime. About 5 hours ago it restarted, on its own count. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. The first sighting on Rust Metrics was 9 October 2026.

Map and rules

What rules does CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY enforce, and what are its settings?

Reading the name gives no gather rate for CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY. 8 players per group, the default value. Mode check gives pve; fighting between players is off. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Vanilla is the label it uses: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. Check: anti-cheat. VAC, Valve's system, is on.

What map is CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY on?

Check: map. Procedural, size 4,500, seed 1586544950, generated by the game on CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Its map carries the name Custom Procedural.

Connection

What do you do to join CREED PVE | VANILLA | CHILL | BIG JAWBS | BI-WEEKLY?

To join: start Rust, press F1 and type client.connect 66.51.99.162:28125. Or press Launch Rust here and Steam opens the game and connects you. https://creedrustservers.com is where its website sits.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players 100 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly It wipes once a fortnight.

Difficulty

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

Gameplay

^p
PvE No fighting between players: the world itself is the hazard.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Region

NA
North America The server browser files it under 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.