Offline 194.44.107.134:28015 checked 22d ago
komar
Connect
srv = rust.server("194.44.107.134:28016")
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 best
Top 62% 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, 25 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 4 Oct, 16:09 UTC24d ago | 1 | NaN | running | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 194.44.107.134:28015
- region
- –
- max players
- 3
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Oct 2026, 16:09 UTC
- hostname
- –
- first seen
- 4 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 · 152 on average | 41/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 59/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 19/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 5/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does komar rank?
Player hours over seven days put komar at #13,786, in the top 62% of the ranked set.
How many players does komar hold at once?
komar returns no live count at this refresh, having last been seen 22 days 10 hours ago.
About the server
What is the Rust version on komar?
The build is Rust network protocol 2634 and build 166586 on Windows, run by komar. The protocol has to match before you can join, and Steam does the updating.
Is komar up, and what does its uptime show?
Offline now for komar, last seen 22 days 10 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 4 October 2026.
Where does komar sit?
For komar, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 194.44.107.134:28015 is its address.
Rules, settings, map
Which settings and rules does komar run?
No gather rate appears in the name: komar. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. The VAC field reads off.
Which map has komar selected?
komar runs a procedural map, which the game generates.
Wipe data
When does komar wipe, and how often?
Too few wipes are on record for komar to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 24 days 13 hours ago, and that is the one in play.
On komar, what happens on wipe day?
The average peak over recent wipes is 1 players. 25 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which lists on Rust Data hold komar, and which filters?
On Rust Data, komar appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on komar?
The game's server browser reads these tags from komar: gmrust (Game mode): Rust survival in its standard form; mp3 (Max players): The server lists 3 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs166586 (Build): The server runs build 166586; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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.
How to join
What is the way to join komar?
The manual route: launch Rust, F1, then client.connect 194.44.107.134:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.