LVSTestLabo
Online 82.21.2.12:10255 checked 10m ago
Server instruments
last reading Thu 06:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 10 · below 20 is lag, below 10 is badEntities
48 h range 28,917–57,158 · memory 1,939 MBUptime
8 h 58 min since its last restart, at the last readingPlayers
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 67% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. 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 3, 26 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Tue 27 Oct, 11:04 UTC1d ago | – | – | running | 0 |
| Mon 5 Oct, 10:03 UTC23d ago | 3 | halved by day 2 | 22 days | 0 |
| Thu 1 Oct, 19:49 UTC FW27d ago | 0 | – | 3.6 days | 0 |
| Mon 14 Sep, 22:09 UTC44d ago | 3 | halved by day 15 | 16.9 days | 0 |
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- 80/500
- 126/100
- 121/225
- 41/700
- 4/200
- 14/1000
Quick answers
from the figures on this pageWipe timing
What should you expect from wipe day on LVSTestLabo?
At their busiest, its recent wipes drew 2 players on average. Peak crowd on the latest wipe: 26 hours in. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 8.5 it fell below half when it didn't.
How often does LVSTestLabo wipe, and when?
There is no next wipe to predict: LVSTestLabo wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 42 hours ago the current world was made.
Lists and filters
Which tags does LVSTestLabo carry, and what do they mean?
Tags published by LVSTestLabo, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. 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 LVSTestLabo?
These Rust Metrics lists carry LVSTestLabo: 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 3 days.
Player count
What position does LVSTestLabo hold among Rust servers?
Ranking for LVSTestLabo: #15,019 on seven-day player hours, top 67% of all ranked servers.
What is the population on LVSTestLabo?
Current headcount on LVSTestLabo: 0 players, 100 slots available. Seven-day check: 0 players on average. Peak reading: 1. The last 48 hours peaked at 14:00 UTC, averaging 0 players at that hour.
Operator and location
Which location does LVSTestLabo run from?
No region tag on LVSTestLabo. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 82.21.2.12:10255.
What Rust version is LVSTestLabo on?
Reading: LVSTestLabo, Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.
Is performance on LVSTestLabo within range?
Check: fps. Average 21 server fps over the last 48 hours, low of 10. Within range. Reading: 57,158 entities at the highest. That covers buildings, deployables and everything else. Reading: 2,461 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.
What is the uptime on LVSTestLabo, and is it online?
LVSTestLabo reports online. Status: normal. Reading: uptime. About 8 hours ago it restarted, on its own count. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Rules and settings
What rules does LVSTestLabo enforce, and what are its settings?
No gather rate appears in the name: LVSTestLabo. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.
What map is LVSTestLabo on?
Size 3,000 and seed 1: the game generates the procedural map on LVSTestLabo from them. The map repeats when size and seed match. Open it on RustMaps from this page.
Join
What do you do to join LVSTestLabo?
To join: start Rust, press F1 and type client.connect 82.21.2.12:10255. Or press Launch Rust here and Steam opens the game and connects you. You can find its website at https://discord.com/invite/d9KAwDeRAP.