RUST METRICSFlight deck · live data
Data live Servers11,649 Players46,616 Populated3,134 Fresh wipes 3 h110 Scan5 min
‹ All servers188.234.213.232:28015
Offline Full Queue Fresh wipe Wipe due No query

Ural Battlefield (coming soon)

Offline 188.234.213.232:28015 checked 26d ago

solo moddedoxide
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#15,929top 70%
Last wipe33d 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, measured since 17 Sep. 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 Sep24 Sep28 Sep1 Oct5 Oct9 Oct

Top 70% of all ranked servers, and #205 of the solo servers (top 91%). 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.

usual gap5.7 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Sat 26 SepSun 20 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 26 Sep, 06:49 UTC33d ago 2 – running 0
Sun 20 Sep, 13:31 UTC38d ago 1 held half 5.7 days 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 Ural Battlefield (coming soon) when wipe day comes?

At their busiest, its recent wipes drew 2 players on average. 4 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

How often does Ural Battlefield (coming soon) wipe, and when?

To tell the rhythm of Ural Battlefield (coming soon), 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. The world it runs now was made 33 days 1 hours ago.

Tag meanings

How should you read the tags on Ural Battlefield (coming soon)?

Tags published by Ural Battlefield (coming soon), read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): The server holds 500 slots; ts1 (Group limit): Team cap: 1; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163493 (Build): The server runs game build 163493; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^i (Battlefield): Kits and high rates feed fast PvP here; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Ural Battlefield (coming soon)?

On Rust Metrics, Ural Battlefield (coming soon) sits in these lists: Modded Rust servers, checked live, Rust battlefield servers: check the readings and Solo-only Rust servers. Reading: server list filters. It comes up under Type: Modded; Server tag: Battlefield ^i, Modded ^z and Oxide ^o; Group limit: Solo.

Player count

Where does Ural Battlefield (coming soon) sit in the rankings?

Ranking for Ural Battlefield (coming soon): #15,929 on seven-day player hours, top 70% of all ranked servers. The solo group places it at #205.

What is the population on Ural Battlefield (coming soon)?

Reading for Ural Battlefield (coming soon): offline at this moment; last seen 26 days 13 hours ago.

Server

Where does Ural Battlefield (coming soon) sit?

No region comes from Ural Battlefield (coming soon). Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 188.234.213.232:28015.

What Rust version is Ural Battlefield (coming soon) on?

Rust network protocol 2633 and build 163493 on Linux is the build Ural Battlefield (coming soon) runs. Check: protocol. To join, your game must match; Steam handles the update.

Is Ural Battlefield (coming soon) up, and how often does it stay up?

Ural Battlefield (coming soon) reports offline. The last reading came 26 days 13 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What rules does Ural Battlefield (coming soon) enforce, and what are its settings?

Check: gather rate. The name Ural Battlefield (coming soon) does not state one. Check: teams. Solo only — no teams. Mode check gives battlefield; kits and high rates drive fast PvP. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is Ural Battlefield (coming soon) on?

Size 4,500: a procedural map on Ural Battlefield (coming soon), made by the game.

Connection

How can you get onto Ural Battlefield (coming soon)?

Press F1 in Rust and enter client.connect 188.234.213.232: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?,v2633,^i,gmrust,cs163493,ts1,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players The server holds 500 slots.
ts1
Group limit Team cap: 1.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163493
Build The server runs game build 163493.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Gameplay

^i
Battlefield Kits and high rates feed fast PvP here.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock game.

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.