Working its way up from the back of the class: #13,792 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
26/ 100
F
Lost ground: down 6,634 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum 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 62% 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.7 daysbetween real wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Thu 1 OctWed 30 Sep
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
Thu 1 Oct, 11:06 UTC28d ago
1
–
running
1
Wed 30 Sep, 18:26 UTC29d ago
1
–
0.7 days
1
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
Where in the world is LOCAL - Staging Livestock Test?
You'll find no region listed by LOCAL - Staging Livestock Test. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 92.209.144.131:28015.
How reliable is LOCAL - Staging Livestock Test, and is it up?
The server is down: LOCAL - Staging Livestock Test is offline now, with the last sighting 23 days 10 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 30 September 2026, Rust Server Score saw it for the first time.
On what Rust version does LOCAL - Staging Livestock Test sit?
The server LOCAL - Staging Livestock Test is on Rust network protocol 2634 and build 166925 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does LOCAL - Staging Livestock Test wipe, and how often?
There are too few wipes on record for LOCAL - Staging Livestock 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. It has been running its current world for 28 days 16 hours.
What happens on LOCAL - Staging Livestock Test when wipe day arrives?
The average peak on its recent wipes was 1 players. 0 hours after the latest wipe began, the crowd hit its peak.
Population
Where does LOCAL - Staging Livestock Test place in the wider field of Rust servers?
Over the last seven days, LOCAL - Staging Livestock Test has #13,792 for player hours, in the top 62% of all ranked servers.
How many players does LOCAL - Staging Livestock Test usually have?
It has been 23 days 10 hours since LOCAL - Staging Livestock Test was last seen, and it is offline right now.
Tags and filters
How should you read the tags on LOCAL - Staging Livestock Test?
The game's browser takes its cue from the tags LOCAL - Staging Livestock Test has set: gmrust (Game mode): Rust survival, played by the standard rules; mp5 (Max players): Its slot count is 5; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166925 (Build): The game build is 166925; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^k (Build server): Design and practise your bases here. 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 LOCAL - Staging Livestock Test appear in the Rust Server Score lists and filters?
These Rust Server Score lists count LOCAL - Staging Livestock Test among them: Rust build and creative servers. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Server tag: Build server ^k; Group limit: 5 or more.
Server rules
Which rules does LOCAL - Staging Livestock Test enforce, and what are its settings?
Nothing in the name of LOCAL - Staging Livestock Test states a gather rate. With no change from the game default, groups take up to 8 players. It runs build & creative, no gathering: sandbox building instead. Under Community in the server browser you will find this community server. You are covered by VAC, Valve's anti-cheat.
Which map is in play on LOCAL - Staging Livestock Test?
The game generates a procedural map for LOCAL - Staging Livestock Test.
Getting in
How do you get onto LOCAL - Staging Livestock Test?
Enter client.connect 92.209.144.131:28015 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 asmp5,ptrak,$r?,v2634,^k,gmrust,cs166925,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp5
Max playersIts slot count is 5.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166925
BuildThe game build is 166925.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Gameplay
^k
Build serverDesign and practise your bases 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 standing (F); momentum is the one to work on (F).