Working its way up from the back of the class: #15,311 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
16/ 100
F
Lost ground: down 10,383 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap0.3 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Sun 18 OctSun 18 OctSun 18 Oct
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 18 Oct, 18:02 UTC9d ago
0
–
running
0
Sun 18 Oct, 10:52 UTC9d ago
0
–
0.3 days
0
Sun 18 Oct, 04:42 UTC10d ago
0
–
0.3 days
0
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for InfestationZ | Colorado V3. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 217.131.66.69:28015.
How dependable is InfestationZ | Colorado V3, and is it online at the moment?
You cannot join now: InfestationZ | Colorado V3 is offline, last seen 8 days 18 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 13 October 2026, Rust Server Score saw it for the first time.
On what Rust version does InfestationZ | Colorado V3 sit?
The server InfestationZ | Colorado V3 is on Rust network protocol 2634 and build 167781 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does InfestationZ | Colorado V3 reset?
No next wipe can be predicted for InfestationZ | Colorado V3, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 9 days 7 hours.
What happens on InfestationZ | Colorado V3 when wipe day arrives?
The average peak on its recent wipes was 0 players. The crowd on the latest wipe was largest 0 hours after it began.
Population
Where does InfestationZ | Colorado V3 sit among Rust servers?
Over the last seven days, InfestationZ | Colorado V3 has #15,311 for player hours, in the top 70% of all ranked servers.
Is InfestationZ | Colorado V3 a busy server?
The last sighting of InfestationZ | Colorado V3 was 8 days 18 hours ago, and it is offline right now.
Tags
How should you read the tags on InfestationZ | Colorado V3?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): Its slot count is 100; ts15 (Group limit): Teams cap out at 15; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Carbon provides the plugin framework here are the tags InfestationZ | Colorado V3 publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show InfestationZ | Colorado V3?
Rust Server Score lists that include InfestationZ | Colorado V3: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
Which rules does InfestationZ | Colorado V3 enforce, and what are its settings?
The name of InfestationZ | Colorado V3 gives no gather rate. You can play in groups of up to 15 players. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Carbon plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Getting in
What is the way to join InfestationZ | Colorado V3?
To connect, start Rust, press F1, and type client.connect 217.131.66.69:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,gmrust,cs167781,ts15,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersIts slot count is 100.
ts15
Group limitTeams cap out at 15.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonCarbon provides the plugin framework 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.
A term to build on. Strongest in standing (F); momentum is the one to work on (F).