RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h90 Scan5 min
‹ All servers178.241.94.248:28015
Offline Full Queue Fresh wipe Wipe due No query

InfestationZ | Colorado V3

Offline 178.241.94.248: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,338top 70%
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
15k10k15k20k20 Oct21 Oct23 Oct24 Oct26 Oct27 Oct

Top 70% 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?

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

Lists and filters

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): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts15 (Group limit): Teams are capped at 15; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Plugin framework in use: Carbon. 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?

On Rust Metrics, InfestationZ | Colorado V3 sits in these lists: 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?

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

What player count does InfestationZ | Colorado V3 carry?

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

Server details

What location is InfestationZ | Colorado V3 hosted in?

No region comes from InfestationZ | Colorado V3. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 178.241.94.248: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. Check: protocol. To join, your game must match; Steam handles the update.

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

Check: connection. InfestationZ | Colorado V3 is offline at this moment. Last contact was 8 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 20 October 2026.

Map and rules

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

Reading the name gives no gather rate for InfestationZ | Colorado V3. Group size, maximum: 15 players. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Plugin count: Carbon. Anti-cheat reading: VAC on, Valve's system.

Join

What do you do to join InfestationZ | Colorado V3?

Check: join. Open Rust, press F1, then enter client.connect 178.241.94.248: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 Teams are capped at 15.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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 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.