Working its way up from the back of the class: #9,959 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
46/ 100
D
Slipped a little: down 789 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from D to C−.
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 45% 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 player (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:28751.
How reliable is osmium dev player (local), and is it up?
You cannot join now: osmium dev player (local) is offline, last seen 9 days 4 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 19 October 2026.
What Rust version is osmium dev player (local) on?
Rust network protocol 2634 and build 167231 on Linux is what osmium dev player (local) runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does osmium dev player (local) wipe its map?
The record holds too few of osmium dev player (local)'s wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 9 days 5 hours have passed since this world was made.
Player numbers
Where does osmium dev player (local) sit among Rust servers?
Over the last seven days, osmium dev player (local) has #9,959 for player hours, in the top 45% of all ranked servers.
How many players does osmium dev player (local) usually have?
It has been 9 days 4 hours since osmium dev player (local) was last seen, and it is offline right now.
Lists and filters
How should you read the tags on osmium dev player (local)?
The game's browser takes its cue from the tags osmium dev player (local) has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp4 (Max players): Its slot count is 4; ts20 (Group limit): No team may go above 20; v2634 (Protocol): Join only if your game runs protocol 2634; cs167231 (Build): The game build is 167231; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature osmium dev player (local)?
Rust Server Score lists that include osmium dev player (local): Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Rules and settings
What settings and rules apply on osmium dev player (local)?
You will find no gather rate in the name of osmium dev player (local). A group here can reach 20 players. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on osmium dev player (local)?
The game generates a procedural map for osmium dev player (local).
Connecting
How should you connect to osmium dev player (local)?
Enter client.connect 208.88.69.27:28751 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,ts20,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp4
Max playersIts slot count is 4.
ts20
Group limitNo team may go above 20.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167231
BuildThe game build is 167231.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^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 D to C−.