Rust Data LabData lab · live
Live readings Servers11,768 Players60,085 Populated3,517 Fresh wipes · 3h135 Sampled every 5 min

Element card · group Vanilla · atomic number 2,189, its rank

Classic|No mods[Viking]

Online 78.29.14.210:28015 checked 9m ago

biweekly wipes vanillaoxide
Join the experiment
Atomic mass · players now 2/ 100 2% full Room to join
7-day average2peak 11
Rank · atomic number#2,189top 10%
Last wipe5d agobiweekly schedule
Next wipe7d 20hThu 5 Nov, 19:00 UTC FW
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
02.557.51023:0008:0017:0002:0011:0021:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
05010015020023:0008:0017:0002:0011:0021: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.

Result 03

Rank

Result

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.

Reaction kinetics

Wipe schedule

from its schedule tag

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

usual gap14 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak7players, last three wipes
crowd held33%else halves by day 8.5

Coming wipes

  1. 7d 20hThu 5 Nov, 19:00 UTCFW
  2. 8d 7hFri 6 Nov, 06:25 UTC
  3. 22d 7hFri 20 Nov, 06:25 UTC
  4. 35d 20hThu 3 Dec, 19:00 UTCFW
  5. 36d 7hFri 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.

Reaction log

Wipes

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

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Ru Rustoria.co - … 92
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 252 on average 92/ 200
  2. 2 Ru Rustafied.com … 33
    Rustafied.com - EU Medium - Large EU · groups of 16+ · biweekly · 133 on average 33/ 100
  3. 3 Ru Rustopia.gg - … 46
    Rustopia.gg - US Medium NA · groups of 12+ · biweekly · 101 on average 46/ 200
  4. 4 Ru Rusty Moose |U… 32
    Rusty Moose |US Biweekly| NA · groups of 12+ · biweekly · 71 on average 32/ 200
  5. 5 Ru Rustoria.co - … 9
    Rustoria.co - SEA Medium EA · groups of 16+ · biweekly · 67 on average 9/ 200
  6. 6 Ru Rustoria.co - … 24
    Rustoria.co - US Medium Premium NA · groups of 12+ · biweekly · 42 on average 24/ 200

Quick answers

from the figures on this page

Map and rules

What map is in play on Classic|No mods[Viking]?

A procedural map of size 4,500 with seed 1317874501 runs on Classic|No mods[Viking], generated by the game. Same size and seed give the same map, so this page lets you look at it on RustMaps.

How is Classic|No mods[Viking] configured, and what rules apply?

Nothing in the name of Classic|No mods[Viking] gives a gather rate. With no change from the default, groups can hold up to 8 players. survival is the game mode, raiding, building and gathering: the standard game. You can fight other players and raid them. The server browser lists it under Community. Plugins in use: Oxide. The server describes itself as vanilla: nothing is changed: rates, kits and rules are as Facepunch ships them. VAC is on, Valve's anti-cheat.

Server details

Which location is Classic|No mods[Viking] based in?

Nothing about a region is published by Classic|No mods[Viking]. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. Connect at 78.29.14.210:28015.

Which Rust version is Classic|No mods[Viking] on?

Rust network protocol 2635 and build 168909 on Linux is what Classic|No mods[Viking] uses. Joining requires the same protocol on your game; Steam takes care of updating it.

How reliably does Classic|No mods[Viking] stay online?

At the moment, Classic|No mods[Viking] is online. About 21 hours ago is when it last restarted, based on its uptime. For the last 7 full days, 162 of 168 hours were online, giving 96% uptime. It first appeared to Rust Data Lab on 13 September 2026.

Is Classic|No mods[Viking] known for smooth running?

Server fps averaged 86 over the last 48 hours, with 10 as the lowest. The entity count reached 122,498, including buildings, deployables and all other world items. Up to 4,754 MB of memory was used. What players experience as lag comes from low fps and a rising entity count.

Wipes and resets

When does Classic|No mods[Viking] wipe, and how often?

Following the tag is the best the prediction can do for Classic|No mods[Viking], whose record holds too few wipes to confirm its schedule. The force wipe on Thursday 5 November at 19:00 UTC is when this server next wipes, along with every other Rust server. Counting back, the current world began 5 days 16 hours ago. Its tags list a wipe schedule of one wipe every two weeks.

On Classic|No mods[Viking], what happens when wipe day arrives?

Recent wipes on average reached 7 players at their busiest. Peak numbers on the latest wipe came 28 hours in. Half that peak was held until the next wipe in 33% of recent wipes. Where it did not hold, the crowd dropped below half by day 8.5.

Tags, lists

Which meanings sit behind the tags on Classic|No mods[Viking]?

These are the tags Classic|No mods[Viking] makes public for the server browser to read: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): 100 is the slot count; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): Protocol 2635 is required; join only if your game matches it; cs168909 (Build): It runs build 168909; ptrak (Networking): This runs on RakNet, the standard layer; $r? (Region code): No region code is set; ^b (Biweekly): Every two weeks, the server wipes; ^v (Vanilla): Nothing is changed: rates, kits and rules are as Facepunch ships them; ^o (Oxide): Plugins run through Oxide (uMod). Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

Where among the Rust Data Lab lists and filters does Classic|No mods[Viking] come up?

You will find Classic|No mods[Viking] on the following Rust Data Lab lists: Rust community servers, measured and Vanilla Rust servers, measured. You can find it on the server list by applying these filters: 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.

Population

Against other Rust servers, where does Classic|No mods[Viking] place?

Player hours over the last week put Classic|No mods[Viking] at #2,189, inside the top 10% of ranked servers.

What does the current player count on Classic|No mods[Viking] tell you?

Of 100 slots, 2 are taken on Classic|No mods[Viking] right now. Averaged over the past week: 2 players, peaking at 11. The busiest point in the last 48 hours came at 09:00 UTC, averaging 8 players.

How to join

What steps get you onto Classic|No mods[Viking]?

Open the console with F1 in Rust and type client.connect 78.29.14.210:28015. The Launch Rust button on this page does the same job through Steam. For more, visit https://m.vk.com/rust_vikings.

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 100 is the slot count.
ts8
Group limit Teams cap at 8, which is the game default.
v2635
Protocol Protocol 2635 is required; join only if your game matches it.
cs168909
Build It runs build 168909.
ptrak
Networking This runs on RakNet, the standard layer.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Every two weeks, the server wipes.

Difficulty

^v
Vanilla Nothing is changed: rates, kits and rules are as Facepunch ships them.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).

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.