MAX3|x2|Kits|TP|Vip[Viking]
ruststatistics.org · independent, not affiliated with Facepunch Studios
Online · checked 12m ago · 78.29.14.210:28215
Abstract
We describe the public Rust server MAX3|x2|Kits|TP|Vip[Viking], reached at 78.29.14.210:28215. At the last check it held 1 of 100 places, against a seven-day mean of 1 and a peak of 41. It ranks #3,220 of all servers, the top 14%. It last wiped 6d ago on a published weekly schedule; the next wipe is expected Thursday 29 October, 23:32 UTC, every Thursday at 23:32 UTC.
Keywords2x gather trio weekly wipes modded oxide
1Summary statistics
2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 14% of all ranked servers, and #239 of the trio servers (top 38%). Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule: fixed weekdays
The next wipe is expected Thursday 29 October, 23:32 UTC, in 14h. Every Thursday at 23:32 UTC (high confidence).
| Measure | Value | Note |
|---|---|---|
| Usual gap | 7 days | between real wipes |
| On rhythm | 100% | of its recent wipes |
| Wipe-day peak | 3 | players, last three wipes |
| Crowd held | 20% | else halves by day 2.5 |
| When (UTC) | In | Kind |
|---|---|---|
| Thu 29 Oct, 23:32 | 14h | its own schedule |
| Thu 5 Nov, 19:00 | 7d 9h | force wipefw |
| Thu 12 Nov, 23:32 | 14d 14h | its own schedule |
| Thu 19 Nov, 23:32 | 21d 14h | its own schedule |
| Thu 26 Nov, 23:32 | 28d 14h | its own schedule |
| Thu 3 Dec, 19:00 | 35d 9h | force wipefw |
| Thu 10 Dec, 23:32 | 42d 14h | its own schedule |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Thu 22 Oct, 23:326d ago | 4 | – | running | 0 |
| Thu 15 Oct, 23:3313d ago | 2 | held half | 7 d | 0 |
| Thu 8 Oct, 23:3220d ago | 3 | halved by day 2 | 7 d | 0 |
| Thu 1 Oct, 23:32fw27d ago | 5 | halved by day 4 | 7 d | 0 |
| Thu 24 Sep, 23:3234d ago | 5 | halved by day 3 | 7 d | 0 |
| Thu 17 Sep, 23:3241d ago | 8 | halved by day 2 | 7 d | 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| Address | 78.29.14.210:28215 |
|---|---|
| Region | – |
| Max players | 100 |
| Group limit | trio |
| Wipe schedule | weekly |
| Last wipe | 22 Oct 2026, 23:32 UTC |
| Hostname | – |
| First seen | 13 Sep 2026 |
| Map | Procedural Map |
| Size | 4000 |
| Seed | 1593250117 |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are group limit three servers [2], find a 2x rust server [3], browse modded Rust servers [4] and predicted wipe schedule [5].
| Server | Players |
|---|---|
| MIRAGE RUST | SATURDAY SOLO/DUO/TRIO 2x | Wipe 24.10EU · trio · 2x · weekly · 256 on average | 18/500 |
| WARBANDITS.GG EU 2X |Solo/Duo/Trio|X2 JUST FULLWIPEDEU · trio · 2x · weekly · 233 on average | 31/200 |
| WARBANDITS.GG 2X |Solo/Duo/Trio|X2 JUST FULLWIPEDNA · trio · 2x · weekly · 189 on average | 10/200 |
| Magic Rust #7 — Modded 2x (Solo/Duo/Trio) | PyccкийEU · trio · 2x · weekly · 176 on average | 85/100 |
| Magic Rust #24 — Vanilla 2x (Solo/Duo/Trio) | Baйп 26.10EU · trio · 2x · weekly · 135 on average | 157/300 |
| MIRAGE RUST | MONDAY SOLO/DUO/TRIO 2x | Wipe 26.10EU · trio · 2x · weekly · 133 on average | 78/350 |
Appendix AQuick answers
From the figures on this page.
About the server
A.1Is the performance of MAX3|x2|Kits|TP|Vip[Viking] smooth?
Its average server fps over the last 48 hours was 43, with a minimum of 10. Buildings, deployables and all other world objects counted together reached a maximum of 102,726 entities. The peak memory usage was 3,441 MB. When fps is low and entity count climbs, players feel lag.
A.2In which location is MAX3|x2|Kits|TP|Vip[Viking] based?
A region is not published by MAX3|x2|Kits|TP|Vip[Viking]. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 78.29.14.210:28215 is its address.
A.3What is the online status and reliability of MAX3|x2|Kits|TP|Vip[Viking]?
MAX3|x2|Kits|TP|Vip[Viking] is currently online. The uptime it reports indicates a restart about 8 hours ago. The server was up 99% of the time over the last 7 full days, 167 of 168 hours. Its first appearance in Rust Statistics's records is 13 September 2026.
A.4What version of Rust is run on MAX3|x2|Kits|TP|Vip[Viking]?
The version of Rust on MAX3|x2|Kits|TP|Vip[Viking] is network protocol 2635 and build 168909, and the operating system is Linux. To join, your game must use the same protocol; Steam handles the update for you.
Wipe timing
A.5When are wipes carried out on MAX3|x2|Kits|TP|Vip[Viking]?
MAX3|x2|Kits|TP|Vip[Viking] follows a wipe rhythm of every Thursday at 23:32 UTC. The server is due to wipe on Thursday 29 October at 23:32 UTC. The current world has been running for 6 days 9 hours. The tags state that wipes occur weekly.
A.6How would you describe wipe day on MAX3|x2|Kits|TP|Vip[Viking]?
Recent wipes saw an average peak of 3 players. The peak on the latest wipe came 38 hours after it began. The crowd stayed above half its peak until the next wipe in 20% of recent wipes. In the other cases, the population fell below half by day 2.5.
Player count
A.7What position does MAX3|x2|Kits|TP|Vip[Viking] occupy in the ranking of Rust servers?
The seven-day player-hours ranking puts MAX3|x2|Kits|TP|Vip[Viking] at #3,220, within the top 14% of ranked servers. The trio group places it at #239.
A.8What is the population level of MAX3|x2|Kits|TP|Vip[Viking]?
The current population of MAX3|x2|Kits|TP|Vip[Viking] is 1, drawn from 100 slots. The peak over seven days is 4, against an average of 1. Averaging 2 players, 12:00 UTC was the busiest hour of the past 48.
Tags, lists
A.9What is the meaning of the tags on MAX3|x2|Kits|TP|Vip[Viking]?
gmrust (Game mode): Survival on standard Rust rules; mp100 (Max players): 100 slots are available; ts3 (Group limit): A team holds no more than 3; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set; ^w (Weekly): Wipes happen every week; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded: these are the tags MAX3|x2|Kits|TP|Vip[Viking] publishes, and the server browser reads them. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.
A.10Where can MAX3|x2|Kits|TP|Vip[Viking] be found among the Rust Statistics lists and filters?
The Rust Statistics lists that MAX3|x2|Kits|TP|Vip[Viking] fits are: Rust servers with a 2x gather rate, Modded Rust servers and Rust servers with a group limit of three. These filters on the server list return it: 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.
Rules, settings, map
A.11Which settings and rules are in force on MAX3|x2|Kits|TP|Vip[Viking]?
At 2x gather, MAX3|x2|Kits|TP|Vip[Viking] states its rate in the server name itself. The group limit is 3 players, under trio. Listed as survival, the game mode is gathering, building and raiding, as the game is usually played. Players may raid and fight one another. The server browser lists it as Modded, where plugins or settings alter the game. The plugin count is Oxide. The server has VAC on, Valve's anti-cheat.
A.12On which map does MAX3|x2|Kits|TP|Vip[Viking] take place?
The game generates MAX3|x2|Kits|TP|Vip[Viking]'s procedural map at size 4,000, from seed 1593250117. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.
How to join
A.13What steps are required to join MAX3|x2|Kits|TP|Vip[Viking]?
Enter client.connect 78.29.14.210:28215 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you. You can find its website at http://viking.gamestores.app/.
Appendix BServer tags
What each of the server's tags means. Published as mp100,ptrak,$r?,v2635,^w,gmrust,cs168909,ts3,^o^z.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. Survival on standard Rust rules. |
mp100 | Max players. 100 slots are available. |
ts3 | Group limit. A team holds no more than 3. |
v2635 | Protocol. Joining requires the same game version: protocol 2635. |
cs168909 | Build. The game build is 168909. |
ptrak | Networking. The network layer is RakNet, standard for the game. |
$r? | Region code. A region code has not been set. |
| Wipe schedule | |
^w | Weekly. Wipes happen every week. |
| Mods and access | |
^o | Oxide. The plugin framework in use is Oxide (uMod). |
^z | Modded. The game is altered by plugins or settings, so it is listed as Modded. |
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.
Appendix CAbout this server, in its own words
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Group limit three servers. ruststatistics.org/top-trio-rust-servers.
- [3]Rust Statistics. Find a 2x rust server. ruststatistics.org/top-2x-rust-servers.
- [4]Rust Statistics. Browse modded Rust servers. ruststatistics.org/top-modded-rust-servers.
- [5]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.