Rust PopulationField survey · Rust servers
Observing 48,587 players 11,721 servers 3,224 with someone on 110 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 2,185habitat unknownfirst seen 13 Sep 2026

Classic|No mods[Viking]

Online 78.29.14.210:28015 checked 6m ago

biweekly wipes vanillaoxide

Measurements

Players now
1/ 100
= 1 player
1% full
7-day average
2
peak 11
Rank
#2,185
top 10%
Last wipe
5d ago
biweekly schedule
Next wipe
7d 18h
Thu 5 Nov, 19:00 UTC FW
Obs. 1 · sightings

Players

AveragePeak
02.557.51001:0010:0019:0003:0012:0022:00

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

05010015020001:0010:0019:0003:0012: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.

Obs. 3 · standing

Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Obs. 4 · the wipe cycle

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 18h. The force wipe · high confidence

14 days
usual gap
between real wipes
67%
on rhythm
of its recent wipes
7
wipe-day peak
players, last three wipes
33%
crowd held
else halves by day 8.5

Coming wipes

7d 18h
Thu 5 Nov, 19:00 UTC
FW
8d 6h
Fri 6 Nov, 06:25 UTC
22d 6h
Fri 20 Nov, 06:25 UTC
35d 18h
Thu 3 Dec, 19:00 UTC
FW
36d 6h
Fri 4 Dec, 06:25 UTC

The first 48 hours of its last wipes

Fri 23 OctThu 15 OctThu 1 Oct
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 7, 28 hours in.

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 06:25 UTC5d ago 7 – running 0
Thu 15 Oct, 23:09 UTC13d ago 7 held half 7.3 days 0
Thu 1 Oct, 23:18 UTC FW27d ago 8 halved by day 11 14 days 0
Thu 17 Sep, 23:15 UTC41d ago 5 halved by day 6 14 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.

Field questions

Quick answers

from the figures on this page

Population

How does Classic|No mods[Viking] rank against other Rust servers?

By player hours over the last seven days, Classic|No mods[Viking] places at #2,185, within the top 10% of ranked servers.

How busy is Classic|No mods[Viking]?

The count reads 1 players on Classic|No mods[Viking], which has 100 slots. Seven days of counting give an average of 2 players and a peak of 11. In the last 48 hours the peak hour came at 09:00 UTC, averaging 8 players.

Lists and tags

What do the server tags on Classic|No mods[Viking] mean?

What the game's server browser reads from Classic|No mods[Viking] is this set of tags: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): You can join up to 100 slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): The protocol is 2635; a different version will not connect; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): A wipe happens once a fortnight; ^v (Vanilla): No kits, no rate changes, no rules added: the game as Facepunch ships it; ^o (Oxide): Oxide (uMod) provides the plugin framework here. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.

Which Rust Population lists and filters include Classic|No mods[Viking]?

On Rust Population, Classic|No mods[Viking] is filed under these lists: Community servers, field-listed and Vanilla Rust servers, counted. Look for it under these filters on the server list: Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last week.

Wipe notes

What does wipe day look like on Classic|No mods[Viking]?

Averaged over recent wipes, 7 players were counted at the busiest point. Peak came 28 hours into the latest wipe. The crowd stayed above half that peak until the next wipe in 33% of its recent wipes. The crowd dropped below half by day 8.5 when it did not hold.

What is the wipe schedule on Classic|No mods[Viking]?

Its tag sets the prediction: too few of Classic|No mods[Viking]'s wipes are on record to confirm the schedule. On Thursday 5 November at 19:00 UTC comes its next wipe: the force wipe, when all Rust servers wipe. Counted from 5 days 17 hours ago, that is how long the current world has stood. The tags carry an every-two-weeks wipe schedule.

Map and rules

Which map does Classic|No mods[Viking] run?

A procedural map of size 4,500 from seed 1317874501, generated by the game, is in use on Classic|No mods[Viking]. The map follows from its size and seed, and RustMaps shows it from this page.

What are the rules and settings on Classic|No mods[Viking]?

No gather rate appears in the name of Classic|No mods[Viking]. Eight players per group is the default, and it applies here. This server runs survival, gather, build and raid, as in the standard game. You can raid and fight other players here. A community server, it appears in the Community section of the browser. The plugins it runs are Oxide. Vanilla is the label it uses: no kits, no rate changes, no rules added: the game as Facepunch ships it. The anti-cheat VAC from Valve is enabled.

About the server

Which version of Rust does Classic|No mods[Viking] run?

Rust network protocol 2635 and build 168909 on Linux is what Classic|No mods[Viking] uses. The protocol must match for you to join, and Steam updates it for you.

Does Classic|No mods[Viking] run smoothly?

The last 48 hours saw an average of 90 server fps, with 10 as the lowest. Up to 122,504 entities were present, counting buildings, deployables and everything else. Memory use peaked at 4,754 MB. Players feel lag when fps is low and the entity count climbs.

Is Classic|No mods[Viking] online, and how reliable is it?

Classic|No mods[Viking] is up and running at the moment. The uptime it reports suggests a restart roughly 22 hours ago. It was up 82% of the time over the last 7 full days, 138 out of 168 hours. The first sighting by Rust Population was on 13 September 2026.

Where is Classic|No mods[Viking] located?

A region is not published by Classic|No mods[Viking]. Rust Population does not look up where the machine stands; it shows where the server says it is. 78.29.14.210:28015 is where it lives.

How to join

How do I join Classic|No mods[Viking]?

Open the console with F1 in Rust and enter client.connect 78.29.14.210:28015. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you. You can find its website at https://m.vk.com/rust_vikings.

Key to its markings

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^b,^v,gmrust,cs168909,ts8,^o

Game

gmrust
Game mode Survival in the standard Rust style.
mp100
Max players You can join up to 100 slots.
ts8
Group limit Teams are capped at 8, the default setting.
v2635
Protocol The protocol is 2635; a different version will not connect.
cs168909
Build Game build: 168909.
ptrak
Networking RakNet is the network layer here, as standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly A wipe happens once a fortnight.

Difficulty

^v
Vanilla No kits, no rate changes, no rules added: the game as Facepunch ships it.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.

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.