Rust Server TrendsSeismic network · station log
Recording Stations11,718 Players59,183 Active3,355 Wipes · 3 h176 48 h

Station XX-15128 · no signal

Rust Battlefield PREVIEW (closed test)

Offline 80.232.242.125:28025 checked 12d ago

Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,128
top 70%
Last wipe
12d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-15128 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 10 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

Rank

daily · 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.

Expected events

Wipe schedule

no rhythm it keeps

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

usual gap
1 daysbetween real wipes
on rhythm
100%of its recent wipes
wipe-day peak
1players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 16 Oct, 15:52 UTC12d ago M0.0steady 1 – running 1
Thu 15 Oct, 16:14 UTC13d ago M0.0rising 1 – 1 days 0
Wed 14 Oct, 16:32 UTC14d ago M0.0steady 1 – 1 days 1
Tue 13 Oct, 17:50 UTC15d ago M0.0rising 1 – 0.9 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
【极光】100000000倍|枪战|礼包|建造|新手入门 EA · groups of 16+ · 19 on average
3/ 200
3/ 200
ADRENALIN Rust RU 2X [ лутай СКИНЫ ] Loot+ EU · groups of 60+ · 2x · weekly · 4 on average
4/ 100
RUSTBURG.GG #1〔X5/X10|NO LIMIT|LOOT+|FPS+|KITS|TP〕27.10 EU · groups of 50+ · 5x · weekly · 185 on average
250/ 260
Scrapland x10000000 |BATTLEFIELD|KITS|TP|CLANS|SKINBOX|PVP| NA · groups of 35+ · 1e+07x · weekly · 139 on average
48/ 600
CoolingLine #1 - x1000 | NOLIMIT | FAST | LOOT+ | FPS |CLANS EU · groups of 100+ · 1000x · weekly · 61 on average
112/ 130
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which settings and rules apply on Rust Battlefield PREVIEW (closed test)?

The name of Rust Battlefield PREVIEW (closed test) gives no gather rate. At the game's default, groups can have up to 8 players. It plays in battlefield mode, kits and high rates for fast PvP. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is switched on.

Player counts

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

No players are recorded on Rust Battlefield PREVIEW (closed test) at this moment; it is offline, and the last sighting was 12 days 13 hours ago.

How does Rust Battlefield PREVIEW (closed test) rank against other Rust servers?

On player hours for the past week, Rust Battlefield PREVIEW (closed test) sits at #15,128, which puts it inside the top 70% of every ranked server.

Operator and location

How reliably does Rust Battlefield PREVIEW (closed test) stay online?

As recorded now, Rust Battlefield PREVIEW (closed test) is not reachable, the last contact having been 12 days 13 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 10 October 2026 is when Rust Server Trends first recorded it.

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

A region is not published by Rust Battlefield PREVIEW (closed test). Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 80.232.242.125:28025 is the address it uses.

What build of Rust does Rust Battlefield PREVIEW (closed test) use?

On Linux, Rust Battlefield PREVIEW (closed test) runs Rust network protocol 2634 and build 167781. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on Rust Battlefield PREVIEW (closed test)?

On average, the busiest point of its recent wipes drew 1 players. The peak on the most recent wipe came 1 hours after the wipe.

On what timetable does Rust Battlefield PREVIEW (closed test) run its wipes?

No next wipe can be predicted for Rust Battlefield PREVIEW (closed test), which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 12 days 16 hours.

Server tags

What do the server tags on Rust Battlefield PREVIEW (closed test) mean?

These are the tags Rust Battlefield PREVIEW (closed test) publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): The server has 10 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): It runs game build 167781; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^i (Battlefield): Kits and high rates drive fast PvP. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does Rust Battlefield PREVIEW (closed test) appear?

The Rust Server Trends lists that take in Rust Battlefield PREVIEW (closed test) are: Rust battlefield servers. You will find it under these filters on the server list: 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 to join

How do you connect to Rust Battlefield PREVIEW (closed test)?

You can connect by pressing F1 in Rust and typing client.connect 80.232.242.125:28025 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,^i,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players The server has 10 slots.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs167781
Build It runs game build 167781.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code The server has no region code.

Gameplay

^i
Battlefield Kits and high rates drive fast PvP.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.