Working its way up from the back of the class: #15,146 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
51/ 100
D
Moving up: up 393 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.
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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 3 Oct. 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
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
Next wipe Saturday 31 October, 19:29 UTC, in 2d 17h.
Weekly: 7 days after its last 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 Try Hard Rust | Fridays | No Tech Tree sit?
Try Hard Rust | Fridays | No Tech Tree leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 62.41.26.27:28015.
How dependable is Try Hard Rust | Fridays | No Tech Tree, and is it online at the moment?
At this moment, Try Hard Rust | Fridays | No Tech Tree is offline; the last time it was seen was 13 days 16 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 3 October 2026.
Which Rust version is Try Hard Rust | Fridays | No Tech Tree running?
The server Try Hard Rust | Fridays | No Tech Tree is on Rust network protocol 2634 and build 166652 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does Try Hard Rust | Fridays | No Tech Tree wipe, and how often?
weekly: 7 days after its last wipe gives the basis for estimating Try Hard Rust | Fridays | No Tech Tree's next wipe. Expect the next wipe on Saturday 31 October at 19:29 UTC. The world it runs now was created 25 days 6 hours. The tags carry a weekly wipe schedule.
Player numbers
What position does Try Hard Rust | Fridays | No Tech Tree hold in the rankings?
Over the last seven days, Try Hard Rust | Fridays | No Tech Tree has #15,146 for player hours, in the top 70% of all ranked servers.
How many players does Try Hard Rust | Fridays | No Tech Tree usually have?
Try Hard Rust | Fridays | No Tech Tree is offline at the moment; the last time it was seen was 13 days 16 hours ago.
Tags and filters
What do Try Hard Rust | Fridays | No Tech Tree's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp200 (Max players): 200 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): This runs on build 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^w (Weekly): It wipes weekly; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^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 Try Hard Rust | Fridays | No Tech Tree 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 Rust Server Score filters and lists feature Try Hard Rust | Fridays | No Tech Tree?
These Rust Server Score lists count Try Hard Rust | Fridays | No Tech Tree among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Weekly.
Rules and settings
Which rules does Try Hard Rust | Fridays | No Tech Tree enforce, and what are its settings?
You will find no gather rate in the name of Try Hard Rust | Fridays | No Tech Tree. With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. The vanilla label is its own: facepunch's own version, with no changed rates, kits or rules. You are covered by VAC, Valve's anti-cheat.
Try Hard Rust | Fridays | No Tech Tree runs which map?
The game generates the procedural map on Try Hard Rust | Fridays | No Tech Tree, at size 5,000. The name of the map reads: Hardcore Rust Server.
Connecting
How should you connect to Try Hard Rust | Fridays | No Tech Tree?
Enter client.connect 62.41.26.27:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://rusttryhard.fun/.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2634,^z,^y,^w,^v,gmrust,cs166652,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp200
Max players200 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^w
WeeklyIt wipes weekly.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
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 momentum (D); standing is the one to work on (F).