Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO E SRV11,622online PAX31,880playing OCC2,774with players WIPED 3H73
MODModded traffic
Callsign

KTS2854=

Solo|x2|Kits|TP|Vip[Viking]

Online 78.29.14.210:28115 checked 12m ago

2x solo weekly wipes moddedoxide
Clearance · join
Players now 0/ 100 0% full
7-day average1peak 7
Rank#2,854top 13%
Last wipe3d agoweekly schedule
Next wipe3d 18hMon 2 Nov, 00:13 UTC
Track history

Players

AveragePeak
0123406:0015:0000:0009:0019:0004:00

Hourly average and peak, UTC.

Server performance

025507510006:0015:0000:0009:0019:0004:00

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
RankRank in region
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 13% of all ranked servers, and #127 of the solo servers (top 57%). Ranked on player hours over the last seven days.

Flight plan

Wipe schedule

fixed weekdays
ETD · next wipe

Next wipe Monday 2 November, 00:13 UTC, in 3d 18h.

Every Monday at 00:13 UTC · high confidence

usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak4players, last three wipes
crowd held80%else halves by day 2

Coming wipes

  1. 3d 18hMon 2 Nov, 00:13 UTC
  2. 7d 13hThu 5 Nov, 19:00 UTCFW
  3. 10d 18hMon 9 Nov, 00:13 UTC
  4. 17d 18hMon 16 Nov, 00:13 UTC
  5. 24d 18hMon 23 Nov, 00:13 UTC
  6. 31d 18hMon 30 Nov, 00:13 UTC
  7. 35d 13hThu 3 Dec, 19:00 UTCFW
  8. 38d 18hMon 7 Dec, 00:13 UTC

The first 48 hours of its last wipes

Mon 26 OctMon 19 OctMon 12 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 4, 38 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign MGC010EU · solo · 2x · weekly · 71 on average Magic Rust #1 — Modded 2x (Только SOLO) | Pyccкий
    Players 8/100
  2. 02MOD
    Callsign WRB015EU · solo · 2x · weekly · 65 on average WARBANDITS.GG EU 2X SOLO ONLY|Loot+|X2 JUST WIPED
    Players 14/200
  3. 03MOD
    Callsign BLD501EU · solo · 2x · weekly · 53 on average Blood Rust - Purple [solo, x2]
    Players 15/200
  4. 04MOD
    Callsign WRB015NA · solo · 2x · weekly · 47 on average WARBANDITS.GG 2X SOLO ONLY|Loot+|X2 JUST WIPED
    Players 23/200
  5. 05MOD
    Callsign MGC010EU · solo · 2x · weekly · 43 on average Magic Rust #16 — Modded 2x (Toлькo SOLO) | Baйп 26.10
    Players 15/100
  6. 06MOD
    Callsign LMT015EU · solo · 2x · weekly · 29 on average EU Limitless 2x Solo Only | No BP Wipes|Noob Friendly|x2|Max 1
    Players 3/200
ATIS · this server

Quick answers

From the figures on this page.

Filters

Which lists and filters on Rust Tracker show Solo|x2|Kits|TP|Vip[Viking]?

These Rust Tracker lists carry Solo|x2|Kits|TP|Vip[Viking]: 2x Rust servers, tracked live, Modded servers, tracked live and Solo Rust servers, tracked live. These filters surface it 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.

How should you read the tags on Solo|x2|Kits|TP|Vip[Viking]?

Listed for the server browser to read, Solo|x2|Kits|TP|Vip[Viking] publishes these tags: gmrust (Game mode): Rust survival, standard mode; mp100 (Max players): Capacity: 100 slots; ts1 (Group limit): No team may exceed 1; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): The region code is unset; ^w (Weekly): Every week it wipes; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; listed under Modded. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.

Wipe Times

What happens on Solo|x2|Kits|TP|Vip[Viking] on wipe day?

Recent wipes averaged a peak of 4 players. The peak on the latest wipe came 38 hours after it. Half the peak was held until the next wipe in 80% of its recent wipes. In the other cases, half the peak was lost by day 2.

Which wipe times are confirmed for Solo|x2|Kits|TP|Vip[Viking]?

Wipe rhythm at Solo|x2|Kits|TP|Vip[Viking]: every Monday at 00:13 UTC. Due on Monday 2 November at 00:13 UTC: its next wipe. Its world went live 3 days 5 hours. Tags list a weekly wipe schedule.

Location and Status

Is Solo|x2|Kits|TP|Vip[Viking] up, and how does its uptime hold?

Right now Solo|x2|Kits|TP|Vip[Viking] is online. By its own uptime figure, the last restart was roughly 4 hours ago. 167 of 168 hours up over the last 7 full days: 99% uptime. The first sighting by Rust Tracker was 13 September 2026.

What Rust version is Solo|x2|Kits|TP|Vip[Viking] on?

Rust network protocol 2635 and build 168909 is the build on Solo|x2|Kits|TP|Vip[Viking]; the platform is Linux. Steam updates it for you; your game must share the protocol to join.

How smoothly does Solo|x2|Kits|TP|Vip[Viking] run?

Server fps held an average of 53 across the last 48 hours, never below 10. Peak entity count: 118,177, covering buildings, deployables and all else in the world. It drew as much as 4,361 MB of memory. A climbing entity count and low fps are what register as lag for players.

Which location is Solo|x2|Kits|TP|Vip[Viking] in?

No region is published by Solo|x2|Kits|TP|Vip[Viking]. Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 78.29.14.210:28115.

Population

What is the player count on Solo|x2|Kits|TP|Vip[Viking]?

Slots 100; players on board 0: that is Solo|x2|Kits|TP|Vip[Viking] now. Seven-day average 1 players; peak 7. Peak traffic in the last 48 hours came at 14:00 UTC, averaging 3 players.

Where does Solo|x2|Kits|TP|Vip[Viking] sit in the server rankings?

On player hours over seven days, Solo|x2|Kits|TP|Vip[Viking] ranks #2,854, inside the top 13% of all ranked servers. Position #127 among solo servers.

Settings

Which settings and rules are confirmed on Solo|x2|Kits|TP|Vip[Viking]?

Going by its name, Solo|x2|Kits|TP|Vip[Viking] runs 2x gather. One player per side: solo only, no teams. It runs survival, gather, build, raid, as the game intends. Raiding and PvP are permitted between players. The server browser lists it under Modded, where plugins or settings change the game. Plugins on it: Oxide. VAC is on, Valve's anti-cheat.

Which map is loaded on Solo|x2|Kits|TP|Vip[Viking]?

A procedural map of size 4,500 runs on Solo|x2|Kits|TP|Vip[Viking], generated by the game from seed 1607695022. Same size, same seed, same map. RustMaps shows it, linked from this page.

Connect

What is the way to join Solo|x2|Kits|TP|Vip[Viking]?

To connect: start Rust, press F1, enter client.connect 78.29.14.210:28115 in the console. Or use Launch Rust on this page to open Rust through Steam and join. For the website, go to http://viking.gamestores.app/.

Transponder codes

Server tags

What each one means.

Published as mp100,ptrak,$r?,v2635,^w,gmrust,cs168909,ts1,^o^z

Game

gmrust
Game mode Rust survival, standard mode.
mp100
Max players Capacity: 100 slots.
ts1
Group limit No team may exceed 1.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking RakNet is the network layer — the game's standard.
$r?
Region code The region code is unset.

Wipe schedule

^w
Weekly Every week it wipes.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; listed under Modded.

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.