This server publishes no banner
Exhibit no. 3,176Acc. 2026.3176
MAX3|x2|Kits|TP|Vip[Viking]
Rust server · in the archive since 13 September 2026
Online 78.29.14.210:28215 checked 9m ago
The timeline
Wipes
Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.
13 Sep Now 17 Sep23:32 24 Sep23:32 1 Oct23:32 · FW 8 Oct23:32 15 Oct23:33 22 Oct23:32 29 Oct23:32 5 Nov19:00 · FW 12 Nov23:32 19 Nov23:32 26 Nov23:32 3 Dec19:00 · FW 10 Dec23:32
a wipe on recordthe monthly force wipeexpectednow, 29 Oct 2026, 13:30 UTCAll times UTC.
The record of each wipe
-
Thu 22 Oct 202623:32 UTC6d ago
- Peak
- 4
- Crowd
- –
- Lasted
- running
- Players before
- 0
-
Thu 15 Oct 202623:33 UTC13d ago
- Peak
- 2
- Crowd
- held half
- Lasted
- 7 days
- Players before
- 0
-
Thu 8 Oct 202623:32 UTC20d ago
- Peak
- 3
- Crowd
- halved by day 2
- Lasted
- 7 days
- Players before
- 0
-
Thu 1 Oct 202623:32 UTC FW27d ago
- Peak
- 5
- Crowd
- halved by day 4
- Lasted
- 7 days
- Players before
- 0
-
Thu 24 Sep 202623:32 UTC34d ago
- Peak
- 5
- Crowd
- halved by day 3
- Lasted
- 7 days
- Players before
- 0
-
Thu 17 Sep 202623:32 UTC41d ago
- Peak
- 8
- Crowd
- halved by day 2
- Lasted
- 7 days
- Players before
- 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.
The rhythm
Wipe schedule
fixed weekdays
Next wipe Thursday 29 October, 23:32 UTC, in 9h. Every Thursday at 23:32 UTC · high confidence
Coming wipes
- 9hThu 29 Oct, 23:32 UTC
- 7d 5hThu 5 Nov, 19:00 UTCFW
- 14d 9hThu 12 Nov, 23:32 UTC
- 21d 9hThu 19 Nov, 23:32 UTC
- 28d 9hThu 26 Nov, 23:32 UTC
- 35d 5hThu 3 Dec, 19:00 UTCFW
- 42d 9hThu 10 Dec, 23:32 UTC
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.
The record
Population, performance and rank
Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
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
Top 14% of all ranked servers, and #234 of the trio servers (top 37%). Ranked on player hours over the last seven days.
Related exhibits
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Visitors' questions about this exhibit
Quick answers
Answered from the figures on this page.
Lists and tags
What do the server tags on MAX3|x2|Kits|TP|Vip[Viking] mean?
You can see the tags MAX3|x2|Kits|TP|Vip[Viking] publishes, read by the game's server browser: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): The server holds 100 slots; ts3 (Group limit): The team cap is 3; v2635 (Protocol): Your game must run protocol 2635 to join; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): No region code is set; ^w (Weekly): Wipes fall every week; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Under Modded: the game is changed by plugins or settings. At the top of this page you also see the current players, the queue and when the world was made, all from the tags.
Which Rust Server History lists and filters include MAX3|x2|Kits|TP|Vip[Viking]?
The Rust Server History lists that feature MAX3|x2|Kits|TP|Vip[Viking] are: 2x Rust servers: the record, Modded Rust servers: the record and Trio Rust servers: the record. These filters on the server list bring it up: 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.
The record
Does MAX3|x2|Kits|TP|Vip[Viking] run smoothly?
Across the last 48 hours it averaged 45 server fps; the low was 10. As many as 102,726 entities were in the world: buildings, deployables and the rest. Memory use peaked at 3,441 MB. Players feel lag when fps drop and the entity count climbs.
Which version of Rust does MAX3|x2|Kits|TP|Vip[Viking] run?
On Linux, MAX3|x2|Kits|TP|Vip[Viking] runs Rust network protocol 2635 and build 168909. Joining requires your game to be on the same protocol; Steam keeps it updated for you.
Is MAX3|x2|Kits|TP|Vip[Viking] online, and how reliable is it?
The live count shows MAX3|x2|Kits|TP|Vip[Viking] online right now. About 12 hours ago is when it last restarted, judged by the uptime it reports. 167 of 168 hours, or 99% of the time, over the last 7 full days. The first sighting by Rust Server History was on 13 September 2026.
Where is MAX3|x2|Kits|TP|Vip[Viking] located?
No region is published by MAX3|x2|Kits|TP|Vip[Viking]. Rust Server History 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.
Wipe log
What does wipe day look like on MAX3|x2|Kits|TP|Vip[Viking]?
At their busiest, its recent wipes drew an average of 3 players. At 38 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 20% of its recent wipes. The fall below half came by day 2.5 in those wipes where it didn't hold.
What is the wipe schedule on MAX3|x2|Kits|TP|Vip[Viking]?
The wipes on MAX3|x2|Kits|TP|Vip[Viking] follow a every Thursday at 23:32 UTC rhythm. On Thursday 29 October at 23:32 UTC its next wipe is due. The world it runs now dates from 6 days 14 hours ago. The tags list a weekly wipe schedule.
Population
How does MAX3|x2|Kits|TP|Vip[Viking] rank against other Rust servers?
The last seven days of player hours place MAX3|x2|Kits|TP|Vip[Viking] at #3,176, among the top 14% of all ranked servers. Ranked against other trio servers, it stands at #234.
How busy is MAX3|x2|Kits|TP|Vip[Viking]?
Against 100 slots, MAX3|x2|Kits|TP|Vip[Viking] records 1 players right now. The seven-day average stands at 1 players; the peak is 4. An average of 2 players at 11:00 UTC made that the busiest hour of the last 48.
Rules and settings
What are the rules and settings on MAX3|x2|Kits|TP|Vip[Viking]?
You can read a 2x gather rate in the name of MAX3|x2|Kits|TP|Vip[Viking]. A group may hold 3 players at most (trio). Under game mode, the entry reads survival, the usual game, with gathering, building and raiding. PvP and raiding are enabled. The server browser lists it under Modded, where plugins or settings change the game. The plugin count is Oxide. VAC from Valve is switched on.
Which map does MAX3|x2|Kits|TP|Vip[Viking] run?
Seed 1593250117, size 4,000: such is the procedural map MAX3|x2|Kits|TP|Vip[Viking] runs, generated by the game. You can look at the map on RustMaps from this page, since one size and seed always give one map.
Joining the server
How do I join MAX3|x2|Kits|TP|Vip[Viking]?
Entering client.connect 78.29.14.210:28215 in the console (F1) connects you to this server. The Launch Rust button on this page does the same: it opens the game via Steam and connects on your behalf. You will find its website at http://viking.gamestores.app/.
The label explained
Server tags
What each tag this server publishes means.
Published as mp100,ptrak,$r?,v2635,^w,gmrust,cs168909,ts3,^o^z
Game
gmrust
mp100
ts3
v2635
cs168909
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.