Rust Server TrendsSeismic network · station log
Recording Stations11,875 Players94,751 Active3,875 Wipes · 3 h395 48 h

Station XX-16967 · no signal

Baltic Rivals LOCAL test

Offline 78.84.160.95:28115 checked 32d ago

moddedcarbon
Connect
Players now
0/ 2
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,967
top 72%
Last wipe
33d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-16967 · 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 2 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
15k10k15k20k20 Sep23 Sep26 Sep28 Sep1 Oct4 Oct

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

Expected events

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 peak
1players, 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, 14 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sat 26 Sep, 09:44 UTC33d ago M0.0rising 1 – running 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
ShockRust | Blue | NoLimit no group limit · 149 on average
173/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
120/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
187/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 94 on average
81/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 86 on average
349/ 350
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 86 on average
252/ 700
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which settings and rules apply on Baltic Rivals LOCAL test?

You will find no gather rate in the name of Baltic Rivals LOCAL test. The group limit is 100 players. survival is the game mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Carbon is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Live population

What is the current population on Baltic Rivals LOCAL test?

A reading taken now finds Baltic Rivals LOCAL test offline; the most recent activity was 32 days 5 hours ago.

How does Baltic Rivals LOCAL test rank against other Rust servers?

Over the last seven days, Baltic Rivals LOCAL test recorded enough player hours to reach #16,967 worldwide, placing it in the top 72% of all ranked servers.

Server facts

How reliably does Baltic Rivals LOCAL test stay online?

No contact with Baltic Rivals LOCAL test right now, and the last recorded contact was 32 days 5 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 18 September 2026 is when Rust Server Trends first recorded it.

Which region does Baltic Rivals LOCAL test run from?

No region is published by Baltic Rivals LOCAL test. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 78.84.160.95:28115 is the address it uses.

What build of Rust does Baltic Rivals LOCAL test use?

On Windows, Baltic Rivals LOCAL test runs Rust network protocol 2633 and build 164530. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

What does wipe day look like on Baltic Rivals LOCAL test?

The recent wipes averaged a busiest count of 1 players. 14 hours into the latest wipe, the crowd reached its peak.

How often does Baltic Rivals LOCAL test wipe, and on which days?

The rhythm of Baltic Rivals LOCAL test cannot yet be told: too few of its wipes are on record. 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 33 days 6 hours.

Lists and tags

What do the server tags on Baltic Rivals LOCAL test mean?

The game's server browser reads the tags Baltic Rivals LOCAL test publishes: gmrust (Game mode): Survival in standard Rust; mp2 (Max players): The server has 2 slots; ts100 (Group limit): The team limit is 100; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs164530 (Build): The game build is 164530; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. 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 Baltic Rivals LOCAL test appear?

These Rust Server Trends lists include Baltic Rivals LOCAL test: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Join the server

How do you connect to Baltic Rivals LOCAL test?

Enter client.connect 78.84.160.95:28115 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp2,ptrak,$r?,v2633,gmrust,cs164530,ts100,^z,^y

Game

gmrust
Game mode Survival in standard Rust.
mp2
Max players The server has 2 slots.
ts100
Group limit The team limit is 100.
v2633
Protocol To connect, your game must be on the same protocol, 2633.
cs164530
Build The game build is 164530.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

Mods and access

^z
Modded Plugins or settings alter the game, so it's listed under Modded.
^y
Carbon A plugin framework, Carbon, runs here.

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.