RUST METRICSFlight deck · live data
Data live Servers11,834 Players79,225 Populated3,875 Fresh wipes 3 h158 Scan5 min
‹ All servers58.3.111.187:28015
Offline Full Queue Fresh wipe Wipe due No query

MashuSaba

Offline 58.3.111.187:28015 checked 35d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 2 /500

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,506top 67%
Last wipe36d 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, measured since 22 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k21 Sep23 Sep25 Sep26 Sep28 Sep30 Sep

Top 67% 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 MashuSaba wipe, and when?

Its rhythm cannot be told from the wipes of MashuSaba on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 36 days 10 hours ago the current world was made.

Lists and filters

Which tags does MashuSaba carry, and what do they mean?

These are the tags MashuSaba publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): 500 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): Game build reading: 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does MashuSaba appear in Rust Metrics lists and filters?

On Rust Metrics, MashuSaba sits in these lists: 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 MashuSaba hold among Rust servers?

Ranking for MashuSaba: #15,506 on seven-day player hours, top 67% of all ranked servers.

What player count does MashuSaba carry?

MashuSaba is not responding; status offline, last seen 35 days 17 hours ago.

Server

Which location does MashuSaba run from?

No region comes from MashuSaba. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 58.3.111.187:28015.

What Rust version is MashuSaba on?

Reading: MashuSaba, Rust network protocol 2633 and build 164530, Windows. Check: protocol. To join, your game must match; Steam handles the update.

Is MashuSaba up, and how often does it stay up?

Check: connection. MashuSaba is offline at this moment. Last contact was 35 days 17 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 21 September 2026, recorded by Rust Metrics.

Rules and settings

What rules does MashuSaba enforce, and what are its settings?

Reading the name gives no gather rate for MashuSaba. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is MashuSaba on?

From seed 1234567, the game generates the procedural map on MashuSaba. Its size is 4,500. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

What do you do to join MashuSaba?

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

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2633,gmrust,cs164530,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players 500 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs164530
Build Game build reading: 164530.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.