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 22% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 7h. The 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.
Estimating bulaaa tatata's next wipe relies on the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe and one that hits every Rust server. This world dates from 4 days 6 hours. Its tags give wipes as monthly.
The Rust Live Stats lists that include bulaaa tatata are Modded Rust servers live now. You will find it on the server list under Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last week.
The server browser reads gmrust (Game mode): Standard survival, in the Rust style; mp10 (Max players): The slot count is 10; ts8 (Group limit): Team cap: 8, which is the game default; v2635 (Protocol): You need protocol 2635 on your game to get in; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): The server sets no region code; ^m (Monthly): It wipes with Facepunch's force wipe, once each month; ^o (Oxide): It runs the plugin framework Oxide (uMod); ^z (Modded): Plugins or settings changes put this under Modded, which bulaaa tatata publishes. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
0 of bulaaa tatata's 10 slots are filled right now. Averaged across seven days, 0 players; the peak was 3. Peak hour over 48 hours: 03:00 UTC, at 2 players on average.
On player hours for the past seven days, bulaaa tatata sits at #4,971, inside the top 22% of ranked servers.
The name bulaaa tatata carries no gather rate. No custom limit is set, so groups hold the default 8 players. survival applies here, the standard game: gather, build, raid. Fighting and raiding between players are allowed. Modded is its browser category, where plugins or settings change the game. Plugins run here: Oxide. Anti-cheat: VAC from Valve is enabled.
A procedural map of 4,500 with seed 482913, generated by the game, runs on bulaaa tatata. RustMaps shows it from this page, since equal size and seed give an equal map.
No region is published by bulaaa tatata. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. You can reach it at 15.204.44.89:60416.
Server fps averaged 107 over the last 48 hours, with a low of 56. Buildings, deployables and everything else in the world added up to a maximum of 128,726 entities. The highest memory usage was 7,321 MB. Lag, as players feel it, comes from low fps and a rising entity count.
bulaaa tatata operates on Linux with Rust network protocol 2635 and build 168909. Steam updates it for you, but your game needs the same protocol to join.
bulaaa tatata is up and running at this moment. About 29 hours ago is when it last restarted, according to its uptime. 71 of 72 hours were online in the last 3 full days, giving 99% uptime. The first sighting by Rust Live Stats was on 25 October 2026.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 15.204.44.89:60416.