Online 198.73.57.130:28025 checked 44m ago
gcb server
Connect
srv = rust.server("198.73.57.130:28027")
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 5 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 · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 5 Oct, 03:35 UTC24d ago | 1 | NaN | running | 0 |
# 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())
Map
4500 · seed 877712140
- map
- Procedural Map
- size
- 4500
- seed
- 877712140
Server
srv.info()- address
- 198.73.57.130:28025
- region
- –
- max players
- 30
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 5 Oct 2026, 03:35 UTC
- hostname
- –
- first seen
- 5 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 491 on average | 84/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 115/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 284 on average | 397/450 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 277 on average | 21/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 266 on average | 476/525 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 253 on average | 362/425 |
Quick answers
From the figures on this page.
Population data
What position does gcb server take in the server rankings?
Player hours over seven days put gcb server at #15,284, in the top 69% of the ranked set.
What population does gcb server carry?
Current row: 0 players on gcb server, against 30 slots. Over the last seven days it averaged 0 players.
Server facts
What does performance look like on gcb server?
Server fps over the last 48 hours averages 93; the floor is 79. The entity count peaked at 116,925, covering buildings, deployables and the rest of the world. The memory field tops out at 3,743 MB. What players call lag is these two fields together: low fps and a rising entity count.
Which Rust version is gcb server on?
Rust network protocol 2634 and build 166652 on Windows is what gcb server runs. Steam updates your game for you, but the protocol must match to join.
How reliable is gcb server, and is it up?
gcb server reports itself online at the current refresh. Count back 2 days 20 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. Its earliest recorded date in Rust Data is 5 October 2026.
Where does gcb server sit?
There is no region published for gcb server. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 198.73.57.130:28025.
Rules, settings, map
What rules and settings are recorded for gcb server?
No gather rate appears in the name: gcb server. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. The server browser lists it under Community. VAC is running: Valve's anti-cheat is on.
What is the map on gcb server?
gcb server runs a procedural map of size 4,500 with seed 877712140, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
When does gcb server wipe, and how often?
The record for gcb server holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 24 days 21 hours ago.
On gcb server, what happens on wipe day?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 0 hours in.
Tags and filters
Which lists on Rust Data hold gcb server, and which filters?
On Rust Data, gcb server appears in these lists: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the server tags on gcb server?
These tags are published by gcb server and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp30 (Max players): Slot count: 30; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): The server runs build 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
How can I connect to gcb server?
In Rust, F1 opens the console: type client.connect 198.73.57.130:28025. Launch Rust on this page does the same by opening the game through Steam and connecting.