RUST METRICSFlight deck · live data
Data live Servers11,736 Players71,890 Populated3,632 Fresh wipes 3 h134 Scan5 min
‹ All servers178.241.89.192:28015
Offline Full Queue Fresh wipe Wipe due No query

InfestationZ | Colorado V3

Offline 178.241.89.192: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,328top 69%
Last wipe9d 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

How often does InfestationZ | Colorado V3 wipe, and when?

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 9 days 15 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): The game mode is plain Rust survival; mp100 (Max players): 100 slots in total; ts15 (Group limit): Teams are capped at 15; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Game build reading: 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^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.

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

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.

Population

What position does InfestationZ | Colorado V3 hold among Rust servers?

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

What is the population on InfestationZ | Colorado V3?

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

Operator and location

Where does InfestationZ | Colorado V3 sit?

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

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

InfestationZ | Colorado V3 reports offline. The last reading came 8 days 16 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.

Settings and map

How is InfestationZ | Colorado V3 configured, and what rules are in force?

No gather rate appears in the name: InfestationZ | Colorado V3. Check: group limit. Up to 15 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Carbon plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

Join

How can you get onto InfestationZ | Colorado V3?

Check: join. Open Rust, press F1, then enter client.connect 178.241.89.192: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 Teams are capped at 15.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build Game build reading: 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

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.