Working its way up from the back of the class: #16,952 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
47/ 100
D
Slipped a little: down 1,065 places this week. Nothing a good wipe can't fix.
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.
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
You'll find no region listed by LOCAL LOOT BOX TEST. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 149.154.11.115:28215.
How reliable is LOCAL LOOT BOX TEST, and is it up?
You cannot join now: LOCAL LOOT BOX TEST is offline, last seen 31 days 9 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 26 September 2026.
On what Rust version does LOCAL LOOT BOX TEST sit?
You will find LOCAL LOOT BOX TEST on Rust network protocol 2633 and build 165217, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does LOCAL LOOT BOX TEST wipe its map?
There are too few wipes on record for LOCAL LOOT BOX TEST to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 32 days 22 hours.
Player numbers
Where does LOCAL LOOT BOX TEST place in the wider field of Rust servers?
Over the last seven days, LOCAL LOOT BOX TEST has #16,952 for player hours, in the top 71% of all ranked servers.
Is LOCAL LOOT BOX TEST a busy server?
It has been 31 days 9 hours since LOCAL LOOT BOX TEST was last seen, and it is offline right now.
Lists and filters
What is meant by the tags on LOCAL LOOT BOX TEST?
gmrust (Game mode): Survival in the standard Rust style; mp0 (Max players): 0 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): This runs on build 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^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 LOCAL LOOT BOX 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 LOCAL LOOT BOX TEST appear in the Rust Server Score lists and filters?
Rust Server Score lists that include LOCAL LOOT BOX 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.
Server rules
Which rules does LOCAL LOOT BOX TEST enforce, and what are its settings?
You will find no gather rate in the name of LOCAL LOOT BOX TEST. The group limit stays at the game's default of 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. VAC, Valve's anti-cheat, is enabled.
Which map is in play on LOCAL LOOT BOX TEST?
The game generates a procedural map for LOCAL LOOT BOX TEST.
Connecting
How should you connect to LOCAL LOOT BOX TEST?
To connect, start Rust, press F1, and type client.connect 149.154.11.115:28215. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp0,ptrak,$r?,v2633,gmrust,cs165217,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp0
Max players0 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
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).