MAX3|x2|Kits|TP|Vip[Viking]
78.29.14.210:28215 checked 11m ago
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 22% of all ranked servers, and #331 of the trio servers (top 54%). Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 22 October, 23:32 UTC, in 7d 17h. Every other Thursday at 23:32 UTC · medium confidence
- 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 17hThu 22 Oct, 23:32 UTC
- 21d 13hThu 5 Nov, 19:00 UTCFW
- 35d 17hThu 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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 8 Oct, 23:32 UTC 6d ago | 3 | – | running | 0 |
| Thu 1 Oct, 23:32 UTCFW 13d ago | 5 | halved by day 4 | 7 days | 0 |
| Thu 24 Sep, 23:32 UTC 20d ago | 5 | halved by day 3 | 7 days | 0 |
| Thu 17 Sep, 23:32 UTC 27d 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
Quick answers
Player Count
MAX3|x2|Kits|TP|Vip[Viking] ranking: what position does it hold?
Rank #4,868 over the last seven days in player hours: MAX3|x2|Kits|TP|Vip[Viking], inside the top 22% of ranked servers. In the trio category, its position is #331.
How many players are on MAX3|x2|Kits|TP|Vip[Viking]?
The current player count for MAX3|x2|Kits|TP|Vip[Viking] is 0, out of 100 slots. Averaged across the last seven days: 0 players, peaking at 3. Over the last 48 hours, the peak hour was 12:00 UTC, averaging 1 players.
Server Tags
How should the tags on MAX3|x2|Kits|TP|Vip[Viking] be interpreted?
The game's server browser reads these tags from MAX3|x2|Kits|TP|Vip[Viking]: gmrust (Game mode): Standard survival gameplay; mp100 (Max players): Slots: 100; ts3 (Group limit): Team size is capped at 3; v2634 (Protocol): Your game must be on protocol 2634 to connect; cs167781 (Build): Running build 167781; ptrak (Networking): RakNet is the network layer in use; $r? (Region code): No region code listed; ^w (Weekly): Wipe cycle: weekly; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Under Modded, because plugins or settings modify play. At the top of this page you also see its players now, its queue and when its world was made, taken from the tags.
Where does MAX3|x2|Kits|TP|Vip[Viking] appear in BestRustServers.xyz lists and filters?
The BestRustServers.xyz lists that include MAX3|x2|Kits|TP|Vip[Viking] are: Rust servers with 2x gather rate, Best modded Rust servers and Trio servers (group limit 3). It appears under these filters 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.
Server Information
What Rust version is MAX3|x2|Kits|TP|Vip[Viking] on?
On Linux, MAX3|x2|Kits|TP|Vip[Viking] runs Rust network protocol 2634 and build 167781. Steam updates your game automatically, but it needs to match the protocol to join.
Is the performance on MAX3|x2|Kits|TP|Vip[Viking] smooth?
For the past 48 hours, server fps averaged 18, never dropping below 10. Buildings, deployables and the rest of the world accounted for up to 92,882 entities. The maximum memory used was 3,639 MB. What players experience as lag is low fps combined with a rising entity count.
MAX3|x2|Kits|TP|Vip[Viking] uptime and reliability: what are they?
At the moment, MAX3|x2|Kits|TP|Vip[Viking] is up. The uptime it reports shows a restart roughly 4 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. It was first seen by BestRustServers.xyz on 13 September 2026.
MAX3|x2|Kits|TP|Vip[Viking] location: where is it?
No region is given by MAX3|x2|Kits|TP|Vip[Viking]. BestRustServers.xyz does not look up where the machine stands; it shows where a server says it is. 78.29.14.210:28215 is its address.
Rules & Map
What is the map on MAX3|x2|Kits|TP|Vip[Viking]?
On MAX3|x2|Kits|TP|Vip[Viking], the map is procedural, size 4,000 with seed 235555252, generated by the game. On RustMaps, from this page, the same size and seed show the same map.
What rules and configuration does MAX3|x2|Kits|TP|Vip[Viking] have?
2x gather: that is the rate MAX3|x2|Kits|TP|Vip[Viking] states in its name. A group of 3 players is the maximum, given as trio. Listed as survival, gather, build, raid: the standard game. Raids and PvP are on. Plugins or settings change the game, so it appears under Modded. Plugins in use: Oxide. The server has VAC on.
Wipe Cycle
When does MAX3|x2|Kits|TP|Vip[Viking] wipe?
MAX3|x2|Kits|TP|Vip[Viking] follows a wipe rhythm of every other Thursday at 23:32 UTC. Due next is a wipe on Thursday 22 October at 23:32 UTC. Its world dates from 6 days 6 hours. The tags state a weekly wipe cycle.
On MAX3|x2|Kits|TP|Vip[Viking], what occurs on wipe day?
The average busiest point of its recent wipes was 4 players. 12 hours after the latest wipe, the crowd hit its peak. The crowd held above half the peak until the next wipe in 0% of recent wipes. In the wipes where it did not hold, half the peak was lost by day 3.
Connect
MAX3|x2|Kits|TP|Vip[Viking] joining: how is it done?
To connect, type client.connect 78.29.14.210:28215 in the F1 console. Launch Rust on this page opens Rust through Steam and joins you. http://viking.gamestores.app/ is its website.
Server tags
Published as mp100,ptrak,$r?,v2634,^w,gmrust,cs167781,ts3,^o^z
Game
gmrust- Game mode Standard survival gameplay.
mp100- Max players Slots: 100.
ts3- Group limit Team size is capped at 3.
v2634- Protocol Your game must be on protocol 2634 to connect.
cs167781- Build Running build 167781.
ptrak- Networking RakNet is the network layer in use.
$r?- Region code No region code listed.
Wipe schedule
^w- Weekly Wipe cycle: weekly.
Mods and access
^o- Oxide Oxide (uMod) provides the plugin framework here.
^z- Modded Under Modded, because plugins or settings modify play.
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.