Working its way up from the back of the class: #15,172 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
32/ 100
F
Lost ground: down 5,551 places this week. A strong wipe could turn it round.
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 70% of all ranked servers, and #623 of the quad servers (top 75%). 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 Finn Sandbox (private). Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 181.111.7.56:28015.
How dependable is Finn Sandbox (private), and is it online at the moment?
The server is down: Finn Sandbox (private) is offline now, with the last sighting 11 days 14 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 16 October 2026, Rust Server Score saw it for the first time.
On what Rust version does Finn Sandbox (private) sit?
You will find Finn Sandbox (private) on Rust network protocol 2634 and build 167781, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Finn Sandbox (private) wipe, and how often?
There are too few wipes on record for Finn Sandbox (private) to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 12 days 13 hours have passed since this world was made.
Player count
Where does Finn Sandbox (private) place in the wider field of Rust servers?
Over the last seven days, Finn Sandbox (private) has #15,172 for player hours, in the top 70% of all ranked servers. It comes #623 among servers in the quad group.
What does the population on Finn Sandbox (private) look like?
It has been 11 days 14 hours since Finn Sandbox (private) was last seen, and it is offline right now.
Tags and filters
What do Finn Sandbox (private)'s tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp8 (Max players): The server holds 8 slots; ts4 (Group limit): A team can hold 4 players at most; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags Finn Sandbox (private) publishes, and the game's server browser reads them. 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 lists and filters on Rust Server Score show Finn Sandbox (private)?
These Rust Server Score lists count Finn Sandbox (private) among them: Modded Rust servers, graded and Rust build and creative servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Quad; Last wipe: In the last 2 weeks.
Map and rules
What settings and rules apply on Finn Sandbox (private)?
Nothing in the name of Finn Sandbox (private) states a gather rate. You can have up to 4 players in a group (quad). survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Finn Sandbox (private) runs which map?
A procedural map, generated by the game, is what Finn Sandbox (private) runs.
Getting in
How should you connect to Finn Sandbox (private)?
Enter client.connect 181.111.7.56: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 asmp8,ptrak,$r?,v2634,gmrust,cs167781,ts4,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp8
Max playersThe server holds 8 slots.
ts4
Group limitA team can hold 4 players at most.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
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.