RUST METRICSFlight deck · live data
Data live Servers11,706 Players60,014 Populated3,275 Fresh wipes 3 h114 Scan5 min
‹ All servers188.146.23.32:28015
Online Full Queue Fresh wipe Wipe due No query

Obztraining

Online 188.146.23.32:28015 checked 46m 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 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 average0peak 1
Rank#7,910top 35%
Last wipe4d agono schedule published
Next wipe–too few wipes seen yet
Memory–48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75117:0018:0019:0021:0022:0023:00

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
12.5k5k7.5k10k16 Oct19 Oct22 Oct24 Oct27 Oct30 Oct

Top 35% 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
Sun 25 Oct, 17:26 UTC4d 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

Wipe timing

What happens on Obztraining when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in.

How often does Obztraining wipe, and when?

Its rhythm cannot be told from the wipes of Obztraining on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 4 days 7 hours ago.

Lists and filters

How should you read the tags on Obztraining?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): 500 slots in total; 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 from Obztraining. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Obztraining appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Obztraining: 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; Last wipe: In the last week.

Occupancy

Where does Obztraining sit in the rankings?

Ranking for Obztraining: #7,910 on seven-day player hours, top 35% of all ranked servers.

How full does Obztraining get?

Current headcount on Obztraining: 0 players, 500 slots available. Seven-day check: 0 players on average. Peak reading: 1. Average at the busiest hour was 1 players, at 18:00 UTC over the last 48 hours.

Server

Where does Obztraining sit?

No region tag on Obztraining. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 188.146.23.32:28015.

What Rust version is Obztraining on?

Rust network protocol 2635 and build 168909 on Windows is the build Obztraining runs. Check: protocol. To join, your game must match; Steam handles the update.

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

Obztraining reports online. Status: normal. Uptime for the last 7 full days: 35 of 168 hours, or 21%. Check: first contact. Rust Metrics logged it on 16 October 2026.

Settings and map

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

Reading the name gives no gather rate for Obztraining. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is Obztraining on?

The game generates a procedural map for Obztraining.

How to join

What do you do to join Obztraining?

Press F1 in Rust and enter client.connect 188.146.23.32:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players 500 slots in total.
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.