Rust Data LabData lab · live
Live readings Servers11,757 Players64,357 Populated3,442 Fresh wipes · 3h196 Sampled every 5 min

Element card · group Modded · atomic number 9,972, its rank

VM_Lokal_Test

Online 92.208.70.137:28015 checked 10m ago

moddedoxide
Join the experiment
Atomic mass · players now 1/ 1 100% full Near capacity
7-day average1peak 1
Rank · atomic number#9,972top 45%
Last wipe1d agono schedule published
Next wipe–too few wipes seen yet
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
00.250.50.75112:0013:0014: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
This server has not answered a direct query in the last 48 hours.

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. 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
15k10k15k20k27 Oct28 Oct29 Oct

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

Reaction kinetics

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 13:02 UTC1d ago – – running 1

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 Sh ShockRust | Bl… 163
    ShockRust | Blue | NoLimit no group limit · 149 on average 163/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 133
    МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 133/ 100
  3. 3 Re RETRO RUST #1 … 186
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average 186/ 225
  4. 4 Ru 404 RUST 2Х|ДЛ… 68
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average 68/ 700
  5. 5 Ru RustSpain.com … 12
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average 12/ 200
  6. 6 Ru 404 RUST 2Х|ДЛ… 18
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average 18/ 1,000

Quick answers

from the figures on this page

Server setup

What map is in play on VM_Lokal_Test?

Generated by the game, the map on VM_Lokal_Test is procedural.

What settings and rules apply on VM_Lokal_Test?

Nothing in the name of VM_Lokal_Test gives a gather rate. With no change from the default, groups can hold up to 8 players. Play runs as survival, raiding, building and gathering: the standard game. Fighting and raiding between players are allowed. Plugins or settings change the game, so the browser lists it under Modded. Plugins in use: Oxide. VAC is on, Valve's anti-cheat.

Server details

In what location does VM_Lokal_Test sit?

There is no region on record for VM_Lokal_Test. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. Connect at 92.208.70.137:28015.

What Rust version does VM_Lokal_Test currently run?

On Windows, VM_Lokal_Test is running Rust network protocol 2635 and build 168909. Your game needs to match the protocol to join, and Steam updates it automatically.

Does VM_Lokal_Test stay up, and how reliable is its uptime?

At the moment, VM_Lokal_Test is online. 0 of 24 hours were up in the last 1 full day, which works out at 0%. On 27 October 2026, Rust Data Lab saw it for the first time.

Wipes and resets

How often does a wipe happen on VM_Lokal_Test, and at what time?

Too few wipes are on record for VM_Lokal_Test to reveal a rhythm. A monthly force wipe happens on every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. Counting back, the current world began 46 hours ago.

Tags, lists

Which meanings sit behind the tags on VM_Lokal_Test?

The game's server browser reads the tags VM_Lokal_Test publishes, which are gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): 1 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): RakNet is the network layer here, as standard in Rust; $r? (Region code): The region field is left blank; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because plugins or settings change the game, it is filed under Modded. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.

Where among the Rust Data Lab lists and filters does VM_Lokal_Test come up?

The Rust Data Lab lists that include VM_Lokal_Test are: Modded Rust servers, measured. Applying these filters on the server list returns it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Player numbers

Against other Rust servers, where does VM_Lokal_Test place?

VM_Lokal_Test sits at #9,972 for seven-day player hours, placing it in the top 45% of ranked servers.

What does the current player count on VM_Lokal_Test tell you?

At the moment VM_Lokal_Test has 1 of its 1 slots filled. A seven-day sample gives 1 players on average and 1 at the top. Over 48 hours, the highest average fell at 12:00 UTC, at 1 players.

How to join

What is the way to join VM_Lokal_Test?

You can connect by pressing F1 in Rust and entering client.connect 92.208.70.137:28015, or by pressing Launch Rust here, which starts the game through Steam and joins for you. Expect a queue: it is full right now.

Server tags

what each one means

Published as mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust style.
mp1
Max players 1 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 RakNet is the network layer here, as standard in Rust.
$r?
Region code The region field is left blank.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Because plugins or settings change the game, it is filed 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.