LiveLive coverage · Rust server
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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 25 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 45% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
This server has not put up a new map since the desk started watching it.
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.
RusBalt's wipe history is too thin on record to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. 9 days 11 hours have passed since this world was generated.
The Rust Live Stats lists that include RusBalt are Modded Rust servers live now. You will find it on the server list under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
The server browser reads gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): The slot count is 50; ts8 (Group limit): 8 per team at most, the game's default setting; v2635 (Protocol): The server runs protocol 2635, so match that version to join; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): No region code is set here; ^z (Modded): Plugins or settings changes put this under Modded; ^y (Carbon): Plugin framework: Carbon, which RusBalt publishes. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
RusBalt is carrying 0 players at the moment, with 50 slots in total. Averaged across seven days, 0 players; the peak was 1. The busiest hour in the past 48 was 15:00 UTC, averaging 1 players.
On player hours for the past seven days, RusBalt sits at #9,947, inside the top 45% of ranked servers.
The name RusBalt carries no gather rate. Eight players per group, which is the game's default. survival applies here, the standard game: gather, build, raid. Raiding and player combat are both permitted. Modded is its browser category, where plugins or settings change the game. The plugin load is Carbon. Anti-cheat: VAC from Valve is enabled.
A procedural map of 4,000 with seed 2124223604, generated by the game, runs on RusBalt. RustMaps shows it from this page, since equal size and seed give an equal map.
Nothing on RusBalt states a region. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. You can reach it at 78.28.93.30:28015.
The average server fps was 139 over the last 48 hours; the lowest was 64. It supported up to 92,610 entities, covering buildings, deployables and all other objects. Up to 3,221 MB of memory was used. A climbing entity count and low fps are felt as lag by players.
The setup on RusBalt is Rust network protocol 2635 and build 168909 with Windows. Steam updates it for you, but your game needs the same protocol to join.
RusBalt is up and running at this moment. The uptime it reports puts the last restart at about 1 hours ago. It was online for 48 of 48 hours in the last 2 full days, or 100% of the time. On 25 October 2026, Rust Live Stats saw it for the first time.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 78.28.93.30:28015.