RUST METRICSFlight deck · live data
Data live Servers11,880 Players96,316 Populated4,103 Fresh wipes 3 h158 Scan5 min
‹ All servers85.86.25.197:28015
Offline Full Queue Fresh wipe Wipe due No query

SADIKO SERVER

Offline 85.86.25.197:28015 checked 2d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

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#13,990top 63%
Last wipe25d 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
15k10k15k20k2 Oct6 Oct11 Oct15 Oct20 Oct27 Oct

Top 63% 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.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 10:58 UTC25d ago 1 – 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

What happens on SADIKO SERVER when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. 2 hours after the wipe, the crowd peaked on the latest wipe.

How often does SADIKO SERVER wipe, and when?

To tell the rhythm of SADIKO SERVER, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 25 days 7 hours ago the current world was made.

Lists and filters

How should you read the tags on SADIKO SERVER?

These are the tags SADIKO SERVER publishes, and the server browser reads them: gmvanilla (Game mode): Survival on vanilla settings; mp1 (Max players): Slots: 1; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does SADIKO SERVER appear in Rust Metrics lists and filters?

These Rust Metrics lists carry SADIKO SERVER: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Where does SADIKO SERVER sit in the rankings?

Player hours over seven days put SADIKO SERVER at #13,990, in the top 63% of all ranked servers.

How full does SADIKO SERVER get?

Reading for SADIKO SERVER: offline at this moment; last seen 2 days 22 hours ago. Check: players over seven days. Average 1, peak 1.

Server details

Where does SADIKO SERVER sit?

No region comes from SADIKO SERVER. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 85.86.25.197:28015.

What Rust version is SADIKO SERVER on?

Reading: SADIKO SERVER, Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.

Is SADIKO SERVER up, and how often does it stay up?

SADIKO SERVER reports offline. The last reading came 2 days 22 hours ago. Uptime for the last 7 full days: 1 of 168 hours, or 1%. Check: first contact. Rust Metrics logged it on 2 October 2026.

Rules and settings

What settings and rules apply on SADIKO SERVER?

No gather rate appears in the name: SADIKO SERVER. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

Which map is live on SADIKO SERVER?

Check: map. Procedural, generated by the game, on SADIKO SERVER.

Connection

How do you connect to SADIKO SERVER?

Check: join. Open Rust, press F1, then enter client.connect 85.86.25.197:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2635,gmvanilla,cs168909,ts8

Game

gmvanilla
Game mode Survival on vanilla settings.
mp1
Max players Slots: 1.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

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.