Skip to the content
Dive report

Solo|x2|Kits|TP|Vip[Viking]

Online 78.29.14.210:28115 checked 11m ago

2x solo weekly wipes moddedoxide
Drop in
4/ 100 players now 4% full
17-day averagepeak 6
#3,191ranktop 14%
6d agolast wipeweekly schedule
12hnext wipeMon 19 Oct, 00:04 UTC

Players

AveragePeak
0246812:0021:0006:0015:0000:0009:00

Hourly average and peak, UTC.

Server performance

025507510012:0021:0006:0015:0000:0009: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.

Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep26 Sep1 Oct7 Oct12 Oct18 Oct

Top 14% of all ranked servers, and #129 of the solo servers (top 59%). Ranked on player hours over the last seven days.

Wipe schedule

fixed weekdays

Next wipe Monday 19 October, 00:04 UTC, in 12h. Every Monday at 00:04 UTC · high confidence

usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak4players, last three wipes
crowd held80%else halves by day 2

Coming wipes

  • 12h
    Mon 19 Oct, 00:04 UTC
  • 7d 12h
    Mon 26 Oct, 00:04 UTC
  • 14d 12h
    Mon 2 Nov, 00:04 UTC
  • 18d 7h
    Thu 5 Nov, 19:00 UTC
    FW
  • 21d 12h
    Mon 9 Nov, 00:04 UTC
  • 28d 12h
    Mon 16 Nov, 00:04 UTC
  • 35d 12h
    Mon 23 Nov, 00:04 UTC
  • 42d 12h
    Mon 30 Nov, 00:04 UTC

The first 48 hours of its last wipes

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

Players each hour, from the hour of the wipe. The latest peaked at 4, 16 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 12 Oct, 00:04 UTC6d ago 4 – running 0
Mon 5 Oct, 00:13 UTC13d ago 5 held half 7 days 0
Thu 1 Oct, 23:56 UTC FW16d ago 4 held half 3 days 0
Mon 28 Sep, 00:04 UTC20d ago 6 halved by day 2 4 days 0
Sun 20 Sep, 23:56 UTC27d ago 4 held half 7 days 0
Mon 14 Sep, 00:07 UTC34d ago 4 held half 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.

Neighbouring dive spots

Similar servers

the same kind of game, then region, group limit, rate and wipes

From the figures on this page

Quick answers

Tags and search

Where does Solo|x2|Kits|TP|Vip[Viking] appear in Rust Going Deep lists and filters?

The Rust Going Deep lists that carry Solo|x2|Kits|TP|Vip[Viking] are: 2x Rust servers, Modded Rust servers and Solo Rust servers. You can find it on the server list by these filters: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Solo; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x.

What's the meaning of the tags on Solo|x2|Kits|TP|Vip[Viking]?

Solo|x2|Kits|TP|Vip[Viking]'s game browser tags read: gmrust (Game mode): Survival, as standard Rust does it; mp100 (Max players): The slot count is 100; ts1 (Group limit): You can have up to 1 in a team; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs167781 (Build): The build number is 167781; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): It has no region code; ^w (Weekly): A wipe every week; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Plugins or settings make changes, so it's listed as Modded. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.

Server details

Is Solo|x2|Kits|TP|Vip[Viking] lag-free?

Average server fps for the last 48 hours was 56, and the lowest was 10. At its peak it carried 125,508 entities, including buildings and deployables. 4,519 MB was the highest memory it used. What players notice as lag comes from low fps and a rising entity count.

What's the location of Solo|x2|Kits|TP|Vip[Viking]?

Solo|x2|Kits|TP|Vip[Viking] does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 78.29.14.210:28115.

How reliable is Solo|x2|Kits|TP|Vip[Viking]?

Solo|x2|Kits|TP|Vip[Viking] is live as of this check. Its reported uptime shows a restart about 9 hours ago. It was up 100% of the time over the last full 7 days, 168 of 168 hours. The first sighting by Rust Going Deep was on 13 September 2026.

What Rust version is Solo|x2|Kits|TP|Vip[Viking] on?

On Linux, Solo|x2|Kits|TP|Vip[Viking] runs Rust network protocol 2634 and build 167781. Steam handles the update; you just need your game on the matching protocol to join.

Wipe details

What schedule does Solo|x2|Kits|TP|Vip[Viking] follow for wipes?

The wipe rhythm for Solo|x2|Kits|TP|Vip[Viking] is every Monday at 00:04 UTC. Expect the next wipe on Monday 19 October at 00:04 UTC. This world has been running since 6 days 11 hours ago. Wipes are scheduled weekly, according to its tags.

What can you expect on wipe day at Solo|x2|Kits|TP|Vip[Viking]?

Across its recent wipes, the average busiest point drew 4 players. 16 hours after the latest wipe started, the crowd hit its peak. Above half that peak until the next wipe: the crowd managed this in 80% of recent wipes. It held on until day 2, then dipped below half.

Rules and settings

What settings and rules have been applied to Solo|x2|Kits|TP|Vip[Viking]?

At 2x gather, Solo|x2|Kits|TP|Vip[Viking] does what its name suggests. You play alone; teams are not permitted. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. In the server browser it sits under Modded, where plugins or settings change the game. Plugins in use: Oxide. VAC, Valve's anti-cheat, is enabled.

Which map is active on Solo|x2|Kits|TP|Vip[Viking]?

The map on Solo|x2|Kits|TP|Vip[Viking] is procedural and size 4,500, generated by the game with seed 406166594. You can see it on RustMaps from this page, since the same size and seed produce the same map.

Population

What's the population like on Solo|x2|Kits|TP|Vip[Viking]?

Out of 100 slots, 4 are filled on Solo|x2|Kits|TP|Vip[Viking] right now. For the past week, players averaged 1 with a high of 6. Over the last 48 hours, 19:00 UTC drew the most players, 6 on average.

What's Solo|x2|Kits|TP|Vip[Viking]'s rank among Rust servers?

Over the last seven days, Solo|x2|Kits|TP|Vip[Viking] is #3,191 by player hours, among the top 14% of all ranked servers. Within the solo group, its position is #129.

Getting in

What's the process to join Solo|x2|Kits|TP|Vip[Viking]?

To join, open Rust, hit F1, and enter client.connect 78.29.14.210:28115. Or click Launch Rust on this page to open the game through Steam and connect. http://viking.gamestores.app/ is its website.

What each one means

Server tags

Published as mp100,ptrak,$r?,v2634,^w,gmrust,cs167781,ts1,^o^z

Game

gmrust
Game mode Survival, as standard Rust does it.
mp100
Max players The slot count is 100.
ts1
Group limit You can have up to 1 in a team.
v2634
Protocol The protocol is 2634; a different version won't get you in.
cs167781
Build The build number is 167781.
ptrak
Networking The network layer is RakNet, Rust's default.
$r?
Region code It has no region code.

Wipe schedule

^w
Weekly A wipe every week.

Mods and access

^o
Oxide This server uses Oxide (uMod) for plugins.
^z
Modded Plugins or settings make changes, so it's listed as 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.