Working its way up from the back of the class: #13,655 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
33/ 100
F
Lost ground: down 4,624 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); wipes are 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.
AveragePeakWipe
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 62% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W·····
·······
···WW··
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap8.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 15
The first 48 hours of its last wipes
Fri 16 OctThu 15 OctTue 29 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 16 Oct, 18:40 UTC11d ago
1
–
running
0
Thu 15 Oct, 20:29 UTC12d ago
1
–
0.9 days
0
Tue 29 Sep, 20:35 UTC28d ago
1
halved by day 15
16 days
0
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
okasha_server leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 188.0.114.67:28015.
How dependable is okasha_server, and is it online at the moment?
At this moment, okasha_server is offline; the last time it was seen was 9 days 14 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 29 September 2026.
On what Rust version does okasha_server sit?
Rust network protocol 2634 and build 167781 on Windows is what okasha_server runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does okasha_server reset?
No next wipe can be predicted for okasha_server, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 11 days 14 hours.
What happens on okasha_server when wipe day arrives?
Recent wipes have peaked at 1 players on average. The crowd on the latest wipe was largest 0 hours after it began. Half the peak held until the next wipe in 0% of its recent wipes. In the other wipes it slipped under half by day 15.
Player numbers
Where does okasha_server place in the wider field of Rust servers?
In the top 62% of all ranked servers, okasha_server sits at #13,655 for player hours over the last seven days.
What does the population on okasha_server look like?
okasha_server is offline at the moment; the last time it was seen was 9 days 14 hours ago.
Tags and filters
What do okasha_server's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): Its slot count is 10; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here are the tags okasha_server publishes, and the game's server browser reads them. 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 okasha_server?
Rust Server Score lists that include okasha_server: 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; Last wipe: In the last 2 weeks.
Map and rules
How is okasha_server set up, and what rules does it keep?
You will find no gather rate in the name of okasha_server. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map okasha_server uses?
The game generates a procedural map for okasha_server.
How to join
What is the way to join okasha_server?
Enter client.connect 188.0.114.67:28015 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 asmp10,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max playersIts slot count is 10.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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 standing (F); wipes are the one to work on (F).