On the class lists: D (54), with population over 48 hours and no performance mark.
Players now0/ 750% full
7-day average0peak 1
Rank#6,575top 30%
Last wipe5d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 75 on average. Plenty of space to grow.
Standingrank on player hours
70/ 100
B−
Holds a respectable place: #6,575 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 226 server fps on average.
Wipeskeeping the crowd after a wipe
50/ 100
D
Keeps a fair share of its players through a wipe: 50% of wipes kept half their crowd.
Momentumrank now against a week ago
52/ 100
D
Moving up: up 245 places this week.
A fair term, with more to come.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Rank
daily · 1 is best
RankRank in region
Top 30% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
···W···
·····W·
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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 gap6.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 4
The first 48 hours of its last wipes
Sat 24 OctThu 15 OctSun 11 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 24 Oct, 00:10 UTC5d ago
1
–
running
0
Thu 15 Oct, 16:25 UTC13d ago
1
halved by day 4
8.3 days
0
Sun 11 Oct, 19:31 UTC17d ago
2
✓ held half
3.9 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
classmates: the same kind of game, then region, group limit, rate and wipes
No region tag appears for [US] Viking Solo PvE, but the name suggests North America. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 135.148.15.213:23975.
How dependable is [US] Viking Solo PvE, and is it online at the moment?
Right now, [US] Viking Solo PvE is online. About 21 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. The first sighting by Rust Server Score was on 11 October 2026.
How well does [US] Viking Solo PvE run?
It averaged 226 server fps over the last 48 hours, with a low of 130. Buildings, deployables and everything else in the world added up to as many as 48,378 entities. Memory use reached up to 3,375 MB. When fps is low and entities climb, that is lag to players.
Which Rust version is [US] Viking Solo PvE running?
You will find [US] Viking Solo PvE on Rust network protocol 2635 and build 168909, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does [US] Viking Solo PvE wipe its map?
[US] Viking Solo PvE wipes at times that vary, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 5 days 11 hours.
What should you expect from wipe day on [US] Viking Solo PvE?
The average peak on its recent wipes was 1 players. Peak numbers came 0 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 50% of its recent wipes. In the other wipes it slipped under half by day 4.
Player numbers
Where does [US] Viking Solo PvE sit among Rust servers?
In the top 30% of all ranked servers, [US] Viking Solo PvE sits at #6,575 for player hours over the last seven days.
How many players does [US] Viking Solo PvE usually have?
With 75 slots available, [US] Viking Solo PvE currently has 0 players. The seven-day average is 0 players, with a peak of 1. Over the last 48 hours, the peak hour was 13:00 UTC, averaging 1 players.
Lists and filters
How should you read the tags on [US] Viking Solo PvE?
You'll see [US] Viking Solo PvE tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp75 (Max players): The server holds 75 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show [US] Viking Solo PvE?
These Rust Server Score lists count [US] Viking Solo PvE among them: Modded Rust servers, graded and North America Rust servers, graded. It shows under the following 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.
Map and rules
Which rules does [US] Viking Solo PvE enforce, and what are its settings?
Nothing in the name of [US] Viking Solo PvE states a gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map [US] Viking Solo PvE uses?
[US] Viking Solo PvE runs a game-generated procedural map at size 3,000, seed 31337. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How should you connect to [US] Viking Solo PvE?
Enter client.connect 135.148.15.213:23975 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp75,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp75
Max playersThe server holds 75 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find 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.
A fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).