Working its way up from the back of the class: #13,507 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
45/ 100
D
Slipped a little: down 1,445 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to D.
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 62% 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
Which region is TroubleChute's Rust Guide Server based in?
TroubleChute's Rust Guide Server leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 217.194.249.123:28015.
How dependable is TroubleChute's Rust Guide Server, and is it online at the moment?
At this moment, TroubleChute's Rust Guide Server is offline; the last time it was seen was 13 days 17 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 14 October 2026.
What Rust version is TroubleChute's Rust Guide Server on?
Rust network protocol 2634 and build 167781 on Windows is what TroubleChute's Rust Guide Server runs. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does TroubleChute's Rust Guide Server reset?
The record holds too few of TroubleChute's Rust Guide Server's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 15 days.
Player count
Where does TroubleChute's Rust Guide Server place in the wider field of Rust servers?
Over the last seven days, TroubleChute's Rust Guide Server has #13,507 for player hours, in the top 62% of all ranked servers.
What does the population on TroubleChute's Rust Guide Server look like?
TroubleChute's Rust Guide Server is offline at the moment; the last time it was seen was 13 days 17 hours ago.
Tags and filters
How should you read the tags on TroubleChute's Rust Guide Server?
The game's browser takes its cue from the tags TroubleChute's Rust Guide Server has set: gmrust (Game mode): Rust survival, played by the standard rules; mp250 (Max players): 250 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set. 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 TroubleChute's Rust Guide Server?
Rust Server Score lists that include TroubleChute's Rust Guide Server: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
Which rules does TroubleChute's Rust Guide Server enforce, and what are its settings?
Nothing in the name of TroubleChute's Rust Guide Server states a gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. The server runs Valve's anti-cheat, VAC.
TroubleChute's Rust Guide Server runs which map?
TroubleChute's Rust Guide Server runs a procedural map, which the game generates.
How to join
How do you get onto TroubleChute's Rust Guide Server?
Enter client.connect 217.194.249.123: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 asmp250,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp250
Max players250 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
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. Even marks across the subjects, from F to D.