Skip to the content
Dive report

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

Online 78.29.14.210:28215 checked 9m ago

2x trio weekly wipes moddedoxide
Drop in
0/ 100 players now 0% full
07-day averagepeak 4
#5,448ranktop 25%
2d agolast wipeweekly schedule
4d 12hnext wipeThu 22 Oct, 23:33 UTC

Players

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

Hourly average and peak, UTC.

Server performance

05010015020012: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
12k4k6k8k20 Sep26 Sep1 Oct7 Oct12 Oct18 Oct

Top 25% of all ranked servers, and #350 of the trio servers (top 57%). Ranked on player hours over the last seven days.

Wipe schedule

fixed weekdays

Next wipe Thursday 22 October, 23:33 UTC, in 4d 12h. Every Thursday at 23:33 UTC · high confidence

usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak3players, last three wipes
crowd held0%else halves by day 2.5

Coming wipes

  • 4d 12h
    Thu 22 Oct, 23:33 UTC
  • 11d 12h
    Thu 29 Oct, 23:33 UTC
  • 18d 7h
    Thu 5 Nov, 19:00 UTC
    FW
  • 25d 12h
    Thu 12 Nov, 23:33 UTC
  • 32d 12h
    Thu 19 Nov, 23:33 UTC
  • 39d 12h
    Thu 26 Nov, 23:33 UTC

The first 48 hours of its last wipes

Thu 15 OctThu 8 OctThu 1 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 23:33 UTC2d ago 2 – running 0
Thu 8 Oct, 23:32 UTC9d ago 3 halved by day 2 7 days 0
Thu 1 Oct, 23:32 UTC FW16d ago 5 halved by day 4 7 days 0
Thu 24 Sep, 23:32 UTC23d ago 5 halved by day 3 7 days 0
Thu 17 Sep, 23:32 UTC30d ago 8 halved by day 2 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 MAX3|x2|Kits|TP|Vip[Viking] appear in Rust Going Deep lists and filters?

These Rust Going Deep lists include MAX3|x2|Kits|TP|Vip[Viking]: 2x Rust servers, Modded Rust servers and Trio Rust servers, live. Its entry appears under the filters Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last 3 days; Gather rate: 2x.

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

gmrust (Game mode): Survival, as standard Rust does it; mp100 (Max players): It holds 100 players; ts3 (Group limit): You can have up to 3 in a team; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167781 (Build): It's on build 167781; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^w (Weekly): It wipes once a week; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded — that is the tag list MAX3|x2|Kits|TP|Vip[Viking] puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.

Server info

What's the performance like on MAX3|x2|Kits|TP|Vip[Viking]?

It averaged 68 server fps over the last 48 hours, with a low of 10. At its peak it carried 91,567 entities, including buildings and deployables. 3,307 MB was the highest memory it used. What players notice as lag comes from low fps and a rising entity count.

Where can you find MAX3|x2|Kits|TP|Vip[Viking]?

No region comes from MAX3|x2|Kits|TP|Vip[Viking]. 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:28215.

What's the uptime like for MAX3|x2|Kits|TP|Vip[Viking]?

MAX3|x2|Kits|TP|Vip[Viking] is up and reachable at the moment. 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. 13 September 2026 is when Rust Going Deep first saw it.

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

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

Wipe info

When does MAX3|x2|Kits|TP|Vip[Viking] wipe?

MAX3|x2|Kits|TP|Vip[Viking] runs on a every Thursday at 23:33 UTC wipe cycle. Expect the next wipe on Thursday 22 October at 23:33 UTC. This world has been running since 2 days 11 hours ago. The tags show wipes set to happen every week.

What happens on wipe day at MAX3|x2|Kits|TP|Vip[Viking]?

Recent wipes have averaged a busiest crowd of 3 players. On the latest wipe, 16 hours passed before the crowd peaked. Above half that peak until the next wipe: the crowd managed this in 0% of recent wipes. By day 2.5, the pop had dropped under half.

Rules and settings

Which rules and settings is MAX3|x2|Kits|TP|Vip[Viking] running?

Gather rates here are 2x, as MAX3|x2|Kits|TP|Vip[Viking] announces in its name. The group cap is 3 players (trio). It runs survival, gather, build and raid, the standard game. You can fight and raid other players. Plugins or settings change the game, so the browser lists it as Modded. You will find Oxide plugins installed. VAC is on: Valve's anti-cheat is active.

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

The map on MAX3|x2|Kits|TP|Vip[Viking] is procedural and size 4,000, generated by the game with seed 83483847. The map is reproducible from its size and seed, so RustMaps can show it from this page.

Player stats

How many players are on MAX3|x2|Kits|TP|Vip[Viking]?

Out of 100 slots, 0 are filled on MAX3|x2|Kits|TP|Vip[Viking] right now. The seven-day average is 0 players, with a peak of 4. The busiest point in the last 48 hours was 04:00 UTC, averaging 3 players.

Where does MAX3|x2|Kits|TP|Vip[Viking] sit in the rankings?

Over the last seven days, MAX3|x2|Kits|TP|Vip[Viking] is #5,448 by player hours, among the top 25% of all ranked servers. Within the trio group, its position is #350.

How to join

How do you get into MAX3|x2|Kits|TP|Vip[Viking]?

To join, open Rust, hit F1, and enter client.connect 78.29.14.210:28215. 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,ts3,^o^z

Game

gmrust
Game mode Survival, as standard Rust does it.
mp100
Max players It holds 100 players.
ts3
Group limit You can have up to 3 in a team.
v2634
Protocol To join, your game has to be on protocol 2634.
cs167781
Build It's on build 167781.
ptrak
Networking RakNet, the network layer Rust uses by default.
$r?
Region code The region field is empty.

Wipe schedule

^w
Weekly It wipes once a week.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^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.