Station XX-2864 · recording
Solo|x2|Kits|TP|Vip[Viking]
Online 78.29.14.210:28115 checked 13m ago
- Players now
- 1/ 100
- 1% full
- Motion · 24 h
- M0.0▼falling
- −1 players on the day
- 7-day average
- 1
- peak 7
- Rank
- #2,864
- top 13%
- Last wipe
- 3d ago
- weekly schedule
- Next wipe
- 3d 20h
- Mon 2 Nov, 00:13 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 100 slots
- Motion · 24 h
- M0.0▼falling−1 players
- Sharpest hour
- −2into Wed 19:00 UTC
- Peak · 48 h
- 4most 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 13% of all ranked servers, and #127 of the solo servers (top 57%). Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdaysNext wipe Monday 2 November, 00:13 UTC, in 3d 20h. Every Monday at 00:13 UTC · high confidence
- usual gap
- 7 daysbetween real wipes
- on rhythm
- 100%of its recent wipes
- wipe-day peak
- 4players, last three wipes
- crowd held
- 80%else halves by day 2
Coming wipes
- 3d 20hMon 2 Nov, 00:13 UTC
- 7d 15hThu 5 Nov, 19:00 UTCFW
- 10d 20hMon 9 Nov, 00:13 UTC
- 17d 20hMon 16 Nov, 00:13 UTC
- 24d 20hMon 23 Nov, 00:13 UTC
- 31d 20hMon 30 Nov, 00:13 UTC
- 35d 15hThu 3 Dec, 19:00 UTCFW
- 38d 20hMon 7 Dec, 00:13 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 |
|---|---|---|---|---|---|---|
| Mon 26 Oct, 00:13 UTC3d ago | M0.6▲rising | 4 | – | running | 0 | |
| Mon 19 Oct, 00:12 UTC10d ago | M0.6▲rising | 4 | held half | 7 days | 0 | |
| Mon 12 Oct, 00:04 UTC17d ago | M0.6▲rising | 4 | held half | 7 days | 0 | |
| Mon 5 Oct, 00:13 UTC24d ago | M0.7▲rising | 5 | held half | 7 days | 0 | |
| Thu 1 Oct, 23:56 UTC FW27d ago | M0.6▲rising | 4 | held half | 3 days | 0 | |
| Mon 28 Sep, 00:04 UTC31d ago | M0.8▲rising | 6 | halved by day 2 | 4 days | 0 | |
| Sun 20 Sep, 23:56 UTC38d ago | M0.6▲rising | 4 | held half | 7 days | 0 | |
| Mon 14 Sep, 00:07 UTC45d ago | M0.6▲rising | 4 | held half | 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 Solo|x2|Kits|TP|Vip[Viking]?
Solo|x2|Kits|TP|Vip[Viking] runs a procedural map of size 4,500 with seed 1607695022, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on Solo|x2|Kits|TP|Vip[Viking]?
2x gather is what Solo|x2|Kits|TP|Vip[Viking] runs, judging by its name. This is a solo-only server, with no teams. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. 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.
Player counts
How many players are recorded on Solo|x2|Kits|TP|Vip[Viking] right now?
A reading taken now shows 1 players on Solo|x2|Kits|TP|Vip[Viking], which has 100 slots. The seven-day average is 1 players, with a peak of 7. The last 48 hours show their highest activity at 14:00 UTC, averaging 3 players.
How does Solo|x2|Kits|TP|Vip[Viking] rank against other Rust servers?
On player hours for the past week, Solo|x2|Kits|TP|Vip[Viking] sits at #2,864, which puts it inside the top 13% of every ranked server. The ranking for solo puts it at #127.
Operator and location
How reliably does Solo|x2|Kits|TP|Vip[Viking] stay online?
As recorded now, Solo|x2|Kits|TP|Vip[Viking] is running. Going by the uptime figure it reports, it restarted about 2 hours ago. It was up 99% of the time across the last 7 full days: 167 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Does Solo|x2|Kits|TP|Vip[Viking] hold a steady tick rate?
Across the last 48 hours it averaged 53 server fps, with a floor of 10. The world held up to 118,177 entities at its peak, buildings and deployables included. It reached a ceiling of 4,361 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Which region does Solo|x2|Kits|TP|Vip[Viking] run from?
A region is not published by Solo|x2|Kits|TP|Vip[Viking]. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 78.29.14.210:28115 is the address it uses.
What build of Rust does Solo|x2|Kits|TP|Vip[Viking] use?
On Linux, Solo|x2|Kits|TP|Vip[Viking] runs Rust network protocol 2635 and build 168909. 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 Solo|x2|Kits|TP|Vip[Viking]?
The recent wipes averaged a busiest count of 4 players. 38 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 80% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 2.
How often does Solo|x2|Kits|TP|Vip[Viking] wipe, and on which days?
every Monday at 00:13 UTC is how Solo|x2|Kits|TP|Vip[Viking] wipes. The date of its next wipe is Monday 2 November at 00:13 UTC. 3 days 3 hours is how long the current world has been running. Its tags state a weekly wipe schedule.
Lists and tags
What do the server tags on Solo|x2|Kits|TP|Vip[Viking] mean?
These are the tags Solo|x2|Kits|TP|Vip[Viking] publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp100 (Max players): Slots: 100; ts1 (Group limit): Each team can hold up to 1; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^w (Weekly): A wipe comes once a week; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Solo|x2|Kits|TP|Vip[Viking] appear?
You will find Solo|x2|Kits|TP|Vip[Viking] on the following Rust Server Trends lists: 2x Rust servers, listed live, Modded Rust servers, tracked live and Solo Rust servers. On the server list, the filters it matches are: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Solo; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x.
Join the server
What steps get you onto Solo|x2|Kits|TP|Vip[Viking]?
You can connect by pressing F1 in Rust and typing client.connect 78.29.14.210:28115 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. You can find its website at http://viking.gamestores.app/.
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.