Working its way up from the back of the class: #15,306 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
24/ 100
F
Lost ground: down 8,031 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 13 Oct, 17:54 UTC16d ago
1
–
running
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 Try To Survive. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 45.93.248.71:28199.
Is Try To Survive up, and how steady is its uptime?
At this moment, Try To Survive is offline; the last time it was seen was 10 days 1 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 8 October 2026.
On what Rust version does Try To Survive sit?
The server Try To Survive is on Rust network protocol 2634 and build 167781 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does Try To Survive wipe its map?
There are too few wipes on record for Try To Survive to show a 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 21 days.
What happens on Try To Survive when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. The crowd on the latest wipe was largest 0 hours after it began.
Player numbers
Where does Try To Survive sit among Rust servers?
Over the last seven days, Try To Survive has #15,306 for player hours, in the top 70% of all ranked servers.
Is Try To Survive a busy server?
Try To Survive is offline at the moment; the last time it was seen was 10 days 1 hours ago.
Lists and filters
What is meant by the tags on Try To Survive?
gmrust (Game mode): Rust survival, played by the standard rules; mp40 (Max players): Its slot count is 40; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server are the tags Try To Survive publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does Try To Survive appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Try To Survive: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
How is Try To Survive set up, and what rules does it keep?
You will find no gather rate in the name of Try To Survive. 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. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map Try To Survive uses?
A procedural map, generated by the game, is what Try To Survive runs.
Connecting
How do you get onto Try To Survive?
To connect, start Rust, press F1, and type client.connect 45.93.248.71:28199. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp40
Max playersIts slot count is 40.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
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 F.