Station XX-6370 · no signal
RusBalt
Offline 78.28.86.84:28015 checked 3d ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak 2
- Rank
- #6,370
- top 29%
- Last wipe
- 10d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 29% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 17 daysbetween real wipes
- wipe-day peak
- 2players, last three wipes
- crowd held
- 0%else halves by day 3
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sun 18 Oct, 19:33 UTC10d ago | M0.0▲rising | 1 | – | running | 0 | |
| Thu 1 Oct, 18:33 UTC FW27d ago | M0.3▲rising | 2 | halved by day 3 | 17 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on RusBalt?
Generated by the game, the map on RusBalt is procedural, size 4,000 with seed 2124223604. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on RusBalt?
You will find no gather rate in the name of RusBalt. The group limit is 8 players, the game's default. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Carbon. VAC, Valve's anti-cheat, is switched on.
Live population
What is the current population on RusBalt?
RusBalt is not responding at this moment and is offline, last seen 3 days 13 hours ago. Averaged across the last seven days the population was 0 players, reaching a peak of 2.
How does RusBalt rank against other Rust servers?
Over the last seven days, RusBalt recorded enough player hours to reach #6,370 worldwide, placing it in the top 29% of all ranked servers.
Server details
How reliably does RusBalt stay online?
As recorded now, RusBalt is not reachable, the last contact having been 3 days 13 hours ago. It was up 54% of the time across the last 7 full days: 91 of 168 hours. 13 September 2026 is when Rust Server Trends first recorded it.
Which region does RusBalt run from?
A region is not published by RusBalt. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 78.28.86.84:28015 is the address it uses.
Which Rust version is RusBalt running?
On Windows, RusBalt runs Rust network protocol 2635 and build 168909. 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 RusBalt?
2 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 0 hours after the wipe. Half that peak was held until the next wipe in 0% of its recent wipes. By day 3 it fell below half in the wipes where it didn't hold.
On what timetable does RusBalt run its wipes?
On record so far are too few of RusBalt's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 10 days 12 hours is how long the current world has been running.
Lists and tags
What do the server tags on RusBalt mean?
Tags published by RusBalt and read by the game's server browser include gmvanilla (Game mode): You'll find vanilla survival here; mp50 (Max players): The server has 50 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $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): Carbon is the plugin framework running here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does RusBalt appear?
You will find RusBalt on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Join the server
What steps get you onto RusBalt?
To join, enter client.connect 78.28.86.84:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
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.