A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,426 on player hours.
Uptimehours on the list, last 48
19/ 100
F
Attendance needs work: on the list only 9 of the last 48 hours.
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
49/ 100
D
Slipped a little: down 253 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); population 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.
AveragePeak
Hourly average and peak, UTC.
AveragePeak
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
You'll find no region listed by 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.92.176:28015.
How dependable is InfestationZ | Colorado V3, and is it online at the moment?
At this moment, InfestationZ | Colorado V3 is offline; the last time it was seen was 39 hours ago. It was up 88% of the time over the last 7 full days, 148 of 168 hours. On 20 October 2026, Rust Server Score saw it for the first time.
What Rust version is InfestationZ | Colorado V3 on?
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?
There are too few wipes on record for InfestationZ | Colorado V3 to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 9 days 21 hours.
Player numbers
Where does InfestationZ | Colorado V3 place in the wider field of Rust servers?
Over the last seven days, InfestationZ | Colorado V3 has #15,426 for player hours, in the top 69% of all ranked servers.
What does the population on InfestationZ | Colorado V3 look like?
The last sighting of InfestationZ | Colorado V3 was 39 hours ago, and it is offline right now. For the last seven days, the average number of players was 0.
Lists and filters
What is meant by the tags on InfestationZ | Colorado V3?
The game's browser takes its cue from the tags InfestationZ | Colorado V3 has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): The server holds 100 slots; 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): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature InfestationZ | Colorado V3?
Rust Server Score lists that include InfestationZ | Colorado V3: Modded Rust servers, graded. It shows under the following filters 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.
Rules and settings
What settings and rules apply on InfestationZ | Colorado V3?
Nothing in the name of InfestationZ | Colorado V3 states a gather rate. You can play in groups of up to 15 players. You get survival here, gather and build and raid: 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. VAC, Valve's anti-cheat, is enabled.
How to join
How do you get onto InfestationZ | Colorado V3?
Enter client.connect 217.131.92.176:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
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 playersThe server holds 100 slots.
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
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonThe 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.
A term to build on. Strongest in momentum (D); population is the one to work on (F).