Rust HeatmapInfrared · players
IR live Players34,156 Servers11,596 Warm2,853 Fresh wipes · 3h63 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 0° now Linear · 0–100° · slots

InfestationZ | Colorado V3

Offline 178.246.202.87:28015 checked 8d ago

moddedcarbon
Sp1 · players now 0/ 100
0% full
Li1 · players, the last 48 hours · hourly average, UTC
No hourly readings in the last 48 hours
0
7-day average
peak –
#15,315
rank
top 69%
9d ago
last wipe
no schedule published
–
next wipe
no wipe seen yet
UTC checked 8d ago

Li2Players

No hourly history yet.

Hourly average and peak, UTC.

Li3Server 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.

Li4Rank

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.

Bx1Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit
no group limit · 158 on average
49 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10
EU · groups of 8+ · weekly · 128 on average
131 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
EU · groups of 16+ · weekly · 114 on average
0 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
EU · groups of 16+ · monthly · 88 on average
29 / 700
RustSpain.com | EU Main
EU · groups of 12+ · weekly · 87 on average
5 / 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10
EU · groups of 16+ · monthly · 83 on average
12 / 1000

LogQuick answers

from the figures on this page

Wipe day

What is the wipe schedule on InfestationZ | Colorado V3?

Its rhythm cannot yet be told: too few of InfestationZ | Colorado V3's wipes are on record. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. The world it runs now dates from 9 days 7 hours ago.

Population

How busy is InfestationZ | Colorado V3?

InfestationZ | Colorado V3 went quiet 8 days 9 hours ago and is offline right now.

How does InfestationZ | Colorado V3 rank against other Rust servers?

Player hours over seven days put InfestationZ | Colorado V3 at #15,315, in the top 69% of ranked servers.

Map and rules

What are the rules and settings on InfestationZ | Colorado V3?

A gather rate is not given in the name InfestationZ | Colorado V3. The group limit is 15 players. survival is the game mode, standard play: gathering, building and raiding. You can fight other players and raid their bases. In the server browser it is Modded, meaning plugins or settings modify the game. Carbon plugins run on this server. Anti-cheat: Valve's VAC is on.

Location and uptime

Which version of Rust does InfestationZ | Colorado V3 run?

Rust network protocol 2634 and build 167781 is the build InfestationZ | Colorado V3 runs, on Windows. To join, your game must match the protocol; Steam handles the update.

Is InfestationZ | Colorado V3 online, and how reliable is it?

InfestationZ | Colorado V3 is down just now; the last sighting was 8 days 9 hours ago. 0 of 168 hours up over the last 7 full days, which is 0%. The first record of it on Rust Heatmap is 19 October 2026.

Where is InfestationZ | Colorado V3 located?

No region is published by InfestationZ | Colorado V3. Rust Heatmap shows the location a server states. It does not look up the machine's location. You can reach it at 178.246.202.87:28015.

Tags

Which Rust Heatmap lists and filters include InfestationZ | Colorado V3?

The Rust Heatmap lists that InfestationZ | Colorado V3 fits are: Modded Rust servers, by live population. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

What do the server tags on InfestationZ | Colorado V3 mean?

gmrust (Game mode): Rust survival, standard rules; mp100 (Max players): The slot count is 100; ts15 (Group limit): Teams cap at 15; v2634 (Protocol): The server runs game protocol 2634, so your game has to match it; cs167781 (Build): This build is 167781; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): A region code is not set; ^z (Modded): The game is changed by settings or plugins, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon are the tags InfestationZ | Colorado V3 publishes, and the server browser reads them. The top of this page also shows the tags for players now, the queue and when the world was made.

Connect

How do I join InfestationZ | Colorado V3?

Enter client.connect 178.246.202.87:28015 in the console, opened with F1 in Rust. Or use Launch Rust here, which opens the game through Steam and connects you.

KeyServer tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs167781,ts15,^z,^y

Game

gmrust
Game mode Rust survival, standard rules.
mp100
Max players The slot count is 100.
ts15
Group limit Teams cap at 15.
v2634
Protocol The server runs game protocol 2634, so your game has to match it.
cs167781
Build This build is 167781.
ptrak
Networking Standard game networking here, which is RakNet.
$r?
Region code A region code is not set.

Mods and access

^z
Modded The game is changed by settings or plugins, so it sits under Modded.
^y
Carbon The plugin framework in use is 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.