Offline 185.54.57.12:28015 checked 11h ago
Combat Bob
Connect
srv = rust.server("185.54.57.12:28017")
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. 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 bestTop 58% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 28 Oct, 18:46 UTC13h ago | NaN | NaN | running | 0 |
| 1 | Mon 19 Oct, 21:56 UTC9d ago | 1 | halved by day 6 | 8.9 days | 0 |
| 2 | Sat 3 Oct, 22:07 UTC25d ago | 1 | halved by day 8 | 16 days | 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
- map
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 185.54.57.12:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 28 Oct 2026, 18:46 UTC
- hostname
- –
- first seen
- 3 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 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 105/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 149/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 46/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 18/1000 |
Quick answers
From the figures on this page.
Player counts
What position does Combat Bob take in the server rankings?
Player hours over seven days put Combat Bob at #12,809, in the top 58% of the ranked set.
What population does Combat Bob carry?
Combat Bob returns no live count at this refresh, having last been seen 11 hours ago. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 20:00 UTC is the busiest, at 1 players.
Server facts
What is the Rust version on Combat Bob?
The build is Rust network protocol 2635 and build 168909 on Windows, run by Combat Bob. The protocol has to match before you can join, and Steam does the updating.
Is Combat Bob up, and what does its uptime show?
The latest sample has Combat Bob offline, with a last sighting 11 hours ago. 5 of 168 hours up over the last 7 full days, or 3%. Its earliest recorded date in Rust Data is 3 October 2026.
Which location does Combat Bob run from?
No region is published by Combat Bob. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 185.54.57.12:28015.
Settings and map
Which rules apply on Combat Bob, and what settings?
No gather rate appears in the name: Combat Bob. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Carbon. Anti-cheat status: VAC on.
Wipe schedule
When does Combat Bob wipe, and how often?
Combat Bob wipes on no fixed rhythm, so there is nothing to predict. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 13 hours ago.
What is wipe day on Combat Bob like?
Recent wipes averaged 1 players at their peak. 1 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 0% of recent wipes. The drop under half arrived by day 7 in the other cases.
Tags, lists
Which lists on Rust Data hold Combat Bob, and which filters?
The Rust Data lists that Combat Bob fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 24 hours.
How should you read the server tags on Combat Bob?
The game's server browser reads these tags from Combat Bob: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): Slot count: 5; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join Combat Bob?
Enter client.connect 185.54.57.12:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.