RUST METRICSFlight deck · live data
Data live Servers11,883 Players104,335 Populated3,951 Fresh wipes 3 h530 Scan5 min
‹ All servers178.246.230.123:28015
Offline Full Queue Fresh wipe Wipe due No query

InfestationZ | Colorado V3

Offline 178.246.230.123:28015 checked 9d 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,328top 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

Wipe schedule

What wipe timing does InfestationZ | Colorado V3 follow?

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

Lists and filters

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

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): 100 slots in total; ts15 (Group limit): You may team up with at most 15; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Carbon handles the plugins here from InfestationZ | Colorado V3. 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?

Rust Metrics lists featuring InfestationZ | Colorado V3: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Occupancy

Where does InfestationZ | Colorado V3 sit in the rankings?

Player hours over seven days put InfestationZ | Colorado V3 at #15,328, in the top 69% of all ranked servers.

What player count does InfestationZ | Colorado V3 carry?

Reading for InfestationZ | Colorado V3: offline at this moment; last seen 9 days 23 hours ago.

Operator and location

Which location does InfestationZ | Colorado V3 run from?

No region tag on InfestationZ | Colorado V3. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 178.246.230.123:28015.

What Rust version is InfestationZ | Colorado V3 on?

Rust network protocol 2634 and build 167781 on Windows is the build InfestationZ | Colorado V3 runs. To get in, your game needs the same protocol; Steam applies the update.

Is InfestationZ | Colorado V3 up, and how often does it stay up?

Reading: offline. InfestationZ | Colorado V3 last answered 9 days 23 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 19 October 2026.

Map and rules

What settings and rules apply on InfestationZ | Colorado V3?

Check: gather rate. The name InfestationZ | Colorado V3 does not state one. Check: group limit. Up to 15 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Carbon. Anti-cheat reading: VAC on, Valve's system.

Connection

What do you do to join InfestationZ | Colorado V3?

Check: join. Open Rust, press F1, then enter client.connect 178.246.230.123: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 The game mode is plain Rust survival.
mp100
Max players 100 slots in total.
ts15
Group limit You may team up with at most 15.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Game build reading: 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Mods and access

^z
Modded Plugins or settings make this a modded server.
^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.