Working its way up from the back of the class: #15,861 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
42/ 100
F
Slipped a little: down 2,521 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (F); 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.
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 72% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····WW·
·······
·······
·····
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.
usual gap0.3 daysbetween real wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Sat 10 OctFri 9 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 10 Oct, 01:22 UTC20d ago
1
–
running
0
Fri 9 Oct, 17:18 UTC20d ago
1
–
0.3 days
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
RustAimLab (private) leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 150.220.36.191:28415.
How reliable is RustAimLab (private), and is it up?
At this moment, RustAimLab (private) is offline; the last time it was seen was 18 days 22 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 8 October 2026.
Which Rust version is RustAimLab (private) running?
You will find RustAimLab (private) on Rust network protocol 2634 and build 166494, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does RustAimLab (private) wipe its map?
The record holds too few of RustAimLab (private)'s wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 20 days have passed since this world was made.
What should you expect from wipe day on RustAimLab (private)?
The average peak on its recent wipes was 1 players. Peak numbers came 1 hours into the latest wipe.
Population
Where does RustAimLab (private) sit among Rust servers?
In the top 72% of all ranked servers, RustAimLab (private) sits at #15,861 for player hours over the last seven days.
Is RustAimLab (private) a busy server?
RustAimLab (private) is offline at the moment; the last time it was seen was 18 days 22 hours ago.
Tags and filters
What do RustAimLab (private)'s tags stand for?
The game's browser takes its cue from the tags RustAimLab (private) has set: gmrust (Game mode): Rust survival, played by the standard rules; mp4 (Max players): The server holds 4 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs166494 (Build): Build number: 166494; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature RustAimLab (private)?
These Rust Server Score lists count RustAimLab (private) among them: Modded Rust servers, graded and Rust combat training servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Server rules
What settings and rules apply on RustAimLab (private)?
The name of RustAimLab (private) gives no gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Carbon. VAC, Valve's anti-cheat, is enabled.
Getting in
How do you get onto RustAimLab (private)?
Enter client.connect 150.220.36.191:28415 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 asmp4,ptrak,$r?,v2634,gmrust,cs166494,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp4
Max playersThe server holds 4 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166494
BuildBuild number: 166494.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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. Strongest in momentum (F); standing is the one to work on (F).