Online 64.40.8.189:33015 checked 15m ago
GOM Hub
Connect
srv = rust.server("64.40.8.189:33016")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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.
display(srv.map, srv.info())
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 155 on average | 155/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 127 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 182/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 95/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 5/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 40/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does GOM Hub rank?
Rank #15,396 on seven-day player hours for GOM Hub, within the top 69% of all ranked servers.
How full does GOM Hub run?
Current row: 0 players on GOM Hub, against 40 slots. Over the last seven days it averaged 0 players.
About the server
How well does GOM Hub perform?
The 48-hour average is 30 server fps, with a low of 30. The entity count peaked at 106,623, covering buildings, deployables and the rest of the world. The memory field tops out at 16,401 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is GOM Hub on?
Version Rust network protocol 2634 and build 167398 on Linux is reported by GOM Hub. Joining needs the same protocol on your game; Steam handles the update.
How reliable is GOM Hub, and is it up?
The current sample puts GOM Hub online. A restart about 17 days 3 hours ago is what its reported uptime implies. Uptime of 100% across the last 7 full days: 168 hours of 168. Rust Data logged it first on 11 October 2026.
In which location is GOM Hub hosted?
No region is published by GOM Hub. Rust Data does not look up where the machine stands; it shows where a server says it is. 64.40.8.189:33015 is its address.
Map and rules
Which rules apply on GOM Hub, and what settings?
The name GOM Hub carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Carbon. VAC is running: Valve's anti-cheat is on.
What is the map on GOM Hub?
GOM Hub runs a procedural map of size 5,000 with seed 121212, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Custom Map is what the map name field says.
Wipe data
When does GOM Hub wipe, and how often?
A rhythm cannot be read from the wipes of GOM Hub on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 17 days 5 hours ago.
Tags and filters
Which lists on Rust Data hold GOM Hub, and which filters?
These Rust Data lists include GOM Hub: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on GOM Hub?
The game's server browser reads these tags from GOM Hub: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): Slot count: 40; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167398 (Build): Build number: 167398; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Runs on Carbon for plugins; ^x (Unknown flag): Facepunch does not document this flag. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into GOM Hub?
Enter client.connect 64.40.8.189:33015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.