Online 92.208.70.137:28015 checked 13m ago
VM_Lokal_Test
Connect
srv = rust.server("92.208.70.137:28016")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 38% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.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 · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 29 Oct, 12:05 UTC4h ago | NaN | NaN | running | 0 |
| 1 | Tue 27 Oct, 13:02 UTC2d ago | 1 | NaN | 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 92.208.70.137:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 29 Oct 2026, 12:42 UTC
- hostname
- –
- first seen
- 27 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 162/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 187/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 83/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 87 on average | 256/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 350/350 |
Quick answers
From the figures on this page.
Player counts
How does VM_Lokal_Test compare in the rankings?
Player hours over seven days put VM_Lokal_Test at #8,461, in the top 38% of the ranked set.
What population does VM_Lokal_Test carry?
VM_Lokal_Test reports 0 players at this refresh, with 1 slots configured. Over the last seven days it averaged 1 players and peaked at 1. Peak hour in the last 48 hours: 13:00 UTC, mean 1 players.
About the server
Which Rust version is VM_Lokal_Test on?
Version Rust network protocol 2635 and build 168909 on Windows is reported by VM_Lokal_Test. Joining needs the same protocol on your game; Steam handles the update.
How reliable is VM_Lokal_Test, and is it up?
VM_Lokal_Test reports itself online at the current refresh. Uptime of 0% across the last 1 full day: 0 hours of 24. The first row Rust Data holds for it is dated 27 October 2026.
In which location is VM_Lokal_Test hosted?
No region is published by VM_Lokal_Test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 92.208.70.137:28015 is its address.
Rules, settings, map
Which rules apply on VM_Lokal_Test, and what settings?
No gather rate appears in the name: VM_Lokal_Test. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on VM_Lokal_Test?
VM_Lokal_Test runs a procedural map, which the game generates.
Wipes and dates
On what schedule does VM_Lokal_Test wipe?
A rhythm cannot be read from the wipes of VM_Lokal_Test on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 3 hours ago.
What is wipe day on VM_Lokal_Test like?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Which Rust Data filters and lists contain VM_Lokal_Test?
On Rust Data, VM_Lokal_Test appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
How should you read the server tags on VM_Lokal_Test?
These tags are published by VM_Lokal_Test and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): Slot count: 1; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into VM_Lokal_Test?
In Rust, F1 opens the console: type client.connect 92.208.70.137:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.