RUST METRICSFlight deck · live data
Data live Servers11,766 Players66,169 Populated3,487 Fresh wipes 3 h192 Scan5 min
‹ All servers176.237.108.134:28015
Offline Full Queue Fresh wipe Wipe due No query

InfestationZ | Colorado V3

Offline 176.237.108.134:28015 checked 9d ago

moddedcarbon
COM 1 · connect
Launch Rust and join

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

Reset cycle

What wipe timing does InfestationZ | Colorado V3 follow?

To tell the rhythm of InfestationZ | Colorado V3, too few of its wipes 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.

Tags

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

These are the tags InfestationZ | Colorado V3 publishes, and the server browser reads them: 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): 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): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Check: framework. Carbon. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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.

Occupancy

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

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?

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

Server

Where does InfestationZ | Colorado V3 sit?

No region comes from InfestationZ | Colorado V3. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 176.237.108.134: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.

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

Reading: offline. InfestationZ | Colorado V3 last answered 9 days 15 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.

Settings and map

What settings and rules apply on InfestationZ | Colorado V3?

Reading the name gives no gather rate for InfestationZ | Colorado V3. Check: group limit. Up to 15 players. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Carbon of them. Anti-cheat reading: VAC on, Valve's system.

Connection

How can you get onto InfestationZ | Colorado V3?

To join: start Rust, press F1 and type client.connect 176.237.108.134:28015. Or press Launch Rust here and Steam opens the game 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 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 Check: category. Modded, because plugins or settings alter the 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.