Working its way up from the back of the class: #13,242 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 895 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to D.
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.
No daily history yet.
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 58% 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
No region is published for Local server 261. Rust Server Score takes the server's word for its location and does not trace the hardware. 87.242.127.43:28015 is the address to use.
How reliable is Local server 261, and is it up?
You cannot join now: Local server 261 is offline, last seen 36 days 11 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 22 September 2026.
On what Rust version does Local server 261 sit?
The server Local server 261 is on Rust network protocol 2633 and build 164530 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does Local server 261 wipe its map?
There are too few wipes on record for Local server 261 to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 36 days 11 hours have passed since this world was made.
Population
What position does Local server 261 hold in the rankings?
In the top 58% of all ranked servers, Local server 261 sits at #13,242 for player hours over the last seven days.
Is Local server 261 a busy server?
The last sighting of Local server 261 was 36 days 11 hours ago, and it is offline right now.
Tags and filters
What is meant by the tags on Local server 261?
You'll see Local server 261 tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp15 (Max players): 15 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs164530 (Build): The game build is 164530; 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): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature Local server 261?
Rust Server Score lists that include Local server 261: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
How is Local server 261 set up, and what rules does it keep?
Nothing in the name of Local server 261 states a 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. You can raid other players and fight them. 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 not enabled.
Which map is in play on Local server 261?
Local server 261 runs a procedural map, which the game generates.
Connecting
How do you get onto Local server 261?
To connect, start Rust, press F1, and type client.connect 87.242.127.43:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp15,ptrak,$r?,v2633,gmrust,cs164530,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp15
Max players15 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs164530
BuildThe game build is 164530.
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
ModdedBecause settings or plugins change how it plays, it is listed as 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 D.