Online 78.29.14.210:28315 checked 8m ago
Hapis|x10|Kits|TP|Vip[Viking]
Connect
srv = rust.server("78.29.14.210:28316")
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 17 Sep. 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 17% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Monday 2 November, 00:03 UTC, in 3d 9h. # Its weekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 3d 9h | Mon 2 Nov, 00:03 UTC | wipe |
| 1 | 7d 4h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 10d 9h | Mon 9 Nov, 00:03 UTC | wipe |
| 3 | 17d 9h | Mon 16 Nov, 00:03 UTC | wipe |
| 4 | 24d 9h | Mon 23 Nov, 00:03 UTC | wipe |
| 5 | 31d 9h | Mon 30 Nov, 00:03 UTC | wipe |
| 6 | 35d 4h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 7 | 38d 9h | Mon 7 Dec, 00:03 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 7 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 19 Oct, 00:03 UTC10d ago | 3 | NaN | running | 0 |
| 1 | Mon 12 Oct, 00:02 UTC17d ago | 4 | held half | 7 days | 0 |
| 2 | Mon 5 Oct, 00:03 UTC24d ago | 2 | held half | 7 days | 0 |
| 3 | Thu 1 Oct, 23:58 UTC FW27d ago | 4 | held half | 3 days | 0 |
| 4 | Sun 27 Sep, 23:59 UTC31d ago | 2 | held half | 4 days | 0 |
| 5 | Sun 20 Sep, 23:58 UTC38d ago | 3 | halved by day 3 | 7 days | 0 |
| 6 | Mon 14 Sep, 00:01 UTC45d ago | 0 | NaN | 7 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
4096 · seed 867815145- map
- Custom Map
- size
- 4096
- seed
- 867815145
Server
srv.info()- address
- 78.29.14.210:28315
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- weekly
- last wipe
- 25 Oct 2026, 23:59 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Atlas - EU 10x | No BPs | Kits | Shop | EU · groups of 20+ · 10x · weekly · 350 on average | 498/600 |
| 1 | TemplarGaming 10x Swift Loot++|PvP|MyMini|SkinBox|x10 JUST WIPE | NA · groups of 8+ · 10x · weekly · 180 on average | 84/200 |
| 2 | Atlas - US 10x | No BPs | Kits | Shop | NA · groups of 30+ · 10x · weekly · 180 on average | 139/150 |
| 3 | KRAKEN | X10 | EU | KITS | RP | FPS+ | EU · groups of 14+ · 10x · weekly · 153 on average | 103/400 |
| 4 | Vitality - US 10x | No BPs | Kits | Shop | NA · groups of 32+ · 10x · weekly · 64 on average | 25/50 |
| 5 | [LATAM] LUNARUST X10 | 28/10 Wipe | SA · groups of 8+ · 10x · weekly · 60 on average | 7/100 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Hapis|x10|Kits|TP|Vip[Viking] rank?
Over the last seven days Hapis|x10|Kits|TP|Vip[Viking] sits at #3,849 on player hours, in the top 17% of ranked servers.
How full does Hapis|x10|Kits|TP|Vip[Viking] run?
Current row: 0 players on Hapis|x10|Kits|TP|Vip[Viking], against 100 slots. Over the last seven days it averaged 1 players and peaked at 4. The 48-hour sample puts the busiest hour at 10:00 UTC, averaging 2 players.
Server facts
How smoothly does Hapis|x10|Kits|TP|Vip[Viking] run?
The 48-hour average is 33 server fps, with a low of 4. Buildings, deployables and all else in the world took the count as high as 68,915 entities. The memory field tops out at 3,634 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is Hapis|x10|Kits|TP|Vip[Viking] on?
The build is Rust network protocol 2635 and build 168909 on Linux, run by Hapis|x10|Kits|TP|Vip[Viking]. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Hapis|x10|Kits|TP|Vip[Viking], and is it up?
Online is the state at the latest refresh for Hapis|x10|Kits|TP|Vip[Viking]. Count back 11 hours from its reported uptime to get the last restart. Uptime of 99% across the last 7 full days: 167 hours of 168. Rust Data logged it first on 13 September 2026.
Which location does Hapis|x10|Kits|TP|Vip[Viking] run from?
For Hapis|x10|Kits|TP|Vip[Viking], no region is published. 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 78.29.14.210:28315.
Rules, settings, map
Which settings and rules does Hapis|x10|Kits|TP|Vip[Viking] run?
Gather sits at 10x, read from the server's own name: Hapis|x10|Kits|TP|Vip[Viking]. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has Hapis|x10|Kits|TP|Vip[Viking] selected?
The game generates the map on Hapis|x10|Kits|TP|Vip[Viking]: procedural, size 4,096, seed 867815145. Size and seed fix the map, so RustMaps can show it, linked from this page. Recorded under map name: Custom Map.
Wipes and dates
When does Hapis|x10|Kits|TP|Vip[Viking] wipe, and on what schedule?
Too few wipes are on record for Hapis|x10|Kits|TP|Vip[Viking] to confirm its schedule, so the tag drives the prediction. The schedule puts the next wipe on Monday 2 November at 00:03 UTC. A new world was started 3 days 14 hours ago, and that is the one in play. Its tags carry a weekly wipe schedule.
What is wipe day on Hapis|x10|Kits|TP|Vip[Viking] like?
Across recent wipes the busiest point averaged 3 players. The crowd on the latest wipe topped out 7 hours after it began. The crowd stayed above half that peak until the next wipe in 80% of recent wipes. In the wipes where it did not hold, half was lost by day 3.
Tags and filters
Which Rust Data filters and lists contain Hapis|x10|Kits|TP|Vip[Viking]?
The Rust Data lists that Hapis|x10|Kits|TP|Vip[Viking] fits are: Modded Rust servers and 10x Rust servers: the live sample. These filters bring it up on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 10x.
Which meanings do the tags on Hapis|x10|Kits|TP|Vip[Viking] hold?
The game's server browser reads these tags from Hapis|x10|Kits|TP|Vip[Viking]: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): Slot count: 100; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^w (Weekly): The interval is one week; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^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 Hapis|x10|Kits|TP|Vip[Viking]?
In Rust, F1 opens the console: type client.connect 78.29.14.210:28315. Launch Rust on this page does the same by opening the game through Steam and connecting. http://viking.gamestores.app/ is the website recorded for it.