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
In what location does osmium dev p1c-osmium (local) sit?
No region is published for osmium dev p1c-osmium (local). The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 208.88.69.27:28610.
Is osmium dev p1c-osmium (local) up, and how steady is its uptime?
The server is down: osmium dev p1c-osmium (local) is offline now, with the last sighting 19 days 16 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 9 October 2026.
On what Rust version does osmium dev p1c-osmium (local) sit?
Rust network protocol 2634 and build 167231 on Linux is what osmium dev p1c-osmium (local) runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does osmium dev p1c-osmium (local) wipe its map?
There are too few wipes on record for osmium dev p1c-osmium (local) to show a 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 16 hours.
Player count
What position does osmium dev p1c-osmium (local) hold in the rankings?
Over the last seven days, osmium dev p1c-osmium (local) has #15,869 for player hours, in the top 72% of all ranked servers.
How many players does osmium dev p1c-osmium (local) usually have?
The last sighting of osmium dev p1c-osmium (local) was 19 days 16 hours ago, and it is offline right now.
Lists and filters
How should you read the tags on osmium dev p1c-osmium (local)?
You'll see osmium dev p1c-osmium (local) tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; 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): To get in, your game needs to be on the same version: the protocol is 2634; cs167231 (Build): The game build is 167231; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. 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 osmium dev p1c-osmium (local)?
Rust Server Score lists that include osmium dev p1c-osmium (local): Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
How is osmium dev p1c-osmium (local) set up, and what rules does it keep?
You will find no gather rate in the name of osmium dev p1c-osmium (local). 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. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on osmium dev p1c-osmium (local)?
osmium dev p1c-osmium (local) runs a procedural map, which the game generates.
Getting in
How should you connect to osmium dev p1c-osmium (local)?
To connect, start Rust, press F1, and type client.connect 208.88.69.27:28610. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp4,ptrak,$r?,v2634,gmrust,cs167231,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp4
Max playersIts slot count is 4.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167231
BuildThe game build is 167231.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^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).