Rust Data

rustdata.spaceservers80.232.242.125:28027.ipynb

Run all rust-data · live

‹ All servers

Offline 80.232.242.125:28025 checked 12d ago

Rust Battlefield PREVIEW (closed test)

Connect

srv = rust.server("80.232.242.125:28027")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,128 # top 70%
last wipe 12d ago # no schedule published
next wipe – # no rhythm it keeps

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. 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
15k10k15k20k10 Oct13 Oct15 Oct18 Oct20 Oct23 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Fri 16 OctThu 15 OctWed 14 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 16 Oct, 15:52 UTC12d ago 1 NaN running 1
1 Thu 15 Oct, 16:14 UTC13d ago 1 NaN 1 days 0
2 Wed 14 Oct, 16:32 UTC14d ago 1 NaN 1 days 1
3 Tue 13 Oct, 17:50 UTC15d ago 1 NaN 0.9 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

Custom map, no picture published
map
Custom Map
size
–
seed
–

Server

srv.info()
address
80.232.242.125:28025
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
16 Oct 2026, 18:45 UTC
hostname
–
first seen
10 Oct 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 average34/200
1【星云】10000倍|爆枪|秒造|全解|礼包|新手入门EA · groups of 16+ · 15 on average21/200
2ADRENALIN Rust RU 2X [ лутай СКИНЫ ] Loot+EU · groups of 60+ · 2x · weekly · 4 on average2/100
3RUSTBURG.GG #1〔X5/X10|NO LIMIT|LOOT+|FPS+|KITS|TP〕27.10EU · groups of 50+ · 5x · weekly · 182 on average138/165
4Scrapland x10000000 |BATTLEFIELD|KITS|TP|CLANS|SKINBOX|PVP|NA · groups of 35+ · 1e+07x · weekly · 137 on average151/200
5CoolingLine #1 - x1000 | NOLIMIT | FAST | LOOT+ | FPS |CLANSEU · groups of 100+ · 1000x · weekly · 60 on average77/105

Quick answers

From the figures on this page.

Population

What position does Rust Battlefield PREVIEW (closed test) take in the server rankings?

Over the last seven days Rust Battlefield PREVIEW (closed test) sits at #15,128 on player hours, in the top 70% of ranked servers.

What population does Rust Battlefield PREVIEW (closed test) carry?

The current row shows Rust Battlefield PREVIEW (closed test) offline; the last response was 12 days ago.

Server data

What is the Rust version on Rust Battlefield PREVIEW (closed test)?

The build is Rust network protocol 2634 and build 167781 on Linux, run by Rust Battlefield PREVIEW (closed test). Steam updates your game for you, but the protocol must match to join.

Is Rust Battlefield PREVIEW (closed test) up, and what does its uptime show?

Rust Battlefield PREVIEW (closed test) is offline at this refresh; the last response came 12 days ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 10 October 2026.

Which location does Rust Battlefield PREVIEW (closed test) run from?

No region is published by Rust Battlefield PREVIEW (closed test). Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 80.232.242.125:28025.

Settings and map

Which settings and rules does Rust Battlefield PREVIEW (closed test) run?

You will not find a gather rate in the string Rust Battlefield PREVIEW (closed test). The group limit sits at the default of 8 players. Game mode battlefield, with this note: fast PvP, kits supplied, rates high. The server browser lists it under Community. Anti-cheat status: VAC on.

Wipes and dates

On what schedule does Rust Battlefield PREVIEW (closed test) wipe?

Rust Battlefield PREVIEW (closed test) wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 12 days 3 hours ago.

On Rust Battlefield PREVIEW (closed test), what happens on wipe day?

The average peak over recent wipes is 1 players. 1 hours after the latest wipe, the crowd reached its peak.

Lists and tags

Which lists on Rust Data hold Rust Battlefield PREVIEW (closed test), and which filters?

The Rust Data lists that Rust Battlefield PREVIEW (closed test) fits are: Rust battlefield servers. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Server tag: Battlefield ^i; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How should you read the server tags on Rust Battlefield PREVIEW (closed test)?

Read by the game's server browser, the tags Rust Battlefield PREVIEW (closed test) publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^i (Battlefield): Battlefield: quick PvP, kits included, rates raised. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Join steps

What is the way to join Rust Battlefield PREVIEW (closed test)?

In Rust, F1 opens the console: type client.connect 80.232.242.125:28025. 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 mp10,ptrak,$r?,v2634,^i,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players Slot count: 10.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167781
Build Recorded game build: 167781.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Gameplay

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

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 69,058 players 11,802 servers online