Online 78.29.14.210:28215 checked 11m ago
MAX3|x2|Kits|TP|Vip[Viking]
Connect
srv = rust.server("78.29.14.210:28216")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 14% of all ranked servers, and #238 of the trio servers (top 38%). Ranked on player hours over the last seven days.
Wipe schedule · fixed weekdays
srv.wipe_schedule()Next wipe Thursday 29 October, 23:32 UTC, in 12h. # Every Thursday at 23:32 UTC · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 12h | Thu 29 Oct, 23:32 UTC | wipe |
| 1 | 7d 8h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 14d 12h | Thu 12 Nov, 23:32 UTC | wipe |
| 3 | 21d 12h | Thu 19 Nov, 23:32 UTC | wipe |
| 4 | 28d 12h | Thu 26 Nov, 23:32 UTC | wipe |
| 5 | 35d 8h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 6 | 42d 12h | Thu 10 Dec, 23:32 UTC | wipe |
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 22 Oct, 23:32 UTC6d ago | 4 | NaN | running | 0 |
| 1 | Thu 15 Oct, 23:33 UTC13d ago | 2 | held half | 7 days | 0 |
| 2 | Thu 8 Oct, 23:32 UTC20d ago | 3 | halved by day 2 | 7 days | 0 |
| 3 | Thu 1 Oct, 23:32 UTC FW27d ago | 5 | halved by day 4 | 7 days | 0 |
| 4 | Thu 24 Sep, 23:32 UTC34d ago | 5 | halved by day 3 | 7 days | 0 |
| 5 | Thu 17 Sep, 23:32 UTC41d 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.
display(srv.map, srv.info())Map
4000 · seed 1593250117- map
- Procedural Map
- size
- 4000
- seed
- 1593250117
Server
srv.info()- 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
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | MIRAGE RUST | SATURDAY SOLO/DUO/TRIO 2x | Wipe 24.10 | EU · trio · 2x · weekly · 256 on average | 27/500 |
| 1 | WARBANDITS.GG EU 2X |Solo/Duo/Trio|X2 JUST FULLWIPED | EU · trio · 2x · weekly · 233 on average | 36/200 |
| 2 | WARBANDITS.GG 2X |Solo/Duo/Trio|X2 JUST FULLWIPED | NA · trio · 2x · weekly · 189 on average | 8/200 |
| 3 | Magic Rust #7 — Modded 2x (Solo/Duo/Trio) | Pyccкий | EU · trio · 2x · weekly · 176 on average | 92/120 |
| 4 | Magic Rust #24 — Vanilla 2x (Solo/Duo/Trio) | Baйп 26.10 | EU · trio · 2x · weekly · 135 on average | 224/300 |
| 5 | MIRAGE RUST | MONDAY SOLO/DUO/TRIO 2x | Wipe 26.10 | EU · trio · 2x · weekly · 133 on average | 91/350 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does MAX3|x2|Kits|TP|Vip[Viking] rank?
Over the last seven days MAX3|x2|Kits|TP|Vip[Viking] sits at #3,213 on player hours, in the top 14% of ranked servers. Within the trio group, its rank is #238.
What population does MAX3|x2|Kits|TP|Vip[Viking] carry?
Current row: 1 players on MAX3|x2|Kits|TP|Vip[Viking], against 100 slots. Over the last seven days it averaged 1 players and peaked at 4. Peak hour in the last 48 hours: 12:00 UTC, mean 2 players.
Server facts
How well does MAX3|x2|Kits|TP|Vip[Viking] perform?
The 48-hour average is 46 server fps, with a low of 10. Buildings, deployables and all else in the world took the count as high as 102,726 entities. Memory peaked at 3,441 MB. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does MAX3|x2|Kits|TP|Vip[Viking] run?
The build is Rust network protocol 2635 and build 168909 on Linux, run by MAX3|x2|Kits|TP|Vip[Viking]. Joining needs the same protocol on your game; Steam handles the update.
How reliable is MAX3|x2|Kits|TP|Vip[Viking], and is it up?
The current sample puts MAX3|x2|Kits|TP|Vip[Viking] online. A restart about 9 hours ago is what its reported uptime implies. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 13 September 2026.
Where does MAX3|x2|Kits|TP|Vip[Viking] sit?
For MAX3|x2|Kits|TP|Vip[Viking], no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 78.29.14.210:28215 is its address.
Settings and map
Which rules apply on MAX3|x2|Kits|TP|Vip[Viking], and what settings?
The name carries the figure: MAX3|x2|Kits|TP|Vip[Viking] runs 2x gather. The group limit is 3 players, the trio setting. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has MAX3|x2|Kits|TP|Vip[Viking] loaded?
Size 4,000, seed 1593250117: the procedural map on MAX3|x2|Kits|TP|Vip[Viking], generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
When does MAX3|x2|Kits|TP|Vip[Viking] wipe, and on what schedule?
every Thursday at 23:32 UTC is how MAX3|x2|Kits|TP|Vip[Viking] wipes. On Thursday 29 October at 23:32 UTC the next wipe is due. This world was created 6 days 11 hours ago. The tags list wipes as weekly.
On MAX3|x2|Kits|TP|Vip[Viking], what happens on wipe day?
The average peak over recent wipes is 3 players. Peak population on the latest wipe came 38 hours in. Recent wipes kept the crowd above half the peak until the next wipe 20% of the time. The drop under half arrived by day 2.5 in the other cases.
Tags and filters
Which lists on Rust Data hold MAX3|x2|Kits|TP|Vip[Viking], and which filters?
The Rust Data lists that MAX3|x2|Kits|TP|Vip[Viking] fits are: Modded Rust servers, 2x Rust servers and Trio Rust servers. 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.
How should you read the server tags on MAX3|x2|Kits|TP|Vip[Viking]?
The game's server browser reads these tags from MAX3|x2|Kits|TP|Vip[Viking]: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): Slot count: 100; ts3 (Group limit): Team size tops out at 3; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^w (Weekly): Wipes run weekly; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to MAX3|x2|Kits|TP|Vip[Viking]?
Enter client.connect 78.29.14.210:28215 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. http://viking.gamestores.app/ is the website recorded for it.