Offline 186.54.172.164:28115 checked 19d ago
KELQOR WipeGuard QA
Connect
srv = rust.server("186.54.172.164:28117")
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 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, 19:28 UTC19d 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
- 186.54.172.164:28115
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 9 Oct 2026, 19:33 UTC
- hostname
- –
- first seen
- 9 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 · 151 on average | 150/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 191/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 93/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 88 on average | 216/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 344/350 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does KELQOR WipeGuard QA rank?
Player hours over seven days put KELQOR WipeGuard QA at #15,814, in the top 72% of the ranked set.
How many players does KELQOR WipeGuard QA hold at once?
The current row shows KELQOR WipeGuard QA offline; the last response was 19 days 12 hours ago.
Server facts
What is the Rust version on KELQOR WipeGuard QA?
Version Rust network protocol 2634 and build 167398 on Windows is reported by KELQOR WipeGuard QA. Steam updates your game for you, but the protocol must match to join.
How reliable is KELQOR WipeGuard QA, and is it up?
KELQOR WipeGuard QA is offline at this refresh; the last response came 19 days 12 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 9 October 2026.
Which location does KELQOR WipeGuard QA run from?
There is no region published for KELQOR WipeGuard QA. Rust Data does not look up where the machine stands; it shows where a server says it is. 186.54.172.164:28115 is its address.
Rules, settings, map
Which settings and rules does KELQOR WipeGuard QA run?
You will not find a gather rate in the string KELQOR WipeGuard QA. The group limit sits at the default of 8 players. Recorded as survival, 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. Oxide plugins run on it. The VAC field reads off.
Which map has KELQOR WipeGuard QA selected?
A procedural map runs on KELQOR WipeGuard QA, generated by the game.
Wipe data
On what schedule does KELQOR WipeGuard QA wipe?
Too few wipes are on record for KELQOR WipeGuard QA 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. The world it runs now was generated 19 days 22 hours ago.
What is wipe day on KELQOR WipeGuard QA like?
The average peak over recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which lists on Rust Data hold KELQOR WipeGuard QA, and which filters?
On Rust Data, KELQOR WipeGuard QA 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 KELQOR WipeGuard QA?
The game's server browser reads these tags from KELQOR WipeGuard QA: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): 2 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167398 (Build): Build number: 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): Modded listing: the game is changed by plugins or settings. 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
What is the way to join KELQOR WipeGuard QA?
In Rust, F1 opens the console: type client.connect 186.54.172.164:28115. Launch Rust on this page does the same by opening the game through Steam and connecting.