Working its way up from the back of the class: #15,648 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
36/ 100
F
Slipped a little: down 4,364 places this week. Nothing a good wipe can't fix.
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 71% 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 Heartfall BotLab [PRIVATE TEST] based in?
Heartfall BotLab [PRIVATE TEST] leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 92.4.219.59:28015 is the address to use.
How reliable is Heartfall BotLab [PRIVATE TEST], and is it up?
You cannot join now: Heartfall BotLab [PRIVATE TEST] is offline, last seen 16 days 14 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 10 October 2026, Rust Server Score saw it for the first time.
Which Rust version is Heartfall BotLab [PRIVATE TEST] running?
Rust network protocol 2634 and build 167398 on Linux is what Heartfall BotLab [PRIVATE TEST] runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does Heartfall BotLab [PRIVATE TEST] wipe, and how often?
Heartfall BotLab [PRIVATE TEST] 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. It has been running its current world for 18 days 10 hours.
Player count
What position does Heartfall BotLab [PRIVATE TEST] hold in the rankings?
In the top 71% of all ranked servers, Heartfall BotLab [PRIVATE TEST] sits at #15,648 for player hours over the last seven days.
How many players does Heartfall BotLab [PRIVATE TEST] usually have?
Heartfall BotLab [PRIVATE TEST] is offline at the moment; the last time it was seen was 16 days 14 hours ago.
Tags and filters
What do Heartfall BotLab [PRIVATE TEST]'s tags stand for?
gmrust (Game mode): Survival in the standard Rust style; 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): Join only if your game runs protocol 2634; cs167398 (Build): The game build is 167398; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon are the tags Heartfall BotLab [PRIVATE TEST] 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.
Where does Heartfall BotLab [PRIVATE TEST] appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Heartfall BotLab [PRIVATE TEST]: 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.
Map and rules
What settings and rules apply on Heartfall BotLab [PRIVATE TEST]?
Nothing in the name of Heartfall BotLab [PRIVATE TEST] 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. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Heartfall BotLab [PRIVATE TEST] uses?
A procedural map, generated by the game, is what Heartfall BotLab [PRIVATE TEST] runs.
Connecting
What is the way to join Heartfall BotLab [PRIVATE TEST]?
To connect, start Rust, press F1, and type client.connect 92.4.219.59:28015. 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,cs167398,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp40
Max playersIts slot count is 40.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167398
BuildThe game build is 167398.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonPlugin framework: 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. Even marks across the subjects, from F to F.