Station XX-3256 · recording
MAX3|x2|Kits|TP|Vip[Viking]
Online 78.29.14.210:28215 checked 9m ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 1
- peak 4
- Rank
- #3,256
- top 15%
- Last wipe
- 6d ago
- weekly schedule
- Next wipe
- 20h
- Thu 29 Oct, 23:32 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- +1into Tue 11:00 UTC
- Peak · 48 h
- 3most players in any hour
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
daily · 1 is bestTop 15% of all ranked servers, and #239 of the trio servers (top 38%). Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdaysNext wipe Thursday 29 October, 23:32 UTC, in 20h. Every Thursday at 23:32 UTC · high confidence
- usual gap
- 7 daysbetween real wipes
- on rhythm
- 100%of its recent wipes
- wipe-day peak
- 3players, last three wipes
- crowd held
- 20%else halves by day 2.5
Coming wipes
- 20hThu 29 Oct, 23:32 UTC
- 7d 15hThu 5 Nov, 19:00 UTCFW
- 14d 20hThu 12 Nov, 23:32 UTC
- 21d 20hThu 19 Nov, 23:32 UTC
- 28d 20hThu 26 Nov, 23:32 UTC
- 35d 15hThu 3 Dec, 19:00 UTCFW
- 42d 20hThu 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.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 22 Oct, 23:32 UTC6d ago | M0.6▲rising | 4 | – | running | 0 | |
| Thu 15 Oct, 23:33 UTC13d ago | M0.3▲rising | 2 | held half | 7 days | 0 | |
| Thu 8 Oct, 23:32 UTC20d ago | M0.5▲rising | 3 | halved by day 2 | 7 days | 0 | |
| Thu 1 Oct, 23:32 UTC FW27d ago | M0.7▲rising | 5 | halved by day 4 | 7 days | 0 | |
| Thu 24 Sep, 23:32 UTC34d ago | M0.7▲rising | 5 | halved by day 3 | 7 days | 0 | |
| Thu 17 Sep, 23:32 UTC41d ago | M0.9▲rising | 8 | halved by day 2 | 7 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on MAX3|x2|Kits|TP|Vip[Viking]?
MAX3|x2|Kits|TP|Vip[Viking] runs a procedural map of size 4,000 with seed 1593250117, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on MAX3|x2|Kits|TP|Vip[Viking]?
2x gather is what MAX3|x2|Kits|TP|Vip[Viking] runs, judging by its name. You can have up to 3 players in a group (trio). It plays in survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.
Population
What is the current population on MAX3|x2|Kits|TP|Vip[Viking]?
0 of the 100 slots on MAX3|x2|Kits|TP|Vip[Viking] are filled right now. Averaged across the last seven days the population was 1 players, reaching a peak of 4. The last 48 hours show their highest activity at 12:00 UTC, averaging 2 players.
How does MAX3|x2|Kits|TP|Vip[Viking] rank against other Rust servers?
Over the last seven days, MAX3|x2|Kits|TP|Vip[Viking] recorded enough player hours to reach #3,256 worldwide, placing it in the top 15% of all ranked servers. It sits at #239 among trio servers.
Server details
How reliably does MAX3|x2|Kits|TP|Vip[Viking] stay online?
Right now, you can reach MAX3|x2|Kits|TP|Vip[Viking]. Its reported uptime points to a restart about 1 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
How well does MAX3|x2|Kits|TP|Vip[Viking] perform under load?
Its average server fps over the last 48 hours was 50, and it never dropped below 10. Buildings, deployables and all the rest of the world's entities brought it to a high of 102,726. It reached a ceiling of 3,441 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Where in the world is MAX3|x2|Kits|TP|Vip[Viking] hosted?
A region is not published by MAX3|x2|Kits|TP|Vip[Viking]. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 78.29.14.210:28215 is the address it uses.
What build of Rust does MAX3|x2|Kits|TP|Vip[Viking] use?
MAX3|x2|Kits|TP|Vip[Viking] is running Rust network protocol 2635 and build 168909 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
What does wipe day look like on MAX3|x2|Kits|TP|Vip[Viking]?
The recent wipes averaged a busiest count of 3 players. 38 hours into the latest wipe, the crowd reached its peak. Until the next wipe the crowd remained above half that peak in 20% of its recent wipes. By day 2.5 it fell below half in the wipes where it didn't hold.
On what timetable does MAX3|x2|Kits|TP|Vip[Viking] run its wipes?
every Thursday at 23:32 UTC is how MAX3|x2|Kits|TP|Vip[Viking] wipes. The date of its next wipe is Thursday 29 October at 23:32 UTC. The present world dates from 6 days 3 hours. A weekly wipe schedule is published in its tags.
Server tags
What do the server tags on MAX3|x2|Kits|TP|Vip[Viking] mean?
These are the tags MAX3|x2|Kits|TP|Vip[Viking] publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): 100 slots are available; ts3 (Group limit): The team limit is 3; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^w (Weekly): A wipe comes once a week; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does MAX3|x2|Kits|TP|Vip[Viking] appear?
You will find MAX3|x2|Kits|TP|Vip[Viking] on the following Rust Server Trends lists: 2x Rust servers, listed live, Modded Rust servers, tracked live and Best trio Rust servers. These filters bring it up 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.
Connecting
How do you connect to MAX3|x2|Kits|TP|Vip[Viking]?
To join, enter client.connect 78.29.14.210:28215 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. http://viking.gamestores.app/ is where its website lives.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.