Rust Server TrendsSeismic network · station log
Recording Stations11,814 Players72,000 Active3,646 Wipes · 3 h206 48 h

Station XX-6566 · recording

[US] Viking Solo PvE

Online 135.148.15.213:23975 checked 6m ago

moddedoxide
Connect
Players now
0/ 75
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#6,566
top 30%
Last wipe
5d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-6566 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 75 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
−1into Wed 14:00 UTC
Peak · 48 h
1most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.250.50.75114:0023:0008:0016:0002:0011:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040014:0023:0008:0016:0002:0011: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 11 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k11 Oct15 Oct18 Oct22 Oct25 Oct29 Oct

Top 30% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap
6.1 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
50%else halves by day 4

The first 48 hours of its last wipes

Sat 24 OctThu 15 OctSun 11 Oct
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sat 24 Oct, 00:10 UTC5d ago M0.0rising 1 – running 0
Thu 15 Oct, 16:25 UTC13d ago M0.0rising 1 halved by day 4 8.3 days 0
Sun 11 Oct, 19:31 UTC17d ago M0.3rising 2 held half 3.9 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Friendly Seattle: No KOS | Chill | Noob Friendly NA · groups of 8+ · biweekly · 42 on average
7/ 100
[US] Enardo - Random Farming - Small One Grid | OneGrid NA · groups of 8+ · 29 on average
4/ 50
[NA] Willjum's Solo Only | Thursday Wipes NA · groups of 8+ · weekly · 27 on average
2/ 100
Rust Degens - US Vanilla | Fridays NA · groups of 8+ · weekly · 15 on average
8/ 150
[NA] Willjum's Casual Solo/Duo Monthly NA · groups of 8+ · monthly · 14 on average
1/ 175
Hempville 420 No Kos Low Decay / Limited PvP NA · groups of 8+ · monthly · 7 on average
1/ 90
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on [US] Viking Solo PvE?

[US] Viking Solo PvE runs a procedural map of size 3,000 with seed 31337, 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 [US] Viking Solo PvE?

The name of [US] Viking Solo PvE gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.

Live population

How many players are recorded on [US] Viking Solo PvE right now?

At this moment, [US] Viking Solo PvE records 0 players across 75 slots. Averaged across the last seven days the population was 0 players, reaching a peak of 1. The last 48 hours show their highest activity at 13:00 UTC, averaging 1 players.

How does [US] Viking Solo PvE rank against other Rust servers?

The last seven days of player hours place [US] Viking Solo PvE at #6,566, in the top 30% of all ranked servers.

Server details

How reliably does [US] Viking Solo PvE stay online?

As recorded now, [US] Viking Solo PvE is running. The uptime it reports puts its last restart about 22 hours ago. It was up 99% of the time across the last 7 full days: 167 of 168 hours. 11 October 2026 is when Rust Server Trends first recorded it.

How well does [US] Viking Solo PvE perform under load?

Its average server fps over the last 48 hours was 226, and it never dropped below 130. The world held up to 48,378 entities at its peak, buildings and deployables included. It reached a ceiling of 3,375 MB of memory. What you feel as lag is the combination of low fps and a rising entity count.

Which region does [US] Viking Solo PvE run from?

Its name points to North America, but [US] Viking Solo PvE publishes no region tag. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 135.148.15.213:23975.

What build of Rust does [US] Viking Solo PvE use?

[US] Viking Solo PvE is running Rust network protocol 2635 and build 168909 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

What does wipe day look like on [US] Viking Solo PvE?

1 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 50% of its recent wipes. It fell under half by day 4 in the wipes where it didn't hold.

On what timetable does [US] Viking Solo PvE run its wipes?

There is no next wipe to predict at [US] Viking Solo PvE, since its wipes fall at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 5 days 13 hours is how long the current world has been running.

Server tags

What do the server tags on [US] Viking Solo PvE mean?

These are the tags [US] Viking Solo PvE publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp75 (Max players): Slots: 75; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does [US] Viking Solo PvE appear?

You will find [US] Viking Solo PvE on the following Rust Server Trends lists: Modded Rust servers, tracked live and North America Rust servers. You will find it under these filters on the server list: Region: North America; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

How to join

How do you connect to [US] Viking Solo PvE?

Enter client.connect 135.148.15.213:23975 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp75,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp75
Max players Slots: 75.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build It runs game build 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it 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.

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.