RUST METRICSFlight deck · live data
Data live Servers11,726 Players64,279 Populated3,337 Fresh wipes 3 h199 Scan5 min
‹ All servers202.189.15.63:6221
Offline Full Queue Fresh wipe Wipe due No query

坐牢1.0

Offline 202.189.15.63:6221 checked 11d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 4 6 8 PAX 0 /8

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,248top 69%
Last wipe27d 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
15k10k15k20k20 Sep27 Sep4 Oct11 Oct18 Oct25 Oct

Top 69% 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
Fri 2 Oct, 06:02 UTC27d 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 坐牢1.0 when wipe day comes?

At their busiest, its recent wipes drew 0 players on average. Peak crowd on the latest wipe: 0 hours in.

What wipe timing does 坐牢1.0 follow?

To tell the rhythm of 坐牢1.0, too few of its wipes 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 27 days 17 hours ago.

Tag meanings

How should you read the tags on 坐牢1.0?

Tags published by 坐牢1.0, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp8 (Max players): 8 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166494 (Build): Game build reading: 166494; 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 坐牢1.0?

Rust Metrics lists featuring 坐牢1.0: Rust community servers: live readings. Check: filters. On the server list it appears under these: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does 坐牢1.0 hold among Rust servers?

Ranking for 坐牢1.0: #15,248 on seven-day player hours, top 69% of all ranked servers.

What is the population on 坐牢1.0?

Status for 坐牢1.0: offline. Last seen 11 days 1 hours ago.

Server details

Where does 坐牢1.0 sit?

Reading: location. Nothing in the tags, but the name of 坐牢1.0 points to Asia. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 202.189.15.63:6221.

What Rust version is 坐牢1.0 on?

Reading: 坐牢1.0, Rust network protocol 2634 and build 166494, Linux. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on 坐牢1.0, and is it online?

坐牢1.0 reports offline. The last reading came 11 days 1 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 19 September 2026.

Settings and map

What rules does 坐牢1.0 enforce, and what are its settings?

No gather rate appears in the name: 坐牢1.0. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on 坐牢1.0?

The game generates a procedural map for 坐牢1.0.

Join

How do you connect to 坐牢1.0?

Press F1 in Rust and enter client.connect 202.189.15.63:6221. 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 mp8,ptrak,$r?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp8
Max players 8 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166494
Build Game build reading: 166494.
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.