Offline 134.19.177.230:26069 checked 19d ago
combat
Connect
srv = rust.server("134.19.177.230:26070")
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 8 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 bestTop 72% 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 | Fri 9 Oct, 21:36 UTC20d ago | 1 | NaN | running | 0 |
| 1 | Thu 8 Oct, 19:01 UTC21d ago | 2 | NaN | 1.1 days | 1 |
# 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
5000 · seed 69737
- map
- Procedural Map
- size
- 5000
- seed
- 69737
Server
srv.info()- address
- 134.19.177.230:26069
- region
- –
- max players
- 200
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 9 Oct 2026, 21:36 UTC
- hostname
- –
- first seen
- 8 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 | 43/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 120 on average | 80/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 32/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 84/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 302/310 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does combat rank?
Rank #15,863 on seven-day player hours for combat, within the top 72% of all ranked servers.
How full does combat run?
combat returns no live count at this refresh, having last been seen 19 days 2 hours ago.
Server facts
Which Rust version is combat on?
Version Rust network protocol 2634 and build 167398 on Linux is reported by combat. Steam updates your game for you, but the protocol must match to join.
Is combat up, and what does its uptime show?
Offline now for combat, last seen 19 days 2 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 8 October 2026.
Which location does combat run from?
No region is published by combat. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 134.19.177.230:26069 is its address.
Settings and map
Which settings and rules does combat run?
You will not find a gather rate in the string combat. 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. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Anti-cheat status: VAC on.
What is the map on combat?
combat runs a procedural map of size 5,000 with seed 69737, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
On what schedule does combat wipe?
A rhythm cannot be read from the wipes of combat on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 20 days ago, and that is the one in play.
On combat, what happens on wipe day?
Across recent wipes the busiest point averaged 2 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which Rust Data filters and lists contain combat?
The Rust Data lists that combat fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on combat hold?
These tags are published by combat and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp200 (Max players): Slot count: 200; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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
How can I connect to combat?
Enter client.connect 134.19.177.230:26069 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.