Rust Data

rustdata.spaceservers82.21.2.12:10412.ipynb

Run all rust-data · live

‹ All servers

Online 82.21.2.12:10255 checked 12m ago

LVSTestLabo

moddedoxide

Connect

srv = rust.server("82.21.2.12:10412")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak 1
rank #15,023 # top 68%
last wipe 1d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeakWipe
00.250.50.75122:0007:0016:0001:0010:0020:00Wiped Tue 27 Oct, 11:04 UTCWIPE

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
Server fpsWipe
010020030040022:0007:0016:0001:0010:0020:00Wiped Tue 27 Oct, 11:04 UTCWIPE

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 best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 68% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap16.9 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 8.5

The first 48 hours of its last wipes

Mon 5 OctThu 1 OctMon 14 Sep
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 26 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 27 Oct, 11:04 UTC1d ago NaN NaN running 0
1 Mon 5 Oct, 10:03 UTC23d ago 3 halved by day 2 22 days 0
2 Thu 1 Oct, 19:49 UTC FW27d ago 0 NaN 3.6 days 0
3 Mon 14 Sep, 22:09 UTC43d 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.

display(srv.map, srv.info())

Map

3000 · seed 1
Map of LVSTestLabo
map
Procedural Map
size
3000
seed
1
Open on RustMaps

Server

srv.info()
address
82.21.2.12:10255
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
27 Oct 2026, 13:34 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 157 on average98/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average123/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average101/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 91 on average87/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average29/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average21/1000

Quick answers

From the figures on this page.

Player counts

What position does LVSTestLabo take in the server rankings?

Rank #15,023 on seven-day player hours for LVSTestLabo, within the top 68% of all ranked servers.

How full does LVSTestLabo run?

The sample now reads 0 players for LVSTestLabo, out of 100 slots. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 14:00 UTC is the busiest, at 0 players.

Server facts

How well does LVSTestLabo perform?

Server fps over the last 48 hours averages 21; the floor is 10. Entity numbers reached 57,294, and that includes buildings, deployables and the rest. Memory peaked at 2,465 MB. Low fps plus an entity count on the way up is the lag players report.

What Rust version does LVSTestLabo run?

Version Rust network protocol 2635 and build 168909 on Linux is reported by LVSTestLabo. The protocol has to match before you can join, and Steam does the updating.

Is LVSTestLabo up, and what does its uptime show?

LVSTestLabo reports itself online at the current refresh. Count back 10 hours from its reported uptime to get the last restart. Uptime of 100% across the last 7 full days: 168 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

In which location is LVSTestLabo hosted?

No region is published by LVSTestLabo. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 82.21.2.12:10255 is its address.

Rules, settings, map

What rules and settings are recorded for LVSTestLabo?

The name LVSTestLabo carries no gather rate. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.

What is the map on LVSTestLabo?

The game generates the map on LVSTestLabo: procedural, size 3,000, seed 1. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe schedule

On what schedule does LVSTestLabo wipe?

Irregular wipe times on LVSTestLabo leave no next wipe to forecast. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 32 hours ago.

On LVSTestLabo, what happens on wipe day?

Across recent wipes the busiest point averaged 2 players. Peak population on the latest wipe came 26 hours in. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. In the wipes where it did not hold, half was lost by day 8.5.

Tags, lists

Which Rust Data filters and lists contain LVSTestLabo?

The Rust Data lists that LVSTestLabo fits are: Modded Rust servers. It appears under these filters 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.

How should you read the server tags on LVSTestLabo?

Read by the game's server browser, the tags LVSTestLabo publishes are: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way into LVSTestLabo?

The manual route: launch Rust, F1, then client.connect 82.21.2.12:10255. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. https://discord.com/invite/d9KAwDeRAP is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp100
Max players 100 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded The Modded section lists it, because plugins or settings change the game.

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.

Rust Data 67,584 players 11,791 servers online