MAX3|x2|Kits|TP|Vip[Viking]
Key statistics
the figures behind the quote- Players now
- 0/ 100 0% full
- Change · 24h
- ▪+0 no reading a day ago
- 7-day average
- 0 peak 3
- Rank
- #4,872 top 22%
- Rank · 7d ago
- #4,014 ▼858 places down
- Last wipe
- 6d ago weekly schedule
- Next wipe
- 7d 21h Thu 22 Oct, 23:32 UTC
- Group limit
- trio players per team
- Gather rate
- 2x read from the name
- Score
- 54 player hours, last seven days
- Map
- 4000 Procedural Map · seed 235555252
- First seen
- 13 Sep 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC. Busiest hour of the two days: 1 players.
Daily average and peak, UTC.
Server performance
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 bestTop 22% of all ranked servers, and #331 of the trio servers (top 54%). Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdays- usual gap
- 14 days between real wipes
- on rhythm
- 100% of its recent wipes
- wipe-day peak
- 4 players, last three wipes
- crowd held
- 0% else halves by day 3
Coming wipes
- 7d 21hThu 22 Oct, 23:32 UTC
- 21d 17hThu 5 Nov, 19:00 UTCFW
- 35d 21hThu 19 Nov, 23:32 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 12 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 8 Oct, 23:32 UTC6d ago | 3 | – | running | 0 |
| Thu 1 Oct, 23:32 UTC FW13d ago | 5 | halved by day 4 | 7 days | 0 |
| Thu 24 Sep, 23:32 UTC20d ago | 5 | halved by day 3 | 7 days | 0 |
| Thu 17 Sep, 23:32 UTC27d 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | WARBANDITS.GG EU 2X |Solo/Duo/Trio|X2 JUST FULLWIPEDEU · trio · 2x · weekly · 233 on average | 9/200 | ▼−21−70.1% | |
| 2 | WARBANDITS.GG 2X |Solo/Duo/Trio|X2 JUST FULLWIPEDNA · trio · 2x · weekly · 199 on average | 36/200 | ▼−38−51.6% | |
| 3 | Magic Rust #7 — Modded 2x (Solo/Duo/Trio) | PyccкийEU · trio · 2x · weekly · 106 on average | 7/100 | ▼−3−28.8% | |
| 4 | MIRAGE RUST | SATURDAY SOLO/DUO/TRIO 2x | Wipe 10.10EU · trio · 2x · weekly · 105 on average | 4/350 | ▼−1−20.0% | |
| 5 | [US] Stevious 2x | Solo/Duo/Trio | 10/8NA · trio · 2x · weekly · 92 on average | 27/150 | ▼−7−20.2% | |
| 6 | Magic Rust #24 — Vanilla 2x (Solo/Duo/Trio) | Baйп 12.10EU · trio · 2x · weekly · 88 on average | 33/300 | ▼−16−32.5% |
Quick answers
from the figures on this pageServer Rules
What settings and rules are in place on MAX3|x2|Kits|TP|Vip[Viking]?
MAX3|x2|Kits|TP|Vip[Viking] carries its gather rate in its name: 2x. trio caps groups at 3 players. It runs survival, gather, build and raid in the standard game. Combat and raiding between players are allowed. The server browser lists it as Modded: plugins or settings change the game. Oxide plugins are in use. VAC is active.
Which map is played on MAX3|x2|Kits|TP|Vip[Viking]?
A procedural map of size 4,000 with seed 235555252 runs on MAX3|x2|Kits|TP|Vip[Viking], created by the game. The map is reproducible from its size and seed; RustMaps shows it from this page.
Activity
Where does MAX3|x2|Kits|TP|Vip[Viking] sit in the rankings?
In the top 22% of all ranked servers, MAX3|x2|Kits|TP|Vip[Viking] is #4,872 on player hours over the last seven days. Among servers in trio, it stands at #331.
How many players does MAX3|x2|Kits|TP|Vip[Viking] have?
0 of 100 slots on MAX3|x2|Kits|TP|Vip[Viking] are filled at the moment. The mean over the last seven days is 0 players, reaching 3 at its highest. At 12:00 UTC in the last 48 hours, it averaged 1 players, the busiest hour.
Wipe Frequency
What happens on wipe day at MAX3|x2|Kits|TP|Vip[Viking]?
The average peak across its recent wipes is 4 players. On the latest wipe, 12 hours after the wipe, the crowd peaked. Half the peak was held until the next wipe in 0% of its recent wipes. If it did not hold, by day 3 the crowd dropped below half.
On what cycle does MAX3|x2|Kits|TP|Vip[Viking] wipe?
The wipe rhythm at MAX3|x2|Kits|TP|Vip[Viking] is every other Thursday at 23:32 UTC. On Thursday 22 October at 23:32 UTC the next wipe is due. This world has been running for 6 days 2 hours. Its tags state a wipe every week.
Server Details
Where can MAX3|x2|Kits|TP|Vip[Viking] be found?
There is no region published for MAX3|x2|Kits|TP|Vip[Viking]. Rust Analytics reports the location a server claims, not the machine's actual location. 78.29.14.210:28215 is its address.
How is the performance on MAX3|x2|Kits|TP|Vip[Viking]?
Server fps over the last 48 hours: 18 on average, 10 at the lowest. At its peak it held 92,882 entities: buildings, deployables and the rest of the world. The memory ceiling reached 3,639 MB. Low fps and growing entities are the source of felt lag.
What Rust version is MAX3|x2|Kits|TP|Vip[Viking] running?
The version in use at MAX3|x2|Kits|TP|Vip[Viking]: Rust network protocol 2634 and build 167781, on Linux. The protocol has to match for you to join, and Steam applies that update.
Is MAX3|x2|Kits|TP|Vip[Viking] up, and how consistent is its uptime?
The server is live: MAX3|x2|Kits|TP|Vip[Viking] is online. 37 minutes ago is when it last restarted, judging by the uptime it reports. 100% is its uptime for the last 7 full days, 168 of 168 hours. 13 September 2026 is when Rust Analytics first saw it.
Tags & Filters
How should you interpret the tags on MAX3|x2|Kits|TP|Vip[Viking]?
Published by MAX3|x2|Kits|TP|Vip[Viking] for the game's server browser to read: gmrust (Game mode): Rust's standard survival mode; mp100 (Max players): Capacity: 100 slots; ts3 (Group limit): Teams take no more than 3; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs167781 (Build): Build 167781; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): The region code is absent; ^w (Weekly): Wipes land every week; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): The Modded listing applies: plugins or settings change play. Also in the tags and at the top of this page: current players, queue and world creation time.
Where does MAX3|x2|Kits|TP|Vip[Viking] show up in Rust Analytics lists and filters?
On Rust Analytics, MAX3|x2|Kits|TP|Vip[Viking] matches these lists: 2x Rust servers, Modded Rust servers and Trio Rust servers. 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.
Connection
What is the process to join MAX3|x2|Kits|TP|Vip[Viking]?
The console route: start Rust, press F1, enter client.connect 78.29.14.210:28215. The page's Launch Rust button opens Rust through Steam and connects you instead. You can visit its website at http://viking.gamestores.app/.
Server tags
what each one meansPublished as mp100,ptrak,$r?,v2634,^w,gmrust,cs167781,ts3,^o^z
Game
gmrust
mp100
ts3
v2634
cs167781
ptrak
$r?
Wipe schedule
^w
Mods and access
^o
^z
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.