RUST METRICSFlight deck · live data
Data live Servers11,840 Players88,651 Populated4,028 Fresh wipes 3 h165 Scan5 min
‹ All servers176.237.98.133:28015
Offline Full Queue Fresh wipe Wipe due No query

InfestationZ | Colorado V3

Offline 176.237.98.133:28015 checked 8d 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 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

Wipe schedule

What wipe timing does InfestationZ | Colorado V3 follow?

Its rhythm cannot be told from the wipes of InfestationZ | Colorado V3 on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 9 days 19 hours ago the current world was made.

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): The game mode is plain Rust survival; mp100 (Max players): The server holds 100 slots; ts15 (Group limit): Team cap: 15; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Game build reading: 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Plugin framework in use: Carbon. 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?

These Rust Metrics lists carry 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

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.

How full does InfestationZ | Colorado V3 get?

InfestationZ | Colorado V3 is not responding; status offline, last seen 8 days 20 hours ago.

Operator and location

Where does InfestationZ | Colorado V3 sit?

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 176.237.98.133: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. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on InfestationZ | Colorado V3, and is it online?

Check: connection. InfestationZ | Colorado V3 is offline at this moment. Last contact was 8 days 20 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 19 October 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on InfestationZ | Colorado V3?

Check: gather rate. The name InfestationZ | Colorado V3 does not state one. The cap on groups is 15 players. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Carbon plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

How to join

How can you get onto InfestationZ | Colorado V3?

To join: start Rust, press F1 and type client.connect 176.237.98.133: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 The server holds 100 slots.
ts15
Group limit Team cap: 15.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Game build reading: 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Plugins or settings make this a modded server.
^y
Carbon Plugin framework in use: 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.