RUST METRICSFlight deck · live data
Data live Servers11,772 Players62,070 Populated3,548 Fresh wipes 3 h127 Scan5 min
‹ All servers176.237.110.69:28015
Offline Full Queue Fresh wipe Wipe due No query

InfestationZ | Colorado V3

Offline 176.237.110.69:28015 checked 8d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,332top 69%
Last wipe10d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k19 Oct20 Oct22 Oct23 Oct25 Oct26 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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

When does InfestationZ | Colorado V3 wipe?

The rhythm of InfestationZ | Colorado V3's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 10 days ago.

Lists and filters

How should you read the tags on InfestationZ | Colorado V3?

These are the tags InfestationZ | Colorado V3 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts15 (Group limit): Teams are capped at 15; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Carbon handles the plugins here. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does InfestationZ | Colorado V3 appear in Rust Metrics lists and filters?

On Rust Metrics, InfestationZ | Colorado V3 sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Population

Where does InfestationZ | Colorado V3 sit in the rankings?

Ranking for InfestationZ | Colorado V3: #15,332 on seven-day player hours, top 69% of all ranked servers.

What is the population on InfestationZ | Colorado V3?

Status for InfestationZ | Colorado V3: offline. Last seen 8 days 23 hours ago.

Operator and location

What location is InfestationZ | Colorado V3 hosted in?

No region tag on InfestationZ | Colorado V3. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 176.237.110.69:28015.

What Rust version is InfestationZ | Colorado V3 on?

Version check: Rust network protocol 2634 and build 167781 on Windows, run by InfestationZ | Colorado V3. To get in, your game needs the same protocol; Steam applies the update.

How reliable is InfestationZ | Colorado V3, and is it online now?

InfestationZ | Colorado V3 reports offline. The last reading came 8 days 23 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 19 October 2026.

Map and rules

What rules does InfestationZ | Colorado V3 enforce, and what are its settings?

Reading the name gives no gather rate for InfestationZ | Colorado V3. The cap on groups is 15 players. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Carbon. Check: anti-cheat. VAC, Valve's system, is on.

Connection

What do you do to join InfestationZ | Colorado V3?

Check: join. Open Rust, press F1, then enter client.connect 176.237.110.69:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs167781,ts15,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players The server holds 100 slots.
ts15
Group limit Teams are capped at 15.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Build 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Carbon handles the plugins here.

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.