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 11 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 69% 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.
The record holds too few of GOM Hub's wipes to reveal its rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. This world dates from 17 days 6 hours.
The Rust Live Stats lists that include GOM Hub are 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.
The server browser reads gmrust (Game mode): The game mode is standard Rust survival; mp40 (Max players): The slot count is 40; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2634 (Protocol): Join only if your game is on protocol 2634; cs167398 (Build): This server runs game build 167398; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): Region code: none set; ^z (Modded): Modded: plugins or changed settings alter the game; ^y (Carbon): The plugins run through Carbon; ^x (Unknown flag): Facepunch does not document what this flag means, which GOM Hub 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.
0 of GOM Hub's 40 slots are filled right now. Averaged over seven days: 0 players.
On player hours for the past seven days, GOM Hub sits at #15,399, inside the top 69% of ranked servers.
Nothing in the name of GOM Hub states a gather rate. Eight players per group, which is the game's default. survival is the mode, with 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 5,000 with seed 121212, generated by the game, runs on GOM Hub. Same size, same seed, same map: RustMaps has it, reachable from this page. For the map name it lists Custom Map.
There is no region from GOM Hub. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. Connect to 64.40.8.189:33015.
The average server fps was 30 over the last 48 hours; the lowest was 30. Entity count reached 106,623: buildings, deployables and the rest of the world. Up to 16,401 MB of memory was used. Lag, as players feel it, comes from low fps and a rising entity count.
The setup on GOM Hub is Rust network protocol 2634 and build 167398 with Linux. To join, your game must use the same protocol; Steam handles the update for you.
GOM Hub is up and running at this moment. About 17 days 4 hours ago is when it last restarted, according to its uptime. It was online for 168 of 168 hours in the last 7 full days, or 100% of the time. Rust Live Stats has tracked it since 11 October 2026.
Enter client.connect 64.40.8.189:33015 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.