RUST METRICSFlight deck · live data
Data live Servers11,699 Players51,000 Populated3,284 Fresh wipes 3 h139 Scan5 min
‹ All servers46.188.26.22:28015
Offline Full Queue Fresh wipe Wipe due No query

Moscow Classic Lab's

Offline 46.188.26.22:28015 checked 42d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 62 125 188 250 PAX 1 /250

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#13,288no region published
Last wipe42d 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
15k10k15k20k20 Sep21 Sep22 Sep
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 schedule

How often does Moscow Classic Lab's wipe, and when?

Its rhythm cannot be told from the wipes of Moscow Classic Lab's on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 42 days 14 hours ago.

Lists and filters

Which tags does Moscow Classic Lab's carry, and what do they mean?

Tags published by Moscow Classic Lab's, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp250 (Max players): The server holds 250 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Game build reading: 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. 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 Moscow Classic Lab's?

Rust Metrics lists featuring Moscow Classic Lab's: 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 Moscow Classic Lab's hold among Rust servers?

Player hours over seven days put Moscow Classic Lab's at #13,288, in the top – of all ranked servers.

What player count does Moscow Classic Lab's carry?

Moscow Classic Lab's is not responding; status offline, last seen 42 days 10 hours ago.

Server details

What location is Moscow Classic Lab's hosted in?

No region tag on Moscow Classic Lab's. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 46.188.26.22:28015.

What Rust version is Moscow Classic Lab's on?

Rust network protocol 2633 and build 163794 on Windows is the build Moscow Classic Lab's runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is Moscow Classic Lab's, and is it online now?

Check: connection. Moscow Classic Lab's is offline at this moment. Last contact was 42 days 10 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 15 September 2026, recorded by Rust Metrics.

Settings and map

How is Moscow Classic Lab's configured, and what rules are in force?

Check: gather rate. The name Moscow Classic Lab's does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Moscow Classic Lab's?

Check: map. Procedural, generated by the game, on Moscow Classic Lab's.

How to join

What do you do to join Moscow Classic Lab's?

Check: join. Open Rust, press F1, then enter client.connect 46.188.26.22:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp250,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp250
Max players The server holds 250 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build Game build reading: 163794.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none 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.