Solo|x2|Kits|TP|Vip[Viking]
Key statistics
the figures behind the quote- Players now
- 4/ 100 4% full
- Change · 24h
- ▲+3 +182.4% from 1
- 7-day average
- 1 peak 4
- Rank
- #3,425 top 15%
- Rank · 7d ago
- #3,765 ▲340 places up
- Last wipe
- 2d ago weekly schedule
- Next wipe
- 4d 7h Mon 19 Oct, 00:04 UTC
- Group limit
- solo players per team
- Gather rate
- 2x read from the name
- Score
- 150 player hours, last seven days
- Map
- 4500 Procedural Map · seed 406166594
- First seen
- 13 Sep 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC. Busiest hour of the two days: 4 players.
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 #129 of the solo servers (top 58%). Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdays- usual gap
- 7 days between real wipes
- on rhythm
- 100% of its recent wipes
- wipe-day peak
- 4 players, last three wipes
- crowd held
- 80% else halves by day 2
Coming wipes
- 4d 7hMon 19 Oct, 00:04 UTC
- 11d 7hMon 26 Oct, 00:04 UTC
- 18d 7hMon 2 Nov, 00:04 UTC
- 22d 2hThu 5 Nov, 19:00 UTCFW
- 25d 7hMon 9 Nov, 00:04 UTC
- 32d 7hMon 16 Nov, 00:04 UTC
- 39d 7hMon 23 Nov, 00:04 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 16 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 12 Oct, 00:04 UTC2d ago | 4 | – | running | 0 |
| Mon 5 Oct, 00:13 UTC9d ago | 5 | held half | 7 days | 0 |
| Thu 1 Oct, 23:56 UTC FW12d ago | 4 | held half | 3 days | 0 |
| Mon 28 Sep, 00:04 UTC16d ago | 6 | halved by day 2 | 4 days | 0 |
| Sun 20 Sep, 23:56 UTC23d ago | 4 | held half | 7 days | 0 |
| Mon 14 Sep, 00:07 UTC30d ago | 4 | held half | 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
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | Magic Rust #1 — Modded 2x (Только SOLO) | PyccкийEU · solo · 2x · weekly · 60 on average | 50/100 | ▼−3−5.5% | |
| 2 | WARBANDITS.GG EU 2X SOLO ONLY|Loot+|X2 JUST WIPEDEU · solo · 2x · weekly · 53 on average | 153/200 | ▼−81−34.7% | |
| 3 | Blood Rust - Purple [solo, x2]EU · solo · 2x · weekly · 45 on average | 43/200 | ▼−11−19.9% | |
| 4 | WARBANDITS.GG 2X SOLO ONLY|Loot+|X2 JUST WIPEDNA · solo · 2x · weekly · 44 on average | 53/175 | ▲+36+219.6% | |
| 5 | EU Limitless 2x Solo Only | No BP Wipes|Noob Friendly|x2|Max 1EU · solo · 2x · weekly · 25 on average | 17/200 | ▼−10−37.6% | |
| 6 | Magic Rust #16 — Modded 2x (Toлькo SOLO) | Baйп 12.10EU · solo · 2x · weekly · 24 on average | 27/100 | ▼−50−64.8% |
Quick answers
from the figures on this pageMap and Rules
How is Solo|x2|Kits|TP|Vip[Viking] configured in terms of rules and settings?
Solo|x2|Kits|TP|Vip[Viking] carries its gather rate in its name: 2x. No teams: solo only. It runs survival, gather, build and raid in the standard game. Combat and raiding between players are allowed. In the server browser it appears under Modded, with plugins or settings that change the game. Plugin count: Oxide. VAC is active.
Which map is played on Solo|x2|Kits|TP|Vip[Viking]?
A procedural map of size 4,500 with seed 406166594 runs on Solo|x2|Kits|TP|Vip[Viking], created by the game. The map is reproducible from its size and seed; RustMaps shows it from this page.
Activity
Where does Solo|x2|Kits|TP|Vip[Viking] sit in the rankings?
In the top 15% of all ranked servers, Solo|x2|Kits|TP|Vip[Viking] is #3,425 on player hours over the last seven days. Among servers in solo, it stands at #129.
What is the population on Solo|x2|Kits|TP|Vip[Viking]?
On Solo|x2|Kits|TP|Vip[Viking], 4 players are in now, out of 100 slots. Average players over seven days: 1; peak: 4. At 14:00 UTC in the last 48 hours, it averaged 3 players, the busiest hour.
Wipe Frequency
How does Solo|x2|Kits|TP|Vip[Viking] handle wipe day?
The average peak across its recent wipes is 4 players. On the latest wipe, 16 hours after the wipe, the crowd peaked. Half the peak was held until the next wipe in 80% of its recent wipes. Below half by day 2 is where the crowd fell when it did not hold.
When does Solo|x2|Kits|TP|Vip[Viking] schedule its wipes?
Solo|x2|Kits|TP|Vip[Viking] wipes on this rhythm: every Monday at 00:04 UTC. On Monday 19 October at 00:04 UTC the next wipe is due. Its world now is 2 days 16 hours old. The tags give a weekly wipe.
Server Details
What is the location of Solo|x2|Kits|TP|Vip[Viking]?
For Solo|x2|Kits|TP|Vip[Viking], no region is published. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. You can reach it at 78.29.14.210:28115.
Is Solo|x2|Kits|TP|Vip[Viking] performing well?
Average server fps for the last 48 hours is 46; the floor was 10. At its peak it held 122,844 entities: buildings, deployables and the rest of the world. Memory use peaked at 4,414 MB. What players feel as lag is low fps together with a rising entity count.
Solo|x2|Kits|TP|Vip[Viking] is on which Rust version?
The build is Rust network protocol 2634 and build 167781 on Linux, running on Solo|x2|Kits|TP|Vip[Viking]. Joining requires the same protocol on your game, which Steam updates.
What is the uptime and reliability of Solo|x2|Kits|TP|Vip[Viking]?
Online at this moment: Solo|x2|Kits|TP|Vip[Viking]. Its own uptime figure dates the last restart to roughly 14 hours ago. The last 7 full days give 100% uptime, 168 hours on out of 168. 13 September 2026 is when Rust Analytics first saw it.
Tags & Filters
How should you interpret the tags on Solo|x2|Kits|TP|Vip[Viking]?
The game's server browser reads gmrust (Game mode): Rust's standard survival mode; mp100 (Max players): It holds 100 slots; ts1 (Group limit): 1 is the maximum team size; v2634 (Protocol): To join, your game needs protocol 2634; cs167781 (Build): Game build: 167781; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): The region code is absent; ^w (Weekly): Wipes land every week; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): The Modded listing applies: plugins or settings change play, which Solo|x2|Kits|TP|Vip[Viking] publishes. The tags also carry its current players, queue and world creation time; this page shows them at the top.
Solo|x2|Kits|TP|Vip[Viking] appears in which of the lists and filters on Rust Analytics?
On Rust Analytics, Solo|x2|Kits|TP|Vip[Viking] matches these lists: 2x Rust servers, Modded Rust servers and Solo Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Solo; Wipe schedule: Weekly; Last wipe: In the last 3 days; Gather rate: 2x.
How to Join
What is the process to join Solo|x2|Kits|TP|Vip[Viking]?
Type client.connect 78.29.14.210:28115 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you. You can visit its website at http://viking.gamestores.app/.
Server tags
what each one meansPublished as mp100,ptrak,$r?,v2634,^w,gmrust,cs167781,ts1,^o^z
Game
gmrust
mp100
ts1
v2634
cs167781
ptrak
$r?
Wipe schedule
^w
Mods and access
^o
^z
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.