RUST METRICSFlight deck · live data
Data live Servers11,674 Players57,845 Populated3,415 Fresh wipes 3 h98 Scan5 min
‹ All servers88.8.48.212:28015
Offline Full Queue Fresh wipe Wipe due No query

[LAB] testing 1337

Offline 88.8.48.212:28015 checked 27d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#16,699top 70%
Last wipe27d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k30 Sep1 Oct3 Oct4 Oct6 Oct7 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

How often does [LAB] testing 1337 wipe, and when?

To tell the rhythm of [LAB] testing 1337, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 27 days 15 hours ago the current world was made.

Tags

How should you read the tags on [LAB] testing 1337?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): The server runs game build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from [LAB] testing 1337. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show [LAB] testing 1337?

Rust Metrics lists featuring [LAB] testing 1337: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does [LAB] testing 1337 hold among Rust servers?

Ranking for [LAB] testing 1337: #16,699 on seven-day player hours, top 70% of all ranked servers.

What player count does [LAB] testing 1337 carry?

Status for [LAB] testing 1337: offline. Last seen 27 days 12 hours ago.

Operator and location

Which location does [LAB] testing 1337 run from?

No region tag on [LAB] testing 1337. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 88.8.48.212:28015.

What Rust version is [LAB] testing 1337 on?

Reading: [LAB] testing 1337, Rust network protocol 2633 and build 165217, Linux. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on [LAB] testing 1337, and is it online?

Reading: offline. [LAB] testing 1337 last answered 27 days 12 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 30 September 2026, recorded by Rust Metrics.

Settings and map

What rules does [LAB] testing 1337 enforce, and what are its settings?

Reading the name gives no gather rate for [LAB] testing 1337. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

What map is [LAB] testing 1337 on?

Procedural map on [LAB] testing 1337, made by the game's generator.

How to join

What do you do to join [LAB] testing 1337?

Press F1 in Rust and enter client.connect 88.8.48.212:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build The server runs game build 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

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.