RUST METRICSFlight deck · live data
Data live Servers11,684 Players38,205 Populated2,919 Fresh wipes 3 h95 Scan5 min
‹ All servers95.70.135.29:28015
Offline Full Queue Fresh wipe Wipe due No query

Serkan Solo

Offline 95.70.135.29:28015 checked 18d ago

COM 1 · connect

Server instruments

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

Players now

100% 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#13,635top 62%
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 Oct11 Oct12 Oct14 Oct15 Oct17 Oct

Top 62% 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, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 23:37 UTC18d ago 1 – running 1

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 Serkan Solo when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours.

When does Serkan Solo wipe?

The rhythm of Serkan Solo's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 18 days 2 hours ago.

Lists and filters

How should you read the tags on Serkan Solo?

These are the tags Serkan Solo publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167398 (Build): Game build reading: 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. 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 Serkan Solo?

Rust Metrics lists featuring Serkan Solo: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

Where does Serkan Solo sit in the rankings?

Player hours over seven days put Serkan Solo at #13,635, in the top 62% of all ranked servers.

What player count does Serkan Solo carry?

Reading for Serkan Solo: offline at this moment; last seen 18 days 2 hours ago.

Server details

Where does Serkan Solo sit?

Reading: location. Serkan Solo gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 95.70.135.29:28015.

What Rust version is Serkan Solo on?

Version check: Rust network protocol 2634 and build 167398 on Windows, run by Serkan Solo. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on Serkan Solo, and is it online?

Serkan Solo reports offline. The last reading came 18 days 2 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.

Settings and map

What rules does Serkan Solo enforce, and what are its settings?

Reading the name gives no gather rate for Serkan Solo. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is Serkan Solo on?

Check: map. Procedural, generated by the game, on Serkan Solo.

Connection

What do you do to join Serkan Solo?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players Slots: 1.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167398
Build Game build reading: 167398.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.