Working its way up from the back of the class: #15,869 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
50/ 100
D
Holding steady: up 89 places this week.
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.
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 72% 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 osmium dev p3 (local). Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 208.88.69.27:28650.
How reliable is osmium dev p3 (local), and is it up?
The server is down: osmium dev p3 (local) is offline now, with the last sighting 19 days 18 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 9 October 2026, Rust Server Score saw it for the first time.
Which Rust version is osmium dev p3 (local) running?
The server osmium dev p3 (local) is on Rust network protocol 2634 and build 167231 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does osmium dev p3 (local) wipe its map?
osmium dev p3 (local) has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 19 days 18 hours.
Player numbers
Where does osmium dev p3 (local) sit among Rust servers?
In the top 72% of all ranked servers, osmium dev p3 (local) sits at #15,869 for player hours over the last seven days.
How many players does osmium dev p3 (local) usually have?
It has been 19 days 18 hours since osmium dev p3 (local) was last seen, and it is offline right now.
Tags and filters
What do osmium dev p3 (local)'s tags stand for?
The game's browser takes its cue from the tags osmium dev p3 (local) has set: gmrust (Game mode): Rust survival, played by the standard rules; mp4 (Max players): Its slot count is 4; 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; cs167231 (Build): This runs on build 167231; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this 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 osmium dev p3 (local)?
Rust Server Score lists that include osmium dev p3 (local): Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
How is osmium dev p3 (local) set up, and what rules does it keep?
The name of osmium dev p3 (local) gives no gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. 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 osmium dev p3 (local)?
A procedural map, generated by the game, is what osmium dev p3 (local) runs.
Connecting
How do you get onto osmium dev p3 (local)?
Enter client.connect 208.88.69.27:28650 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 asmp4,ptrak,$r?,v2634,gmrust,cs167231,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp4
Max playersIts slot count is 4.
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.
cs167231
BuildThis runs on build 167231.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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).