RUST METRICSFlight deck · live data
Data live Servers11,749 Players65,278 Populated3,453 Fresh wipes 3 h195 Scan5 min
‹ All servers176.89.230.20:28015
Offline Full Queue Fresh wipe Wipe due No query

InfestationZ | Colorado V3

Offline 176.89.230.20: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,335top 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 Oct21 Oct22 Oct24 Oct25 Oct27 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 it runs now was made 10 days 14 hours ago.

Tag meanings

Which tags does InfestationZ | Colorado V3 carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts15 (Group limit): You may team up with at most 15; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): The server runs game build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Check: framework. Carbon from InfestationZ | Colorado V3. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show InfestationZ | Colorado V3?

Rust Metrics lists featuring InfestationZ | Colorado V3: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: 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?

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

What player count does InfestationZ | Colorado V3 carry?

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

Server details

Which location does InfestationZ | Colorado V3 run from?

Reading: location. InfestationZ | Colorado V3 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 176.89.230.20: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. Matching protocol is required to join. Let Steam update your game.

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

Reading: offline. InfestationZ | Colorado V3 last answered 9 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 19 October 2026, recorded by Rust Metrics.

Rules and settings

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

Reading the name gives no gather rate for InfestationZ | Colorado V3. Check: group limit. Up to 15 players. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Carbon of them. Anti-cheat reading: VAC on, Valve's system.

How to join

How can you get onto InfestationZ | Colorado V3?

Check: join. Open Rust, press F1, then enter client.connect 176.89.230.20: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 You may team up with at most 15.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build The server runs game build 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Check: framework. Carbon.

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.