Working its way up from the back of the class: #13,364 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
35/ 100
F
Slipped a little: down 4,040 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 61% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
·······
·······
····
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.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
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
Fri 2 Oct, 10:10 UTC26d ago
1
–
running
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
You'll find no region listed by Local Sandbox. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 110.235.162.229:28015.
How reliable is Local Sandbox, and is it up?
You cannot join now: Local Sandbox is offline, last seen 16 days 17 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 30 September 2026, Rust Server Score saw it for the first time.
Which Rust version is Local Sandbox running?
You will find Local Sandbox on Rust network protocol 2634 and build 167398, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does Local Sandbox wipe, and how often?
There are too few wipes on record for Local Sandbox 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. 26 days 20 hours have passed since this world was made.
What happens on Local Sandbox when wipe day arrives?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 0 hours after it began.
Population
What position does Local Sandbox hold in the rankings?
Over the last seven days, Local Sandbox has #13,364 for player hours, in the top 61% of all ranked servers.
How many players does Local Sandbox usually have?
It has been 16 days 17 hours since Local Sandbox was last seen, and it is offline right now.
Tags
What do Local Sandbox's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp2 (Max players): The server holds 2 slots; 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; cs167398 (Build): This runs on build 167398; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here are the tags Local Sandbox publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does Local Sandbox appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Local Sandbox among them: Rust build and creative servers and Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
How is Local Sandbox set up, and what rules does it keep?
The name of Local Sandbox gives no gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map Local Sandbox uses?
A procedural map, generated by the game, is what Local Sandbox runs.
How to join
What is the way to join Local Sandbox?
To connect, start Rust, press F1, and type client.connect 110.235.162.229:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2634,gmrust,cs167398,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp2
Max playersThe server holds 2 slots.
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.
cs167398
BuildThis runs on build 167398.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set 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. Even marks across the subjects, from F to F.