VM_Lokal_Test
Key statistics
the figures behind the quote- Players now
- 0/ 1 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #16,283 top 70%
- Rank · 7d ago
- #8,429 ▼7854 places down
- Last wipe
- 14d ago no schedule published
- Next wipe
- – too few wipes seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 27 Oct 2026 no hostname published
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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yet- usual gap
- 2 days between real wipes
- wipe-day peak
- 1 players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 5 Nov, 19:00 UTC FW6d ago | – | – | running | – |
| Thu 29 Oct, 12:05 UTC14d ago | 1 | – | – | 0 |
| Tue 27 Oct, 13:02 UTC16d ago | 1 | – | 2 days | 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| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | STEEL RUST /ДЛЯ НОВИЧКОВ /EU Main 11.11EU · groups of 24+ · monthly · 138 on average | 53/100 | ▼−403−88.4% | |
| 2 | 666 RUST /ДЛЯ НОВИЧКОВ /ПИТЕРСКИЙ 11.11EU · groups of 16+ · monthly · 137 on average | 51/750 | ▼−243−82.7% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 11.11EU · groups of 8+ · weekly · 127 on average | 133/100 | ▲+6+4.3% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 11.11EU · groups of 16+ · monthly · 124 on average | 210/1000 | ▼−81−27.8% | |
| 5 | ShockRust | Blue | NoLimitno group limit · 121 on average | 165/400 | ▼−40−19.3% | |
| 6 | Московская Классика для НовичковEU · groups of 8+ · weekly · 120 on average | 139/300 | ▲+15+11.8% |
Quick answers
from the figures on this pageServer Rules
How is VM_Lokal_Test configured in terms of rules and settings?
No gather rate appears in the name of VM_Lokal_Test. The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. The server browser lists it as Modded: plugins or settings change the game. Oxide plugins are in use. The server has VAC, Valve's anti-cheat, switched on.
Which map is played on VM_Lokal_Test?
The game generates the procedural map on VM_Lokal_Test.
Activity
Where does VM_Lokal_Test sit in the rankings?
For the last seven days, VM_Lokal_Test holds rank #16,283 on player hours, in the top 70% of all ranked servers.
How many players does VM_Lokal_Test have?
At present, VM_Lokal_Test is offline; the last sighting was 13 days 22 hours ago.
Wipe Frequency
What happens on wipe day at VM_Lokal_Test?
An average of 1 players marked the busiest point of its recent wipes. 0 hours after the latest wipe, the crowd reached its peak.
On what cycle does VM_Lokal_Test wipe?
There are too few wipes on record for VM_Lokal_Test to reveal its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 3 December at 19:00 UTC. Its world now is 14 days 2 hours old.
Server Details
What is the location of VM_Lokal_Test?
There is no region published for VM_Lokal_Test. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. 92.208.70.137:28015 is its address.
VM_Lokal_Test is on which Rust version?
The build is Rust network protocol 2635 and build 168909 on Windows, running on VM_Lokal_Test. Joining requires the same protocol on your game, which Steam updates.
How reliable is VM_Lokal_Test and is it currently online?
VM_Lokal_Test is down. The last time we saw it was 13 days 22 hours ago. 0% is its uptime for the last 7 full days, 0 of 168 hours. First sighting by Rust Analytics: 27 October 2026.
Server Tags
What is the meaning of the tags on VM_Lokal_Test?
The game's server browser reads gmrust (Game mode): Rust's standard survival mode; mp1 (Max players): It holds 1 slots; ts8 (Group limit): Team size stays at the game default of 8; v2635 (Protocol): Your game must run protocol 2635 to connect; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): Region code: none set; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): Modded listing: the game is changed by plugins or settings, which VM_Lokal_Test publishes. The top of this page and the tags both show its players now, its queue and when its world was made.
Where does VM_Lokal_Test show up in Rust Analytics lists and filters?
The following Rust Analytics lists feature VM_Lokal_Test: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Joining the Server
What steps do I take to join VM_Lokal_Test?
The console route: start Rust, press F1, enter client.connect 92.208.70.137:28015. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp1
ts8
v2635
cs168909
ptrak
$r?
Mods and access
^o
^z
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.