On the class lists: C (63), with population over 48 hours and no performance mark.
Players now3/ 1003% full
7-day average1peak 7
Rank#2,720top 12%
Last wipe3d agoweekly schedule
Next wipe3d 7hMon 2 Nov, 00:13 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 1 of 100 on average. Plenty of space to grow.
Standingrank on player hours
88/ 100
A−
Holds a respectable place: #2,720 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
85/ 100
A−
Mostly smooth: 51 server fps on average.
Wipeskeeping the crowd after a wipe
80/ 100
B+
Holds its players well after a wipe: 80% of wipes kept half their crowd.
Momentumrank now against a week ago
52/ 100
D
Moving up: up 126 places this week.
A steady term.
Strongest in uptime (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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 12% of all ranked servers, and #122 of the solo servers (top 55%). Ranked on player hours over the last seven days.
Attendance: the wipe record
8 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
W·····W
·······
W··F···
W······
W······
W······
W···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Monday 2 November, 00:13 UTC, in 3d 7h.
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
3d 7hMon 2 Nov, 00:13 UTC
7d 1hThu 5 Nov, 19:00 UTCFW
10d 7hMon 9 Nov, 00:13 UTC
17d 7hMon 16 Nov, 00:13 UTC
24d 7hMon 23 Nov, 00:13 UTC
31d 7hMon 30 Nov, 00:13 UTC
35d 1hThu 3 Dec, 19:00 UTCFW
38d 7hMon 7 Dec, 00:13 UTC
The first 48 hours of its last wipes
Mon 26 OctMon 19 OctMon 12 Oct
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 UTCFW27d 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
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is Solo|x2|Kits|TP|Vip[Viking] based in?
Solo|x2|Kits|TP|Vip[Viking] leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 78.29.14.210:28115 is the address to use.
How reliable is Solo|x2|Kits|TP|Vip[Viking], and is it up?
You can join now: Solo|x2|Kits|TP|Vip[Viking] is online. About 15 hours ago, it restarted, based on the uptime it reports. It was up 99% of the time over the last 7 full days, 167 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
How well does Solo|x2|Kits|TP|Vip[Viking] run?
It averaged 51 server fps over the last 48 hours, with a low of 10. Buildings, deployables and everything else in the world added up to as many as 118,177 entities. Memory use reached up to 4,361 MB. When fps is low and entities climb, that is lag to players.
On what Rust version does Solo|x2|Kits|TP|Vip[Viking] sit?
You will find Solo|x2|Kits|TP|Vip[Viking] 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 Solo|x2|Kits|TP|Vip[Viking] wipe its map?
Wipes come every Monday at 00:13 UTC on Solo|x2|Kits|TP|Vip[Viking]. It is due to wipe next on Monday 2 November at 00:13 UTC. 3 days 16 hours have passed since this world was made. Its tags state that it wipes weekly.
What should you expect from wipe day on Solo|x2|Kits|TP|Vip[Viking]?
Recent wipes have peaked at 4 players on average. Peak numbers came 38 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 80% of its recent wipes. Day 2 is when it sank below half in the wipes that did not hold.
Player numbers
Where does Solo|x2|Kits|TP|Vip[Viking] sit among Rust servers?
In the top 12% of all ranked servers, Solo|x2|Kits|TP|Vip[Viking] sits at #2,720 for player hours over the last seven days. It comes #122 among servers in the solo group.
What does the population on Solo|x2|Kits|TP|Vip[Viking] look like?
With 100 slots available, Solo|x2|Kits|TP|Vip[Viking] currently has 3 players. The seven-day average is 1 players, with a peak of 7. The highest average in the last 48 hours came at 14:00 UTC, with 4 players.
Lists and filters
What do Solo|x2|Kits|TP|Vip[Viking]'s tags stand for?
The game's browser takes its cue from the tags Solo|x2|Kits|TP|Vip[Viking] has set: gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; ts1 (Group limit): A team can hold 1 players at most; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^w (Weekly): Wipes come once a week; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show Solo|x2|Kits|TP|Vip[Viking]?
Rust Server Score lists that include Solo|x2|Kits|TP|Vip[Viking]: 2x Rust servers, graded, Modded Rust servers, graded and Solo Rust servers, graded. 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.
Map and rules
Which rules does Solo|x2|Kits|TP|Vip[Viking] enforce, and what are its settings?
The name of Solo|x2|Kits|TP|Vip[Viking] points to a 2x gather rate. Solo play only, with no teams permitted. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Solo|x2|Kits|TP|Vip[Viking] runs which map?
A procedural map of size 4,500 and seed 1607695022, generated by the game, is what Solo|x2|Kits|TP|Vip[Viking] runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
What is the way to join Solo|x2|Kits|TP|Vip[Viking]?
To connect, start Rust, press F1, and type client.connect 78.29.14.210:28115. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at http://viking.gamestores.app/.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^w,gmrust,cs168909,ts1,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max players100 slots are available.
ts1
Group limitA team can hold 1 players at most.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyWipes come once a week.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, 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.
A steady term. Strongest in uptime (A); population is the one to work on (F).