RUST METRICSFlight deck · live data
Data live Servers11,898 Players102,212 Populated3,932 Fresh wipes 3 h403 Scan5 min
‹ All servers78.29.14.210:28215
Online Full Queue Fresh wipe Wipe due No query

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

Online 78.29.14.210:28215 checked 13m ago

2x trio weekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Thu 16:00 UTC
0 25 50 75 100 PAX 1 /100

Players now

1% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 87 SERVER FPS

Server fps

48 h low 10 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 101,763 ×1000

Entities

48 h range 96,719–102,726 · memory 2,648 MB
1239 ET SINCE RESTART 16:35

Uptime

16 h 35 min since its last restart, at the last reading
7-day average1peak 4
Rank#3,134top 14%
Last wipe6d agoweekly schedule
Next wipe5hThu 29 Oct, 23:32 UTC
Memory2,648MB48 h peak 2 players
REC 1

Players

AveragePeak
00.511.5218:0003:0012:0022:0007:0016:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020018:0003:0012:0022:0007:0016: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.

REC 3

Rank

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

Top 14% of all ranked servers, and #232 of the trio servers (top 37%). Ranked on player hours over the last seven days.

PLAN

Wipe schedule

fixed weekdays

Next wipe Thursday 29 October, 23:32 UTC, in 5h. Every Thursday at 23:32 UTC · high confidence

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

Coming wipes

  1. WPT 1Thu 29 Oct, 23:32 UTC5h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 1hFW
  3. WPT 3Thu 12 Nov, 23:32 UTC14d 5h
  4. WPT 4Thu 19 Nov, 23:32 UTC21d 5h
  5. WPT 5Thu 26 Nov, 23:32 UTC28d 5h
  6. WPT 6Thu 3 Dec, 19:00 UTC35d 1hFW
  7. WPT 7Thu 10 Dec, 23:32 UTC42d 5h

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 23:32 UTC6d ago 4 – running 0
Thu 15 Oct, 23:33 UTC13d ago 2 held half 7 days 0
Thu 8 Oct, 23:32 UTC20d ago 3 halved by day 2 7 days 0
Thu 1 Oct, 23:32 UTC FW27d ago 5 halved by day 4 7 days 0
Thu 24 Sep, 23:32 UTC34d ago 5 halved by day 3 7 days 0
Thu 17 Sep, 23:32 UTC41d 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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on MAX3|x2|Kits|TP|Vip[Viking]?

An average of 3 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 38 hours in. Until the next wipe, the crowd stayed above half that peak in 20% of its recent wipes. By day 2.5 it fell below half when it didn't.

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

Wipes on MAX3|x2|Kits|TP|Vip[Viking] come every Thursday at 23:32 UTC. Due on Thursday 29 October at 23:32 UTC is its next wipe. The world it runs now was made 6 days 18 hours ago. The tags state a wipe schedule of one wipe a week.

Tag meanings

How should you read the tags on MAX3|x2|Kits|TP|Vip[Viking]?

These are the tags MAX3|x2|Kits|TP|Vip[Viking] publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): The server holds 100 slots; ts3 (Group limit): Teams are capped at 3; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^w (Weekly): Wipe cycle: weekly; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does MAX3|x2|Kits|TP|Vip[Viking] appear in Rust Metrics lists and filters?

On Rust Metrics, MAX3|x2|Kits|TP|Vip[Viking] sits in these lists: 2x Rust servers, checked live, Modded Rust servers, checked live and Trio servers, group limit 3. These filters bring it up on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x.

Population

What position does MAX3|x2|Kits|TP|Vip[Viking] hold among Rust servers?

Ranking for MAX3|x2|Kits|TP|Vip[Viking]: #3,134 on seven-day player hours, top 14% of all ranked servers. Check: group rank. #232 among trio servers.

What is the population on MAX3|x2|Kits|TP|Vip[Viking]?

1 of 100 slots are filled on MAX3|x2|Kits|TP|Vip[Viking] right now. Check: players over seven days. Average 1, peak 4. Average at the busiest hour was 2 players, at 11:00 UTC over the last 48 hours.

Server

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

Reading: location. MAX3|x2|Kits|TP|Vip[Viking] gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 78.29.14.210:28215.

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

Reading: MAX3|x2|Kits|TP|Vip[Viking], Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for MAX3|x2|Kits|TP|Vip[Viking]?

Check: fps. Average 49 server fps over the last 48 hours, low of 10. Within range. Reading: 102,726 entities at the highest. That covers buildings, deployables and everything else. Reading: 3,441 MB of memory at the highest. Expect lag when fps falls and entities climb.

What is the uptime on MAX3|x2|Kits|TP|Vip[Viking], and is it online?

MAX3|x2|Kits|TP|Vip[Viking] reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 16 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

How is MAX3|x2|Kits|TP|Vip[Viking] configured, and what rules are in force?

The name carries the rate: 2x gather on MAX3|x2|Kits|TP|Vip[Viking]. Groups stop at 3 players. The label given is trio. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.

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

Size 4,000 and seed 1593250117: the game generates the procedural map on MAX3|x2|Kits|TP|Vip[Viking] from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

How can you get onto MAX3|x2|Kits|TP|Vip[Viking]?

Press F1 in Rust and enter client.connect 78.29.14.210:28215. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. http://viking.gamestores.app/ is where its website sits.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players The server holds 100 slots.
ts3
Group limit Teams are capped at 3.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^w
Weekly Wipe cycle: weekly.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.