Solo|x2|Kits|TP|Vip[Viking]
Online 78.29.14.210:28115 checked 7m ago
Server instruments
last reading Thu 17:00 UTCPlayers now
2% full 7-day avg7-day peakServer fps
48 h low 10 · below 20 is lag, below 10 is badEntities
48 h range 103,521–118,177 · memory 4,327 MBUptime
17 h 14 min since its last restart, at the last readingPlayers
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 12% of all ranked servers, and #122 of the solo servers (top 55%). Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdaysNext wipe Monday 2 November, 00:13 UTC, in 3d 5h. Every Monday at 00:13 UTC · high confidence
Coming wipes
- WPT 1Mon 2 Nov, 00:13 UTC3d 5h
- WPT 2Thu 5 Nov, 19:00 UTC7d 0hFW
- WPT 3Mon 9 Nov, 00:13 UTC10d 5h
- WPT 4Mon 16 Nov, 00:13 UTC17d 5h
- WPT 5Mon 23 Nov, 00:13 UTC24d 5h
- WPT 6Mon 30 Nov, 00:13 UTC31d 5h
- WPT 7Thu 3 Dec, 19:00 UTC35d 0hFW
- WPT 8Mon 7 Dec, 00:13 UTC38d 5h
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 | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 26 Oct, 00:13 UTC3d ago | 4 | – | running | 0 |
| Mon 19 Oct, 00:12 UTC10d ago | 4 | held half | 7 days | 0 |
| Mon 12 Oct, 00:04 UTC17d ago | 4 | held half | 7 days | 0 |
| Mon 5 Oct, 00:13 UTC24d ago | 5 | held half | 7 days | 0 |
| Thu 1 Oct, 23:56 UTC FW27d ago | 4 | held half | 3 days | 0 |
| Mon 28 Sep, 00:04 UTC31d ago | 6 | halved by day 2 | 4 days | 0 |
| Sun 20 Sep, 23:56 UTC38d ago | 4 | held half | 7 days | 0 |
| Mon 14 Sep, 00:07 UTC45d 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- 27/100
- 34/200
- 40/200
- 25/200
- 37/100
- 12/200
Quick answers
from the figures on this pageWipe schedule
What happens on Solo|x2|Kits|TP|Vip[Viking] when wipe day comes?
The busiest point of its recent wipes drew 4 players on average. Peak crowd on the latest wipe: 38 hours in. The crowd stayed above half that peak until the next wipe in 80% of its recent wipes. When it didn't hold, by day 2 it fell below half.
How often does Solo|x2|Kits|TP|Vip[Viking] wipe, and when?
The wipe rhythm of Solo|x2|Kits|TP|Vip[Viking] is every Monday at 00:13 UTC. Monday 2 November at 00:13 UTC is when its next wipe is due. 3 days 18 hours ago the current world was made. The tags state a wipe schedule of one wipe a week.
Tag meanings
How should you read the tags on Solo|x2|Kits|TP|Vip[Viking]?
Tags published by Solo|x2|Kits|TP|Vip[Viking], read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): 100 slots in total; ts1 (Group limit): You may team up with at most 1; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^w (Weekly): Check: wipe cycle. Every week; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show Solo|x2|Kits|TP|Vip[Viking]?
On Rust Metrics, Solo|x2|Kits|TP|Vip[Viking] sits in these lists: 2x Rust servers, checked live, Modded Rust servers, checked live and Solo-only 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 week; Gather rate: 2x.
Player count
Where does Solo|x2|Kits|TP|Vip[Viking] sit in the rankings?
Ranking for Solo|x2|Kits|TP|Vip[Viking]: #2,714 on seven-day player hours, top 12% of all ranked servers. Among servers in solo, it stands at #122.
What is the population on Solo|x2|Kits|TP|Vip[Viking]?
Current headcount on Solo|x2|Kits|TP|Vip[Viking]: 2 players, 100 slots available. Seven-day check: 1 players on average. Peak reading: 7. Check: 48-hour peak. 14:00 UTC, 4 players on average.
Operator and location
Where does Solo|x2|Kits|TP|Vip[Viking] sit?
No region comes from Solo|x2|Kits|TP|Vip[Viking]. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 78.29.14.210:28115.
What Rust version is Solo|x2|Kits|TP|Vip[Viking] on?
Reading: Solo|x2|Kits|TP|Vip[Viking], Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.
Is performance on Solo|x2|Kits|TP|Vip[Viking] within range?
Check: fps. Average 51 server fps over the last 48 hours, low of 10. Within range. Reading: 118,177 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 4,361 MB. What players call lag comes from low fps and an entity count on the rise.
How reliable is Solo|x2|Kits|TP|Vip[Viking], and is it online now?
Reading: online. Solo|x2|Kits|TP|Vip[Viking] answers right now. Check: restart. The uptime it reports puts the last restart about 17 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.
Rules and settings
What settings and rules apply on Solo|x2|Kits|TP|Vip[Viking]?
The name carries the rate: 2x gather on Solo|x2|Kits|TP|Vip[Viking]. Check: teams. Solo only — no teams. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on Solo|x2|Kits|TP|Vip[Viking]?
Check: map. Procedural, size 4,500, seed 1607695022, generated by the game on Solo|x2|Kits|TP|Vip[Viking]. The map repeats when size and seed match. Open it on RustMaps from this page.
Connection
What do you do to join Solo|x2|Kits|TP|Vip[Viking]?
Press F1 in Rust and enter client.connect 78.29.14.210:28115. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. http://viking.gamestores.app/ is where its website sits.