RUST METRICSFlight deck · live data
Data live Servers11,837 Players77,657 Populated3,729 Fresh wipes 3 h257 Scan5 min
‹ All servers85.238.80.163:28115
Offline Full Queue Fresh wipe Wipe due No query

MantaScope Rust test

Offline 85.238.80.163:28115 checked 34d ago

COM 1 · connect

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#16,269top 71%
Last wipe34d 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
15k10k15k20k25 Sep26 Sep28 Sep29 Sep1 Oct2 Oct

Top 71% 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

What wipe timing does MantaScope Rust test follow?

Its rhythm cannot be told from the wipes of MantaScope Rust test on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 34 days 15 hours ago.

Tags

How should you read the tags on MantaScope Rust test?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Game build reading: 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty from MantaScope Rust test. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show MantaScope Rust test?

These Rust Metrics lists carry MantaScope Rust test: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does MantaScope Rust test hold among Rust servers?

Player hours over seven days put MantaScope Rust test at #16,269, in the top 71% of all ranked servers.

What is the population on MantaScope Rust test?

MantaScope Rust test is not responding; status offline, last seen 34 days 3 hours ago.

Server

Which location does MantaScope Rust test run from?

No region tag on MantaScope Rust test. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 85.238.80.163:28115.

What Rust version is MantaScope Rust test on?

Version check: Rust network protocol 2633 and build 165217 on Linux, run by MantaScope Rust test. To get in, your game needs the same protocol; Steam applies the update.

How reliable is MantaScope Rust test, and is it online now?

Check: connection. MantaScope Rust test is offline at this moment. Last contact was 34 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 25 September 2026, recorded by Rust Metrics.

Map and rules

What rules does MantaScope Rust test enforce, and what are its settings?

No gather rate appears in the name: MantaScope Rust test. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is off.

What map is MantaScope Rust test on?

Check: map. Procedural, generated by the game, on MantaScope Rust test.

Join

How can you get onto MantaScope Rust test?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build Game build reading: 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

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.