Working its way up from the back of the class: #15,328 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
50/ 100
D
Holding steady: up 113 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
No daily history yet.
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
In what location does InfestationZ | Colorado V3 sit?
No region is published for InfestationZ | Colorado V3. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 176.89.254.175:28015.
Is InfestationZ | Colorado V3 up, and how steady is its uptime?
The server is down: InfestationZ | Colorado V3 is offline now, with the last sighting 10 days 2 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 19 October 2026.
Which Rust version is InfestationZ | Colorado V3 running?
The server InfestationZ | Colorado V3 is on Rust network protocol 2634 and build 167781 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does InfestationZ | Colorado V3 wipe its map?
InfestationZ | Colorado V3 has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 11 days 1 hours have passed since this world was made.
Player numbers
Where does InfestationZ | Colorado V3 sit among Rust servers?
Over the last seven days, InfestationZ | Colorado V3 has #15,328 for player hours, in the top 69% of all ranked servers.
How many players does InfestationZ | Colorado V3 usually have?
InfestationZ | Colorado V3 is offline at the moment; the last time it was seen was 10 days 2 hours ago.
Lists and filters
How should you read the tags on InfestationZ | Colorado V3?
You'll see InfestationZ | Colorado V3 tagged with gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): The server holds 100 slots; ts15 (Group limit): A team can hold 15 players at most; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): The plugin framework in use is Carbon in the browser, which picks them up from the server. 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 lists and filters on Rust Server Score show InfestationZ | Colorado V3?
Rust Server Score lists that include InfestationZ | Colorado V3: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server rules
How is InfestationZ | Colorado V3 set up, and what rules does it keep?
Nothing in the name of InfestationZ | Colorado V3 states a gather rate. The limit for a group is 15 players. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. The server runs Valve's anti-cheat, VAC.
Connecting
What is the way to join InfestationZ | Colorado V3?
Enter client.connect 176.89.254.175: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 modeSurvival in the standard Rust style.
mp100
Max playersThe server holds 100 slots.
ts15
Group limitA team can hold 15 players at most.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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); standing is the one to work on (F).