RUST METRICSFlight deck · live data
Data live Servers11,637 Players32,508 Populated2,805 Fresh wipes 3 h70 Scan5 min
‹ All servers151.250.255.111:28015
Online Full Queue Fresh wipe Wipe due No query

InfestationZ | Colorado V3

Online 151.250.255.111:28015 checked 8m 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,349top 69%
Last wipe10d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players
AveragePeak
0123405:0014:0023:0008:0017:0003:00

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
15k10k15k20k27 Oct28 Oct29 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 timing

What wipe timing does InfestationZ | Colorado V3 follow?

The rhythm of InfestationZ | Colorado V3's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 10 days 7 hours ago the current world was made.

Tags

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): Teams are capped at 15; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): The server runs game build 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): Carbon handles the plugins here from InfestationZ | Colorado V3. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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

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?

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

How full does InfestationZ | Colorado V3 get?

0 of 100 slots are filled on InfestationZ | Colorado V3 right now. A seven-day average of 0 players is the reading.

Operator and location

Which location does InfestationZ | Colorado V3 run from?

Reading: location. InfestationZ | Colorado V3 gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 151.250.255.111: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.

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

InfestationZ | Colorado V3 reports online. Status: normal. Uptime for the last 1 full day: 23 of 24 hours, or 96%. The first sighting on Rust Metrics was 27 October 2026.

Settings and map

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

Check: gather rate. The name InfestationZ | Colorado V3 does not state one. Group size, maximum: 15 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. 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?

To join: start Rust, press F1 and type client.connect 151.250.255.111: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 Survival, as standard Rust plays it.
mp100
Max players The server holds 100 slots.
ts15
Group limit Teams are capped at 15.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build The server runs game build 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 Carbon handles the plugins here.

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.