Station XX-9999 · no signal
VM_Lokal_Test
Offline 92.208.70.137:28015 checked 1d ago
- Players now
- 1/ 1
- 100% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 1
- peak 1
- Rank
- #9,999
- top 45%
- Last wipe
- 1d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 1 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- +0into Tue 12:00 UTC
- Peak · 48 h
- 1most players in any hour
- Events picked
- 1wipe on this record, in red
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 45% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Tue 27 Oct, 13:02 UTC1d ago | – | – | – | – | running | 1 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageRules and settings
Which map is running on VM_Lokal_Test?
A procedural map runs on VM_Lokal_Test, generated by the game.
Which settings and rules apply on VM_Lokal_Test?
No gather rate appears in the name of VM_Lokal_Test. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.
Live population
What is the current population on VM_Lokal_Test?
VM_Lokal_Test is not responding at this moment and is offline, last seen 43 hours ago. Across seven days this server recorded an average of 1 players and a peak of 1. The busiest point in the last 48 hours came at 12:00 UTC, averaging 1 players.
How does VM_Lokal_Test rank against other Rust servers?
Over the last seven days, VM_Lokal_Test recorded enough player hours to reach #9,999 worldwide, placing it in the top 45% of all ranked servers.
Operator and location
How reliably does VM_Lokal_Test stay online?
No contact with VM_Lokal_Test right now, and the last recorded contact was 43 hours ago. 0 of 24 hours in the last 1 full day were up time, 0% of the total. On 27 October 2026 it was recorded for the first time by Rust Server Trends.
Which region does VM_Lokal_Test run from?
A region is not published by VM_Lokal_Test. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 92.208.70.137:28015.
Which Rust version is VM_Lokal_Test running?
Rust network protocol 2635 and build 168909 on Windows is what VM_Lokal_Test runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
How often does VM_Lokal_Test wipe, and on which days?
On record so far are too few of VM_Lokal_Test's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 44 hours.
Tags
What do the server tags on VM_Lokal_Test mean?
The game's server browser reads the tags VM_Lokal_Test publishes: gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does VM_Lokal_Test appear?
The Rust Server Trends lists that take in VM_Lokal_Test are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Join the server
How do you connect to VM_Lokal_Test?
Enter client.connect 92.208.70.137:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.