Working its way up from the back of the class: #15,102 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
52/ 100
D
Moving up: up 687 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 70% 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
Which region is osmium release selftest (local) based in?
No region is published for osmium release selftest (local). Rust Server Score takes the server's word for its location and does not trace the hardware. 208.88.69.27:28785 is the address to use.
How reliable is osmium release selftest (local), and is it up?
At this moment, osmium release selftest (local) is offline; the last time it was seen was 12 days 12 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 16 October 2026.
On what Rust version does osmium release selftest (local) sit?
The server osmium release selftest (local) is on Rust network protocol 2635 and build 168268 under Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does osmium release selftest (local) wipe its map?
There are too few wipes on record for osmium release selftest (local) 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. It has been running its current world for 12 days 12 hours.
Player numbers
Where does osmium release selftest (local) sit among Rust servers?
In the top 70% of all ranked servers, osmium release selftest (local) sits at #15,102 for player hours over the last seven days.
How many players does osmium release selftest (local) usually have?
The last sighting of osmium release selftest (local) was 12 days 12 hours ago, and it is offline right now.
Lists and filters
How should you read the tags on osmium release selftest (local)?
You'll see osmium release selftest (local) tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp4 (Max players): 4 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168268 (Build): Build number: 168268; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here in the browser, which picks them up from the server. 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.
Where does osmium release selftest (local) appear in the Rust Server Score lists and filters?
Rust Server Score lists that include osmium release selftest (local): Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server rules
How is osmium release selftest (local) set up, and what rules does it keep?
You will find no gather rate in the name of osmium release selftest (local). The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
osmium release selftest (local) runs which map?
The game generates a procedural map for osmium release selftest (local).
Connecting
What is the way to join osmium release selftest (local)?
To connect, start Rust, press F1, and type client.connect 208.88.69.27:28785. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp4,ptrak,$r?,v2635,gmrust,cs168268,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp4
Max players4 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168268
BuildBuild number: 168268.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
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).