RUST METRICSFlight deck · live data
Data live Servers11,596 Players34,156 Populated2,853 Fresh wipes 3 h62 Scan5 min
‹ All servers185.232.233.93:28015
Offline Full Queue Fresh wipe Wipe due No query

RU_SERVER_STOK

Offline 185.232.233.93:28015 checked 18d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg
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 average0peak –
Rank#15,863top 72%
Last wipe18d 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
15k10k15k20k9 Oct10 Oct12 Oct13 Oct15 Oct16 Oct

Top 72% 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

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 9 Oct, 14:39 UTC18d 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 RU_SERVER_STOK when wipe day comes?

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

When does RU_SERVER_STOK wipe?

Its rhythm cannot be told from the wipes of RU_SERVER_STOK on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 18 days 10 hours ago the current world was made.

Tag meanings

How should you read the tags on RU_SERVER_STOK?

These are the tags RU_SERVER_STOK publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): Build 167398; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does RU_SERVER_STOK appear in Rust Metrics lists and filters?

On Rust Metrics, RU_SERVER_STOK sits in these lists: 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.

Occupancy

Where does RU_SERVER_STOK sit in the rankings?

Player hours over seven days put RU_SERVER_STOK at #15,863, in the top 72% of all ranked servers.

What is the population on RU_SERVER_STOK?

Reading for RU_SERVER_STOK: offline at this moment; last seen 18 days 9 hours ago.

Server details

Where does RU_SERVER_STOK sit?

No region tag on RU_SERVER_STOK. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 185.232.233.93:28015.

What Rust version is RU_SERVER_STOK on?

Reading: RU_SERVER_STOK, Rust network protocol 2634 and build 167398, Windows. To get in, your game needs the same protocol; Steam applies the update.

Is RU_SERVER_STOK up, and how often does it stay up?

Check: connection. RU_SERVER_STOK is offline at this moment. Last contact was 18 days 9 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 9 October 2026.

Rules and settings

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

No gather rate appears in the name: RU_SERVER_STOK. 8 players per group, the default value. Mode check gives survival; 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. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on RU_SERVER_STOK?

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

Connection

What do you do to join RU_SERVER_STOK?

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

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players 100 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build Build 167398.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.