Rust Data

rustdata.spaceservers188.234.213.232:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 188.234.213.232:28015 checked 26d ago

Ural Battlefield (coming soon)

solo moddedoxide

Connect

srv = rust.server("188.234.213.232:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/500 # 0% full
7-day average 0 # peak –
rank #15,929 # top 70%
last wipe 33d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sat 26 Sep, 06:49 UTC33d ago 2 NaN running 0
1 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.

display(srv.map, srv.info())

Map

4500 · seed 0
No map picture published
map
Procedural Map
size
4500
seed
–

Server

srv.info()
address
188.234.213.232:28015
region
–
max players
500
group limit
solo
wipe schedule
–
last wipe
26 Sep 2026, 07:30 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0【极光】100000000倍|枪战|礼包|建造|新手入门EA · groups of 16+ · 19 on average0/200
1【星云】10000倍|爆枪|秒造|全解|礼包|新手入门EA · groups of 16+ · 15 on average3/200
2CHOYKA RUST №2[ONE GRID] [X2] SMALL MAP - FPS+Deep SeaEU · duo · 2x · weekly · 13 on average14/50
3CHOYKA RUST №1 [ONE GRID] [X2] SMALL MAP - FPS+Deep SeaEU · duo · 2x · weekly · 10 on average29/50
4#4 BroRust X5/X10|MAX 2|WIPE 27.10|TP|KIT|LOOT+|SHOPEU · duo · 5x · weekly · 18 on average22/100
5ADRENALIN Rust RU 2X [ лутай СКИНЫ ] Loot+EU · groups of 60+ · 2x · weekly · 5 on average5/100

Quick answers

From the figures on this page.

Population

How does Ural Battlefield (coming soon) compare in the rankings?

Over the last seven days Ural Battlefield (coming soon) sits at #15,929 on player hours, in the top 70% of ranked servers. Within the solo group, its rank is #205.

How full does Ural Battlefield (coming soon) run?

The current row shows Ural Battlefield (coming soon) offline; the last response was 26 days 17 hours ago.

Server facts

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

Version Rust network protocol 2633 and build 163493 on Linux is reported by Ural Battlefield (coming soon). Steam updates your game for you, but the protocol must match to join.

How reliable is Ural Battlefield (coming soon), and is it online now?

The latest sample has Ural Battlefield (coming soon) offline, with a last sighting 26 days 17 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.

Where does Ural Battlefield (coming soon) sit?

For Ural Battlefield (coming soon), no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 188.234.213.232:28015.

Map and rules

What rules and settings are recorded for Ural Battlefield (coming soon)?

No gather rate appears in the name: Ural Battlefield (coming soon). No teams here: solo only. Recorded as battlefield, kits and high rates for fast PvP. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.

Which map has Ural Battlefield (coming soon) loaded?

Generated by the game at size 4,500, the map on Ural Battlefield (coming soon) is procedural.

Wipe schedule

On what schedule does Ural Battlefield (coming soon) wipe?

A rhythm cannot be read from the wipes of Ural Battlefield (coming soon) on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 33 days 5 hours ago, and that is the one in play.

What is wipe day on Ural Battlefield (coming soon) like?

Across recent wipes the busiest point averaged 2 players. Peak population on the latest wipe came 4 hours in. Half the peak or more was held to the next wipe in 100% of recent wipes.

Tags, lists

Which lists on Rust Data hold Ural Battlefield (coming soon), and which filters?

On Rust Data, Ural Battlefield (coming soon) appears in these lists: Modded Rust servers, Rust battlefield servers and Solo Rust servers, group limit 1. Under these filters on the server list, it is listed: Type: Modded; Server tag: Battlefield ^i, Modded ^z and Oxide ^o; Group limit: Solo.

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

These tags are published by Ural Battlefield (coming soon) and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp500 (Max players): Slot count: 500; ts1 (Group limit): Team size tops out at 1; v2633 (Protocol): To join, your game must run protocol 2633; cs163493 (Build): The server runs build 163493; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^i (Battlefield): Battlefield: quick PvP, kits included, rates raised; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

How can I connect to Ural Battlefield (coming soon)?

In Rust, F1 opens the console: type client.connect 188.234.213.232:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp500,ptrak,$r?,v2633,^i,gmrust,cs163493,ts1,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp500
Max players Slot count: 500.
ts1
Group limit Team size tops out at 1.
v2633
Protocol To join, your game must run protocol 2633.
cs163493
Build The server runs build 163493.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Gameplay

^i
Battlefield Battlefield: quick PvP, kits included, rates raised.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits under Modded.

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.

Rust Data 68,594 players 11,792 servers online