VM_Lokal_Test
Offline 92.208.70.137:28015 checked 6h ago
Measurements
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
Top 38% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 29 Oct, 12:05 UTC10h ago | – | – | running | 0 |
| Tue 27 Oct, 13:02 UTC2d 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.
Quick answers
Population
How does VM_Lokal_Test rank against other Rust servers?
Over the past week it ranks #8,425 for player hours, which puts VM_Lokal_Test in the top 38% of all ranked servers.
How busy is VM_Lokal_Test?
At this count VM_Lokal_Test is offline, with its last sighting 6 hours ago. Seven days of counting give an average of 1 players and a peak of 1. In the last 48 hours the peak hour came at 13:00 UTC, averaging 1 players.
Tags
What do the server tags on VM_Lokal_Test mean?
What the game's server browser reads from VM_Lokal_Test is this set of tags: gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): You can join up to 1 slots; ts8 (Group limit): 8 per team is the default limit; v2635 (Protocol): The protocol is 2635; a different version will not connect; cs168909 (Build): Game build: 168909; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): The region code is left blank; ^o (Oxide): The plugin framework Oxide (uMod) runs on this server; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.
Which Rust Population lists and filters include VM_Lokal_Test?
VM_Lokal_Test appears among the Rust Population lists that follow: Modded Rust servers, counted. These are the filters it appears under when you browse the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
Wipe schedule
What does wipe day look like on VM_Lokal_Test?
The busiest point of its recent wipes averaged 1 players. The crowd on the latest wipe peaked 0 hours in.
What is the wipe schedule on VM_Lokal_Test?
Its rhythm cannot be told yet: too few of VM_Lokal_Test's wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. Counted from 9 hours ago, that is how long the current world has stood.
Settings
Which map does VM_Lokal_Test run?
VM_Lokal_Test uses a map the game generates: procedural.
What are the rules and settings on VM_Lokal_Test?
The name tells you nothing about gather rates: VM_Lokal_Test states none. Eight players per group is the default, and it applies here. This server runs survival, the usual game, where you gather, build and raid. You can raid and fight other players here. Modded is its browser category: plugins or settings change the game. You will find Oxide running as plugins. The anti-cheat VAC from Valve is enabled.
Server details
Which version of Rust does VM_Lokal_Test run?
On Windows, VM_Lokal_Test runs Rust network protocol 2635 and build 168909. Your game needs the same protocol to join; Steam takes care of updating it.
Is VM_Lokal_Test online, and how reliable is it?
Currently offline, VM_Lokal_Test was last seen 6 hours ago. The last 1 full day gave 0% uptime, with 0 of 24 hours recorded as up. It was first seen by Rust Population on 27 October 2026.
Where is VM_Lokal_Test located?
No region is published by VM_Lokal_Test. The location a server claims is what Rust Population shows, not the place where the machine stands. You will find it at 92.208.70.137:28015.
How to join
How do I join VM_Lokal_Test?
Open the console with F1 in Rust and enter client.connect 92.208.70.137:28015. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.