LiveLive coverage · Rust server
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 10% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
from its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 7d 18h. The force wipe · high confidence
Players each hour, from the hour of the wipe. The latest peaked at 7, 28 hours in.
The current map
Friday 23 October 2026, 06:25 UTC
Wipe
Thursday 15 October 2026, 23:09 UTC
Force wipe
Thursday 1 October 2026, 23:18 UTC FW
Wipe
Thursday 17 September 2026, 23:15 UTC
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.
The average peak across its recent wipes is 7 players. The crowd on the latest wipe peaked 28 hours in. The crowd stayed above half that peak until the next wipe in 33% of its recent wipes. In the other cases it dropped under half by day 8.5.
With too few of Classic|No mods[Viking]'s wipes recorded to confirm the schedule, the tag is used for the prediction. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe and one that hits every Rust server. 5 days 17 hours have passed since this world was generated. A two-weekly wipe schedule appears in its tags.
These are the Rust Live Stats lists Classic|No mods[Viking] fits: Live Rust community servers and Vanilla Rust servers, live. These filters on the server list bring it up: 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.
gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): 100 slots are available; ts8 (Group limit): Team cap: 8, which is the game default; v2635 (Protocol): You need protocol 2635 on your game to get in; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): No region code is set here; ^b (Biweekly): The cycle is two weeks per wipe; ^v (Vanilla): It runs the game as Facepunch ships it: rates, kits and rules unchanged; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server: that is the tag list Classic|No mods[Viking] publishes for the game's server browser. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
Live now: 0 players on Classic|No mods[Viking], out of 100 slots. Peak over the past week: 11. Average: 2 players. Between now and 48 hours back, 09:00 UTC drew the most players, 8 on average.
Ranked by seven-day player hours, Classic|No mods[Viking] is #2,185, placing it in the top 10% of ranked servers.
No gather rate appears in the name Classic|No mods[Viking]. No custom limit is set, so groups hold the default 8 players. It runs survival, the standard game: gather, build, raid. You can raid and fight other players. Community is its browser category. Oxide plugins are in use. Its self-description is vanilla: it runs the game as Facepunch ships it: rates, kits and rules unchanged. VAC is enabled: Valve's anti-cheat.
Classic|No mods[Viking] runs a game-generated procedural map: size 4,500, seed 1317874501. Size and seed repeat the same map, so RustMaps can show it from this page.
No region is published by Classic|No mods[Viking]. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. Connect to 78.29.14.210:28015.
It never went below 10 server fps in the last 48 hours, averaging 90. Buildings, deployables and everything else in the world added up to a maximum of 122,504 entities. Up to 4,754 MB of memory was used. Lag, as players feel it, comes from low fps and a rising entity count.
Rust network protocol 2635 and build 168909 on Linux is what Classic|No mods[Viking] runs. To join, your game must use the same protocol; Steam handles the update for you.
Right now Classic|No mods[Viking] is online. The uptime it reports puts the last restart at about 22 hours ago. 138 of 168 hours were online in the last 7 full days, giving 82% uptime. On 13 September 2026, Rust Live Stats saw it for the first time.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 78.29.14.210:28015. You can find its website at https://m.vk.com/rust_vikings.