Rust Server TrendsSeismic network · station log
Recording Stations11,836 Players72,948 Active3,667 Wipes · 3 h218 48 h

Station XX-3856 · recording

Hapis|x10|Kits|TP|Vip[Viking]

Online 78.29.14.210:28315 checked 8m ago

10x weekly wipes moddedoxide
Connect
Players now
0/ 100
0% full
Motion · 24 h
M0.0falling
−1 players on the day
7-day average
1
peak 4
Rank
#3,856
top 17%
Last wipe
3d ago
weekly schedule
Next wipe
3d 10h
Mon 2 Nov, 00:03 UTC
Seismic record · station XX-3856 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 100 slots
Motion · 24 h
M0.0falling−1 players
Sharpest hour
+1into Wed 10:00 UTC
Peak · 48 h
2most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.511.5214:0023:0008:0017:0003:0012:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020014:0023:0008:0017:0003:0012:00

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 17% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

from its schedule tag

Next wipe Monday 2 November, 00:03 UTC, in 3d 10h. Its weekly schedule tag · low confidence

usual gap
7 daysbetween real wipes
on rhythm
67%of its recent wipes
wipe-day peak
3players, last three wipes
crowd held
80%else halves by day 3

Coming wipes

  1. 3d 10hMon 2 Nov, 00:03 UTC
  2. 7d 5hThu 5 Nov, 19:00 UTCFW
  3. 10d 10hMon 9 Nov, 00:03 UTC
  4. 17d 10hMon 16 Nov, 00:03 UTC
  5. 24d 10hMon 23 Nov, 00:03 UTC
  6. 31d 10hMon 30 Nov, 00:03 UTC
  7. 35d 5hThu 3 Dec, 19:00 UTCFW
  8. 38d 10hMon 7 Dec, 00:03 UTC

The first 48 hours of its last wipes

Mon 19 OctMon 12 OctMon 5 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 7 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 19 Oct, 00:03 UTC10d ago M0.5rising 3 – running 0
Mon 12 Oct, 00:02 UTC17d ago M0.6rising 4 held half 7 days 0
Mon 5 Oct, 00:03 UTC24d ago M0.3rising 2 held half 7 days 0
Thu 1 Oct, 23:58 UTC FW27d ago M0.6rising 4 held half 3 days 0
Sun 27 Sep, 23:59 UTC31d ago M0.3rising 2 held half 4 days 0
Sun 20 Sep, 23:58 UTC38d ago M0.5rising 3 halved by day 3 7 days 0
Mon 14 Sep, 00:01 UTC45d ago M0.0steady 0 – 7 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Atlas - EU 10x | No BPs | Kits | Shop EU · groups of 20+ · 10x · weekly · 350 on average
507/ 550
TemplarGaming 10x Swift Loot++|PvP|MyMini|SkinBox|x10 JUST WIPE NA · groups of 8+ · 10x · weekly · 181 on average
83/ 200
Atlas - US 10x | No BPs | Kits | Shop NA · groups of 30+ · 10x · weekly · 180 on average
140/ 150
KRAKEN | X10 | EU | KITS | RP | FPS+ EU · groups of 14+ · 10x · weekly · 153 on average
109/ 400
Vitality - US 10x | No BPs | Kits | Shop NA · groups of 32+ · 10x · weekly · 64 on average
22/ 50
[LATAM] LUNARUST X10 | 28/10 Wipe SA · groups of 8+ · 10x · weekly · 61 on average
6/ 100
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Hapis|x10|Kits|TP|Vip[Viking]?

The procedural map on Hapis|x10|Kits|TP|Vip[Viking] is size 4,096 with seed 867815145, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map. You will find the map named Custom Map.

Which settings and rules apply on Hapis|x10|Kits|TP|Vip[Viking]?

10x gather is what Hapis|x10|Kits|TP|Vip[Viking] runs, judging by its name. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.

Population

How many players are recorded on Hapis|x10|Kits|TP|Vip[Viking] right now?

A reading taken now shows 0 players on Hapis|x10|Kits|TP|Vip[Viking], which has 100 slots. Across seven days this server recorded an average of 1 players and a peak of 4. The last 48 hours show their highest activity at 10:00 UTC, averaging 2 players.

How does Hapis|x10|Kits|TP|Vip[Viking] rank against other Rust servers?

Over the last seven days, Hapis|x10|Kits|TP|Vip[Viking] recorded enough player hours to reach #3,856 worldwide, placing it in the top 17% of all ranked servers.

Server facts

How reliably does Hapis|x10|Kits|TP|Vip[Viking] stay online?

Hapis|x10|Kits|TP|Vip[Viking] is up at the moment. The uptime it reports puts its last restart about 11 hours ago. It was up 99% of the time across the last 7 full days: 167 of 168 hours. 13 September 2026 is when Rust Server Trends first recorded it.

Does Hapis|x10|Kits|TP|Vip[Viking] hold a steady tick rate?

The 48-hour average is 32 server fps; 4 is the lowest observed. The world held up to 68,915 entities at its peak, buildings and deployables included. Its highest memory use was 3,634 MB. What you feel as lag is the combination of low fps and a rising entity count.

Which region does Hapis|x10|Kits|TP|Vip[Viking] run from?

A region is not published by Hapis|x10|Kits|TP|Vip[Viking]. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 78.29.14.210:28315 is the address it uses.

Which Rust version is Hapis|x10|Kits|TP|Vip[Viking] running?

Hapis|x10|Kits|TP|Vip[Viking] is running Rust network protocol 2635 and build 168909 on a machine with Linux. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on Hapis|x10|Kits|TP|Vip[Viking]?

On average, the busiest point of its recent wipes drew 3 players. 7 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 80% of its recent wipes. By day 3 it fell below half in the wipes where it didn't hold.

How often does Hapis|x10|Kits|TP|Vip[Viking] wipe, and on which days?

The prediction follows its tag, because too few of Hapis|x10|Kits|TP|Vip[Viking]'s wipes are on record to confirm its schedule. Monday 2 November at 00:03 UTC is when its next wipe is due. The present world dates from 3 days 13 hours. A weekly wipe schedule is published in its tags.

Server tags

What do the server tags on Hapis|x10|Kits|TP|Vip[Viking] mean?

These are the tags Hapis|x10|Kits|TP|Vip[Viking] publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): The server has 100 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^w (Weekly): Wipes happen weekly; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does Hapis|x10|Kits|TP|Vip[Viking] appear?

The Rust Server Trends lists that take in Hapis|x10|Kits|TP|Vip[Viking] are: 10x Rust servers and Modded Rust servers, tracked live. 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.

Connecting

How do you connect to Hapis|x10|Kits|TP|Vip[Viking]?

To join, enter client.connect 78.29.14.210:28315 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. http://viking.gamestores.app/ is where its website lives.

Instrument codes

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^w,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
mp100
Max players The server has 100 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is set for this server.

Wipe schedule

^w
Weekly Wipes happen weekly.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.