Working its way up from the back of the class: #16,967 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
32/ 100
F
Lost ground: down 6,079 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to F.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
RankRank in region
Top 72% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
·······
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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 peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 14 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 26 Sep, 09:44 UTC31d ago
1
–
running
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is Baltic Rivals LOCAL test based in?
No region is published for Baltic Rivals LOCAL test. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 78.84.160.95:28115.
Is Baltic Rivals LOCAL test up, and how steady is its uptime?
You cannot join now: Baltic Rivals LOCAL test is offline, last seen 30 days 7 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 18 September 2026.
Which Rust version is Baltic Rivals LOCAL test running?
You will find Baltic Rivals LOCAL test on Rust network protocol 2633 and build 164530, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does Baltic Rivals LOCAL test reset?
The record holds too few of Baltic Rivals LOCAL test's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 31 days 8 hours.
What should you expect from wipe day on Baltic Rivals LOCAL test?
Across its recent wipes, the busiest moments averaged 1 players. The crowd on the latest wipe was largest 14 hours after it began.
Population
Where does Baltic Rivals LOCAL test sit among Rust servers?
In the top 72% of all ranked servers, Baltic Rivals LOCAL test sits at #16,967 for player hours over the last seven days.
What does the population on Baltic Rivals LOCAL test look like?
It has been 30 days 7 hours since Baltic Rivals LOCAL test was last seen, and it is offline right now.
Tags and filters
What do Baltic Rivals LOCAL test's tags stand for?
You'll see Baltic Rivals LOCAL test tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp2 (Max players): 2 slots are available; ts100 (Group limit): Teams cap out at 100; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs164530 (Build): This runs on build 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature Baltic Rivals LOCAL test?
Rust Server Score lists that include Baltic Rivals LOCAL test: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Map and rules
Which rules does Baltic Rivals LOCAL test enforce, and what are its settings?
Nothing in the name of Baltic Rivals LOCAL test states a gather rate. A group here can reach 100 players. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Connecting
How should you connect to Baltic Rivals LOCAL test?
Enter client.connect 78.84.160.95:28115 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2633,gmrust,cs164530,ts100,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp2
Max players2 slots are available.
ts100
Group limitTeams cap out at 100.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs164530
BuildThis runs on build 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonPlugin framework: Carbon.
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.
A term to build on. Even marks across the subjects, from F to F.