RUST METRICSFlight deck · live data
Data live Servers11,675 Players48,366 Populated3,000 Fresh wipes 3 h102 Scan5 min
‹ All servers103.206.38.221:28015
Offline Full Queue Fresh wipe Wipe due No query

okasha_server

Offline 103.206.38.221:28015 checked 4d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average1peak 1
Rank#11,950top 54%
Last wipe13d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k25 Oct26 Oct27 Oct28 Oct29 Oct30 Oct

Top 54% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 18:40 UTC13d ago – – running 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

How often does okasha_server wipe, and when?

Its rhythm cannot be told from the wipes of okasha_server on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 13 days 7 hours ago.

Lists and filters

Which tags does okasha_server carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set from okasha_server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show okasha_server?

These Rust Metrics lists carry okasha_server: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player count

What position does okasha_server hold among Rust servers?

Ranking for okasha_server: #11,950 on seven-day player hours, top 54% of all ranked servers.

What player count does okasha_server carry?

okasha_server is not responding; status offline, last seen 4 days 5 hours ago. Seven-day check: 1 players on average. Peak reading: 1.

Operator and location

Where does okasha_server sit?

Reading: location. okasha_server gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 103.206.38.221:28015.

What Rust version is okasha_server on?

Reading: okasha_server, Rust network protocol 2635 and build 168909, Windows. To get in, your game needs the same protocol; Steam applies the update.

How reliable is okasha_server, and is it online now?

Check: connection. okasha_server is offline at this moment. Last contact was 4 days 5 hours ago. Uptime for the last 4 full days: 0 of 96 hours, or 0%. Reading: first seen 25 October 2026, recorded by Rust Metrics.

Rules and settings

How is okasha_server configured, and what rules are in force?

Reading the name gives no gather rate for okasha_server. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

Which map is live on okasha_server?

Check: map. Procedural, generated by the game, on okasha_server.

Join

How can you get onto okasha_server?

To join: start Rust, press F1 and type client.connect 103.206.38.221:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

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.