RUST METRICSFlight deck · live data
Data live Servers11,855 Players100,368 Populated3,884 Fresh wipes 3 h533 Scan5 min
‹ All servers126.95.141.182:28315
Offline Full Queue Fresh wipe Wipe due No query

のぐそのしま(PVE)

Offline 126.95.141.182:28315 checked 28d ago

moddedcarbonpve
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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,408top 69%
Last wipe55d 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 17 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
15k10k15k20k20 Sep24 Sep27 Sep1 Oct4 Oct8 Oct

Top 69% 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 のぐそのしま(PVE) follow?

Its rhythm cannot be told from the wipes of のぐそのしま(PVE) 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. 55 days 11 hours ago the current world was made.

Tag meanings

Which tags does のぐそのしま(PVE) carry, and what do they mean?

These are the tags のぐそのしま(PVE) publishes, and the server browser reads them: gmvanilla (Game mode): Survival on vanilla settings; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): The server runs game build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Carbon handles the plugins here. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does のぐそのしま(PVE) appear in Rust Metrics lists and filters?

Rust Metrics lists featuring のぐそのしま(PVE): Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more.

Population

What position does のぐそのしま(PVE) hold among Rust servers?

Player hours over seven days put のぐそのしま(PVE) at #16,408, in the top 69% of all ranked servers.

What player count does のぐそのしま(PVE) carry?

のぐそのしま(PVE) is not responding; status offline, last seen 28 days 5 hours ago.

Server

Which location does のぐそのしま(PVE) run from?

The name of のぐそのしま(PVE) points to Asia, though it publishes no region tag. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 126.95.141.182:28315.

What Rust version is のぐそのしま(PVE) on?

Version check: Rust network protocol 2633 and build 165217 on Windows, run by のぐそのしま(PVE). To get in, your game needs the same protocol; Steam applies the update.

How reliable is のぐそのしま(PVE), and is it online now?

Check: connection. のぐそのしま(PVE) is offline at this moment. Last contact was 28 days 5 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Map and rules

What rules does のぐそのしま(PVE) enforce, and what are its settings?

Check: gather rate. The name のぐそのしま(PVE) does not state one. 8 players per group, the default value. Mode check gives pve; other players are not fought. Plugins or settings change the game, so it is listed as Modded. Carbon plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is のぐそのしま(PVE) on?

From seed 810514, the game generates the procedural map on のぐそのしま(PVE). Its size is 4,000. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

How can you get onto のぐそのしま(PVE)?

Press F1 in Rust and enter client.connect 126.95.141.182:28315. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,^z,^y,^p,gmvanilla,cs165217,ts8

Game

gmvanilla
Game mode Survival on vanilla settings.
mp50
Max players 50 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build The server runs game build 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Gameplay

^p
PvE There is no player-on-player combat here; the danger comes from the world.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Carbon handles the plugins here.

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.