RUST METRICSFlight deck · live data
Data live Servers11,668 Players48,663 Populated3,138 Fresh wipes 3 h118 Scan5 min
‹ All servers78.179.225.65:28015
Offline Full Queue Fresh wipe Wipe due No query

ozkan1692620:31

Offline 78.179.225.65:28015 checked 42d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /500

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#13,889no region published
Last wipe42d 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
15k10k15k20k20 Sep21 Sep22 Sep23 Sep
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
Wed 16 Sep, 17:42 UTC42d 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 should you expect from wipe day on ozkan1692620:31?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does ozkan1692620:31 follow?

Its rhythm cannot be told from the wipes of ozkan1692620:31 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. 42 days 15 hours ago the current world was made.

Tag meanings

Which tags does ozkan1692620:31 carry, and what do they mean?

These are the tags ozkan1692620:31 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): The server holds 500 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): Game build reading: 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does ozkan1692620:31 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry ozkan1692620:31: 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.

Player count

Where does ozkan1692620:31 sit in the rankings?

Player hours over seven days put ozkan1692620:31 at #13,889, in the top – of all ranked servers.

How full does ozkan1692620:31 get?

Reading for ozkan1692620:31: offline at this moment; last seen 42 days 13 hours ago.

Server details

Which location does ozkan1692620:31 run from?

No region comes from ozkan1692620:31. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 78.179.225.65:28015.

What Rust version is ozkan1692620:31 on?

Rust network protocol 2633 and build 163794 on Windows is the build ozkan1692620:31 runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is ozkan1692620:31, and is it online now?

ozkan1692620:31 reports offline. The last reading came 42 days 13 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 16 September 2026.

Rules and settings

How is ozkan1692620:31 configured, and what rules are in force?

Check: gather rate. The name ozkan1692620:31 does not state one. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Which map is live on ozkan1692620:31?

The game generates a procedural map for ozkan1692620:31.

Join

How can you get onto ozkan1692620:31?

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

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players The server holds 500 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163794
Build Game build reading: 163794.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.