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 24 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 68% 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.
BigBert's 2X [Solo/Duo/Trio] (Midwest)'s wipe history is too thin on record to show a rhythm. Every server in Rust, this one among them, wipes at the monthly force wipe; Thursday 5 November at 19:00 UTC is the next. The world you are playing on was built 26 days 12 hours.
On Rust Live Stats, BigBert's 2X [Solo/Duo/Trio] (Midwest) is listed under 2x Rust servers live now and Modded Rust servers live now. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: 2x.
gmrust (Game mode): Survival here follows standard Rust; mp50 (Max players): The slot count is 50; ts8 (Group limit): 8 per team at most, the game's default setting; v2635 (Protocol): You need protocol 2635 on your game to get in; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): No region code is set here; ^z (Modded): The game changes here through plugins or settings, so it is Modded; ^y (Carbon): It uses the plugin framework Carbon: that is the tag list BigBert's 2X [Solo/Duo/Trio] (Midwest) publishes for the game's server browser. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
0 of BigBert's 2X [Solo/Duo/Trio] (Midwest)'s 50 slots are filled right now. Averaged across seven days, 0 players; the peak was 1.
Ranked by seven-day player hours, BigBert's 2X [Solo/Duo/Trio] (Midwest) is #15,194, placing it in the top 68% of ranked servers.
The name says it: gathering runs at 2x on BigBert's 2X [Solo/Duo/Trio] (Midwest). Eight players per group, which is the game's default. survival is the mode, with the standard game: gather, build, raid. Fighting and raiding between players are allowed. Plugins or settings change the game, and the browser lists it as Modded. Carbon plugins are in use. Anti-cheat: VAC from Valve is enabled.
BigBert's 2X [Solo/Duo/Trio] (Midwest) runs a game-generated procedural map: size 4,500, seed 1337. Same size, same seed, same map: RustMaps has it, reachable from this page.
Nothing on BigBert's 2X [Solo/Duo/Trio] (Midwest) states a region. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. Connect to 216.82.5.222:28015.
It never went below 131 server fps in the last 48 hours, averaging 200. Buildings, deployables and everything else in the world added up to a maximum of 121,200 entities. Memory use peaked at 4,744 MB. Lag, as players feel it, comes from low fps and a rising entity count.
Rust network protocol 2635 and build 168909 on Linux is what BigBert's 2X [Solo/Duo/Trio] (Midwest) runs. Steam updates it for you, but your game needs the same protocol to join.
BigBert's 2X [Solo/Duo/Trio] (Midwest) is up and running at this moment. The uptime it reports puts the last restart at about 4 days 23 hours ago. It was online for 95 of 96 hours in the last 4 full days, or 99% of the time. On 24 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 216.82.5.222:28015.