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 20 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 24% 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.
BeanTownPlus's wipe history is too thin on record to show a rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. The world you are playing on was built 8 days 22 hours.
These are the Rust Live Stats lists BeanTownPlus fits: Live Rust community servers, Rust PvE servers, live now and Vanilla Rust servers, live. These filters on the server list bring it up: Type: Vanilla, Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: Vanilla ^v and PvE ^p; Group limit: 5 or more; Last wipe: In the last 2 weeks.
The server browser reads gmrust (Game mode): Survival here follows standard Rust; mp40 (Max players): Slots: 40; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): Region code: none set; ^v (Vanilla): It runs the game as Facepunch ships it: rates, kits and rules unchanged; ^p (PvE): No player fights another — the danger comes from the world, which BeanTownPlus publishes. Also in the tags: players on now, the queue, and when the world was made. You will find them at the top of this page.
BeanTownPlus is carrying 0 players at the moment, with 40 slots in total. Averaged across seven days, 0 players; the peak was 2. The busiest hour in the past 48 was 03:00 UTC, averaging 0 players.
On player hours for the past seven days, BeanTownPlus sits at #5,299, inside the top 24% of ranked servers.
No gather rate appears in the name BeanTownPlus. Eight players per group, which is the game's default. pve applies here, no fighting other players. The server browser lists it under Community. Its self-description is vanilla: it runs the game as Facepunch ships it: rates, kits and rules unchanged. Anti-cheat: VAC from Valve is enabled.
A procedural map of 3,000 with seed 1, generated by the game, runs on BeanTownPlus. Size and seed repeat the same map, so RustMaps can show it from this page.
Nothing on BeanTownPlus states a region. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. You can reach it at 173.240.145.198:9000.
Server fps averaged 224 over the last 48 hours, with a low of 189. Buildings, deployables and everything else in the world added up to a maximum of 49,076 entities. Up to 2,678 MB of memory was used. Lag, as players feel it, comes from low fps and a rising entity count.
The setup on BeanTownPlus is Rust network protocol 2635 and build 168909 with Linux. To join, your game must use the same protocol; Steam handles the update for you.
BeanTownPlus is up and running at this moment. Based on the uptime it reports, the last restart was about 6 days 14 hours ago. It was online for 167 of 168 hours in the last 7 full days, or 99% of the time. The first sighting by Rust Live Stats was on 20 October 2026.
Enter client.connect 173.240.145.198:9000 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.