Station XX-13655 · no signal
okasha_server
Offline 188.0.114.67:28015 checked 9d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,655
- top 62%
- Last wipe
- 11d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 8.5 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 0%else halves by day 15
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 16 Oct, 18:40 UTC11d ago | M0.0▲rising | 1 | – | running | 0 | |
| Thu 15 Oct, 20:29 UTC12d ago | M0.0▲rising | 1 | – | 0.9 days | 0 | |
| Tue 29 Sep, 20:35 UTC28d ago | M0.0▲rising | 1 | halved by day 15 | 16 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on okasha_server?
The map on okasha_server is procedural, produced by the game.
Which settings and rules apply on okasha_server?
No gather rate appears in the name of okasha_server. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Under Community in the server browser, it runs as a community server. The server has VAC on, Valve's anti-cheat.
Player counts
What is the current population on okasha_server?
A reading taken now finds okasha_server offline; the most recent activity was 9 days 3 hours ago.
How does okasha_server rank against other Rust servers?
Over the last seven days, okasha_server recorded enough player hours to reach #13,655 worldwide, placing it in the top 62% of all ranked servers.
Operator and location
How reliably does okasha_server stay online?
okasha_server is down at the moment; the last recorded contact was 9 days 3 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 29 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does okasha_server run from?
No region is published by okasha_server. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 188.0.114.67:28015.
What build of Rust does okasha_server use?
okasha_server is running Rust network protocol 2634 and build 167781 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on okasha_server?
The recent wipes averaged a busiest count of 1 players. 0 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. It fell under half by day 15 in the wipes where it didn't hold.
How often does okasha_server wipe, and on which days?
No next wipe can be predicted for okasha_server, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 11 days 3 hours.
Tags
What do the server tags on okasha_server mean?
The game's server browser reads the tags okasha_server publishes: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): Slots: 10; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does okasha_server appear?
You will find okasha_server on the following Rust Server Trends lists: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Connecting
How do you connect to okasha_server?
You can connect by pressing F1 in Rust and typing client.connect 188.0.114.67:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.