Working its way up from the back of the class: #15,310 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
48/ 100
D
Slipped a little: down 514 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 70% of all ranked servers, and #202 of the solo servers (top 90%). 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
In what location does Last Stronghold (local test) sit?
No region is published for Last Stronghold (local test). The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 5.31.2.129:28015.
Is Last Stronghold (local test) up, and how steady is its uptime?
You cannot join now: Last Stronghold (local test) is offline, last seen 8 days 11 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 1 October 2026, Rust Server Score saw it for the first time.
What Rust version is Last Stronghold (local test) on?
You will find Last Stronghold (local test) on Rust network protocol 2634 and build 166494, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does Last Stronghold (local test) reset?
Last Stronghold (local test) has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 25 days 19 hours have passed since this world was made.
Player count
Where does Last Stronghold (local test) sit among Rust servers?
In the top 70% of all ranked servers, Last Stronghold (local test) sits at #15,310 for player hours over the last seven days. In the solo group, it ranks #202.
How many players does Last Stronghold (local test) usually have?
It has been 8 days 11 hours since Last Stronghold (local test) was last seen, and it is offline right now.
Lists and filters
What do Last Stronghold (local test)'s tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp8 (Max players): 8 slots are available; ts1 (Group limit): No team may go above 1; v2634 (Protocol): Join only if your game runs protocol 2634; cs166494 (Build): The game build is 166494; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags Last Stronghold (local test) 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 Rust Server Score filters and lists feature Last Stronghold (local test)?
These Rust Server Score lists count Last Stronghold (local test) among them: Modded Rust servers, graded and Solo Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Solo.
Map and rules
How is Last Stronghold (local test) set up, and what rules does it keep?
You will find no gather rate in the name of Last Stronghold (local test). This is a solo-only server, so teams cannot form. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
How to join
How do you get onto Last Stronghold (local test)?
To connect, start Rust, press F1, and type client.connect 5.31.2.129:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp8,ptrak,$r?,v2634,gmrust,cs166494,ts1,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp8
Max players8 slots are available.
ts1
Group limitNo team may go above 1.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166494
BuildThe game build is 166494.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits 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. Strongest in momentum (D); standing is the one to work on (F).