RUST METRICSFlight deck · live data
Data live Servers11,704 Players60,571 Populated3,281 Fresh wipes 3 h172 Scan5 min
‹ All servers188.143.83.131:28115
Offline Full Queue Fresh wipe Wipe due No query

MantaScope Rust test

Offline 188.143.83.131:28115 checked 35d 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,089top 71%
Last wipe35d 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
15k10k15k20k24 Sep25 Sep27 Sep28 Sep30 Sep1 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

Reset cycle

What wipe timing does MantaScope Rust test follow?

The rhythm of MantaScope Rust test's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 35 days 1 hours ago.

Tags

How should you read the tags on MantaScope Rust test?

Tags published by MantaScope Rust test, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. 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 MantaScope Rust test?

On Rust Metrics, MantaScope Rust test sits in these lists: 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.

Player count

Where does MantaScope Rust test sit in the rankings?

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

How full does MantaScope Rust test get?

Status for MantaScope Rust test: offline. Last seen 35 days 1 hours ago.

Operator and location

What location is MantaScope Rust test hosted in?

Reading: location. MantaScope Rust test gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 188.143.83.131:28115.

What Rust version is MantaScope Rust test on?

Rust network protocol 2633 and build 165217 on Linux is the build MantaScope Rust test runs. To get in, your game needs the same protocol; Steam applies the update.

Is MantaScope Rust test up, and how often does it stay up?

MantaScope Rust test reports offline. The last reading came 35 days 1 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 24 September 2026.

Map and rules

What settings and rules apply on MantaScope Rust test?

Check: gather rate. The name MantaScope Rust test does not state one. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Anti-cheat reading: VAC off, Valve's system.

Which map is live on MantaScope Rust test?

The game generates a procedural map for MantaScope Rust test.

How to join

What do you do to join MantaScope Rust test?

Check: join. Open Rust, press F1, then enter client.connect 188.143.83.131: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 The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build Build 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.