RUST METRICSFlight deck · live data
Data live Servers11,814 Players69,594 Populated3,624 Fresh wipes 3 h187 Scan5 min
‹ All servers51.91.242.62:28100
Offline Full Queue Fresh wipe Wipe due No query

LushMap test

Offline 51.91.242.62:28100 checked 18d ago

moddedoxide
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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#15,826top 72%
Last wipe18d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k11 Oct12 Oct14 Oct15 Oct17 Oct18 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

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

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 11 Oct, 04:48 UTC18d ago 0 – running 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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Reset cycle

What happens on LushMap test when wipe day comes?

The busiest point of its recent wipes drew 0 players on average. Peak crowd on the latest wipe: 0 hours in.

When does LushMap test wipe?

The rhythm of LushMap test's wipes cannot be told yet: too few 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. The world in play was created 18 days 2 hours ago.

Tag meanings

Which tags does LushMap test carry, and what do they mean?

These are the tags LushMap test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167398 (Build): Game build reading: 167398; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock 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 LushMap test?

These Rust Metrics lists carry LushMap test: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

What position does LushMap test hold among Rust servers?

Player hours over seven days put LushMap test at #15,826, in the top 72% of all ranked servers.

What is the population on LushMap test?

Reading for LushMap test: offline at this moment; last seen 18 days 2 hours ago.

Server details

Where does LushMap test sit?

Reading: location. LushMap test gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 51.91.242.62:28100.

What Rust version is LushMap test on?

Rust network protocol 2634 and build 167398 on Linux is the build LushMap test runs. Matching protocol is required to join. Let Steam update your game.

What is the uptime on LushMap test, and is it online?

LushMap test reports offline. The last reading came 18 days 2 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 11 October 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on LushMap test?

Reading the name gives no gather rate for LushMap test. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

Connection

What do you do to join LushMap test?

To join: start Rust, press F1 and type client.connect 51.91.242.62:28100. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167398
Build Game build reading: 167398.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock 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.