VM_Lokal_Test
Offline 92.208.70.137:28015 checked 12h ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avg7-day peakServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 38% 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.
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 29 Oct, 12:05 UTC16h 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 26/500
- 127/100
- 57/225
- 10/700
- 30/700
- 50/200
Quick answers
from the figures on this pageWipe timing
What happens on VM_Lokal_Test when wipe day comes?
The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours.
How often does VM_Lokal_Test wipe, and when?
To tell the rhythm of VM_Lokal_Test, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 16 hours ago the current world was made.
Lists and filters
Which tags does VM_Lokal_Test carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game from VM_Lokal_Test. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show VM_Lokal_Test?
Rust Metrics lists featuring VM_Lokal_Test: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
Player count
What position does VM_Lokal_Test hold among Rust servers?
Ranking for VM_Lokal_Test: #8,427 on seven-day player hours, top 38% of all ranked servers.
How full does VM_Lokal_Test get?
Reading for VM_Lokal_Test: offline at this moment; last seen 12 hours ago. Seven-day check: 1 players on average. Peak reading: 1. The last 48 hours peaked at 13:00 UTC, averaging 1 players at that hour.
Operator and location
Which location does VM_Lokal_Test run from?
No region tag on VM_Lokal_Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 92.208.70.137:28015.
What Rust version is VM_Lokal_Test on?
Rust network protocol 2635 and build 168909 on Windows is the build VM_Lokal_Test runs. To get in, your game needs the same protocol; Steam applies the update.
Is VM_Lokal_Test up, and how often does it stay up?
Reading: offline. VM_Lokal_Test last answered 12 hours ago. Reading: 12% uptime over the last 2 full days. It was up 6 of 48 hours. Reading: first seen 27 October 2026, recorded by Rust Metrics.
Rules and settings
What settings and rules apply on VM_Lokal_Test?
Reading the name gives no gather rate for VM_Lokal_Test. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on VM_Lokal_Test?
Procedural map on VM_Lokal_Test, made by the game's generator.
Connection
How do you connect to VM_Lokal_Test?
Press F1 in Rust and enter client.connect 92.208.70.137:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.