MAX3|x2|Kits|TP|Vip[Viking]
Online 78.29.14.210:28215 checked 5m ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 14% of all ranked servers, and #232 of the trio servers (top 37%). Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdaysNext wipe Thursday 5 November, 19:00 UTC, in 6d 15h. The force wipe · high confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 6d 15h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 13d 20h | Thu 12 Nov, 23:32 UTC | its own |
| 20d 20h | Thu 19 Nov, 23:32 UTC | its own |
| 27d 20h | Thu 26 Nov, 23:32 UTC | its own |
| 34d 15h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 41d 20h | Thu 10 Dec, 23:32 UTC | its own |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 38 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 29 Oct, 23:32 UTC3h ago | – | – | running | 0 |
| Thu 22 Oct, 23:32 UTC7d ago | 4 | held half | 7 days | 0 |
| Thu 15 Oct, 23:33 UTC14d ago | 2 | held half | 7 days | 0 |
| Thu 8 Oct, 23:32 UTC21d ago | 3 | halved by day 2 | 7 days | 0 |
| Thu 1 Oct, 23:32 UTC FW28d ago | 5 | halved by day 4 | 7 days | 0 |
| Thu 24 Sep, 23:32 UTC35d ago | 5 | halved by day 3 | 7 days | 0 |
| Thu 17 Sep, 23:32 UTC42d 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 | Profile | Players now |
|---|---|---|
| MIRAGE RUST | SATURDAY SOLO/DUO/TRIO 2x | Wipe 24.10 | EU · trio · 2x · weekly · 242 on average | 2 / 500 |
| WARBANDITS.GG EU 2X |Solo/Duo/Trio|X2 JUST FULLWIPED | EU · trio · 2x · weekly · 234 on average | 179 / 250 |
| Magic Rust #7 — Modded 2x (Solo/Duo/Trio) | Pyccкий | EU · trio · 2x · weekly · 181 on average | 7 / 100 |
| WARBANDITS.GG 2X |Solo/Duo/Trio|X2 JUST FULLWIPED | NA · trio · 2x · weekly · 179 on average | 563 / 650 |
| Magic Rust #24 — Vanilla 2x (Solo/Duo/Trio) | Pyccкий | EU · trio · 2x · weekly · 150 on average | 32 / 300 |
| MIRAGE RUST | MONDAY SOLO/DUO/TRIO 2x | Wipe 26.10 | EU · trio · 2x · weekly · 144 on average | 10 / 350 |
Quick answers
from the figures on this pageWipe cycle
When does MAX3|x2|Kits|TP|Vip[Viking] wipe?
MAX3|x2|Kits|TP|Vip[Viking] follows a wipe rhythm of every Thursday at 23:32 UTC. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The current world dates from 3 hours. The tags list a wipe schedule of one week.
On MAX3|x2|Kits|TP|Vip[Viking], what happens on wipe day?
Recent wipes averaged a busiest count of 3 players. Peak population for the latest wipe came 38 hours after it began. The crowd stayed above half that peak until the next wipe in 40% of recent wipes. By day 3 it had fallen below half where the hold failed.
Server
In which region does MAX3|x2|Kits|TP|Vip[Viking] sit?
A region is not published by MAX3|x2|Kits|TP|Vip[Viking]. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. You will find it at 78.29.14.210:28215.
What Rust build does MAX3|x2|Kits|TP|Vip[Viking] run?
Rust network protocol 2635 and build 168909 on Linux is the setup for MAX3|x2|Kits|TP|Vip[Viking]. Your game must match the protocol to join, and Steam applies that update.
How reliable is MAX3|x2|Kits|TP|Vip[Viking], and is it online now?
The current status of MAX3|x2|Kits|TP|Vip[Viking] is online. About 1 hours ago is when it last restarted, judged by its reported uptime. Uptime over the last full days (7) was 99%, or 167 of 168 hours. 13 September 2026 is when Rust Server Analytics first recorded it.
Is performance on MAX3|x2|Kits|TP|Vip[Viking] stable?
Over 48 hours the average held at 45 server fps, and the minimum was 10. Entity count reached 102,726, covering buildings, deployables and the rest of the world. Peak memory was 3,441 MB. Players experience lag as low fps combined with a rising entity count.
Tags
How should the tags on MAX3|x2|Kits|TP|Vip[Viking] be read?
Tags from MAX3|x2|Kits|TP|Vip[Viking], as read by the game's server browser, are: gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): Player slots: 100; ts3 (Group limit): The cap is 3 players per team; v2635 (Protocol): Joining needs your game on protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): The region code is blank; ^w (Weekly): Wipes run on a weekly cycle; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section, because plugins or settings modify play. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.
Where does MAX3|x2|Kits|TP|Vip[Viking] appear across Rust Server Analytics's lists and filters?
Among the Rust Server Analytics lists MAX3|x2|Kits|TP|Vip[Viking] fits are: Rust servers with a 2x gather rate, Modded Rust servers: live data and Trio Rust servers, live. On the server list, the filters that return it are: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last 24 hours; Gather rate: 2x.
Player numbers
What position does MAX3|x2|Kits|TP|Vip[Viking] hold in the server rankings?
Player hours for the last seven days place MAX3|x2|Kits|TP|Vip[Viking] at #3,120, in the top 14% of the ranked field. The trio segment places it at #232.
At what level does MAX3|x2|Kits|TP|Vip[Viking] run its population?
MAX3|x2|Kits|TP|Vip[Viking] holds 0 players of its 100 slots as of the latest update. Seven-day figures: an average of 1 players and a peak of 4. Across the last 48 hours, 11:00 UTC shows the highest average: 2 players.
Settings
How is MAX3|x2|Kits|TP|Vip[Viking] configured, and what rules apply?
MAX3|x2|Kits|TP|Vip[Viking] names a 2x gather rate. A maximum of 3 players per group is set (trio). It runs survival, the standard game: gather, build, raid. Raiding and PvP combat are available. In the server browser it sits under Modded, where plugins or settings alter the game. Plugins from Oxide are in use. Anti-cheat status: VAC on.
What is the map for MAX3|x2|Kits|TP|Vip[Viking]?
A procedural map of size 4,000 with seed 328147289, generated by the game, runs on MAX3|x2|Kits|TP|Vip[Viking]. The map is reproducible from its size and seed and can be seen on RustMaps from here.
How to join
What is the way onto MAX3|x2|Kits|TP|Vip[Viking]?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 78.29.14.210:28215. http://viking.gamestores.app/ is its website.