Top Rust ServersObservatory · live
Live Servers11,527 Players47,061 Populated3,278 Fresh wipes · 3h113 Scanevery 5 min

RS-3331Modded server

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

Offline 78.29.14.210:28115 checked 28m ago

2x solo weekly wipes moddedoxide
Connect
Players now
0/ 100
0% full
7-day average
1
peak 4
Rank
#3,331
top 15%
Last wipe
2d ago
weekly schedule
Next wipe
T− 4d 0h
Mon 19 Oct, 00:04 UTC
Light curve

Players

AveragePeak
0123400:0009:0018:0004:0013:0022:00

Hourly average and peak, UTC.

Systems telemetry

Server performance

025507510000:0009:0018:0004:0013:0022: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.

Standing

Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

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

Orbit

Wipe schedule

fixed weekdays

Next wipe Monday 19 October, 00:04 UTC, in 4d 0h. Every Monday at 00:04 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. T− 4d 0hMon 19 Oct, 00:04 UTC
  2. T− 11d 0hMon 26 Oct, 00:04 UTC
  3. T− 18d 0hMon 2 Nov, 00:04 UTC
  4. T− 21d 19hThu 5 Nov, 19:00 UTCFW
  5. T− 25d 0hMon 9 Nov, 00:04 UTC
  6. T− 32d 0hMon 16 Nov, 00:04 UTC
  7. T− 39d 0hMon 23 Nov, 00:04 UTC

The first 48 hours of its last wipes

Mon 12 OctMon 5 OctThu 1 Oct
01234+0h+9h+19h+28h+38h+47h

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

Record

Wipes

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

Nearby objects

Similar servers

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

Readouts in words

Quick answers

From the figures on this page.

Player count

How populated is Solo|x2|Kits|TP|Vip[Viking]?

Solo|x2|Kits|TP|Vip[Viking] is offline at this moment; the last signal was 28 minutes ago. Over seven days it averaged 1, and the highest point was 4. Over the last 48 hours, the peak hour was 16:00 UTC, with an average of 3 players.

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

On player hours across seven days, Solo|x2|Kits|TP|Vip[Viking] is #3,331, inside the top 15% of all ranked servers. It is #126 among solo servers.

Tags and filters

Where does Solo|x2|Kits|TP|Vip[Viking] appear among the Top Rust Servers lists and filters?

These Top Rust Servers lists count Solo|x2|Kits|TP|Vip[Viking] among their servers: Rust servers with 2x gather rate, Top modded Rust servers and Solo Rust servers, ranked live. 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.

What is the meaning of the tags on Solo|x2|Kits|TP|Vip[Viking]?

Published by Solo|x2|Kits|TP|Vip[Viking] for the game's server browser to read: gmrust (Game mode): Standard survival, as in Rust; mp100 (Max players): Player slots: 100; ts1 (Group limit): The team limit is 1; v2634 (Protocol): To join, your game must be on protocol 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): This uses RakNet, Rust's default network layer; $r? (Region code): The region code is left blank; ^w (Weekly): This server wipes once a week; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): The game is changed by plugins or settings, so it is listed as Modded. At the top of this page you also see its players now, its queue, and the time its world was made, taken from the tags.

Settings and map

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

The map on Solo|x2|Kits|TP|Vip[Viking] is procedural, size 4,500, seed 406166594, and generated by the game. The map can be seen on RustMaps from this page, as identical size and seed yield the same map.

What does Solo|x2|Kits|TP|Vip[Viking] run for rules and settings?

2x gather is what Solo|x2|Kits|TP|Vip[Viking] runs, as its name shows. Teams are not allowed: this is solo only. You play survival, standard survival: gathering, building and raiding. Player versus player combat and raiding are enabled. Plugins or settings change the game; it is listed as Modded. Oxide plugins are in use. The server runs with VAC on.

Server info

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

On Linux, Solo|x2|Kits|TP|Vip[Viking] operates Rust network protocol 2634 and build 167781. The protocol must match for you to join; Steam will update your game.

How well does Solo|x2|Kits|TP|Vip[Viking] perform?

Over the last two days, it ran at an average of 47 server fps, minimum 10. At its peak, it held 126,296 entities: everything from buildings to deployables and more. At its highest, it consumed 4,414 MB of memory. A climbing entity count and low fps are the source of the lag players feel.

What is the server location for Solo|x2|Kits|TP|Vip[Viking]?

No region is published by Solo|x2|Kits|TP|Vip[Viking]. Top Rust Servers does not look up where the machine stands; it shows where a server says it is. 78.29.14.210:28115 is its address.

How reliable is Solo|x2|Kits|TP|Vip[Viking]?

Solo|x2|Kits|TP|Vip[Viking] is offline now; the last time it was seen was 28 minutes ago. Based on the uptime it reports, the last restart was roughly 22 hours ago. Across the last 7 full days, it was online for 168 of 168 hours, or 100%. Its first appearance in Top Rust Servers was on 13 September 2026.

Wipe cycle

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

Across recent wipes, the busiest times averaged 4 players. The peak of the latest wipe came 16 hours after it began. Half the peak was held until the next wipe in 80% of recent wipes. In the cases where it did not hold, the crowd dropped below half by day 2.

How often does Solo|x2|Kits|TP|Vip[Viking] wipe?

The wipe frequency for Solo|x2|Kits|TP|Vip[Viking] is every Monday at 00:04 UTC. On Monday 19 October at 00:04 UTC, the next wipe is anticipated. The present world has been live since 2 days 23 hours ago. The tags show a wipe schedule of one week.

Connection

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

To connect manually, open the console with F1 and type client.connect 78.29.14.210:28115. Or click Launch Rust on this page to open Rust through Steam and connect directly. You can find its website at http://viking.gamestores.app/.

Spectrum

Server tags

What each one means.

Published as mp100,ptrak,$r?,v2634,^w,gmrust,cs167781,ts1,^o^z

Game

gmrust
Game mode Standard survival, as in Rust.
mp100
Max players Player slots: 100.
ts1
Group limit The team limit is 1.
v2634
Protocol To join, your game must be on protocol 2634.
cs167781
Build The game build is 167781.
ptrak
Networking This uses RakNet, Rust's default network layer.
$r?
Region code The region code is left blank.

Wipe schedule

^w
Weekly This server wipes once a week.

Mods and access

^o
Oxide This server uses Oxide (uMod) for plugins.
^z
Modded The game is changed by plugins or settings, so it is listed as 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.