RUST METRICSFlight deck · live data
Data live Servers11,830 Players74,645 Populated3,703 Fresh wipes 3 h224 Scan5 min
‹ All servers49.215.58.62:28015
Offline Full Queue Fresh wipe Wipe due No query

Sakuya lib

Offline 49.215.58.62:28015 checked 25d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 5 10 15 20 PAX 0 /20

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,000top 71%
Last wipe25d 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
15k10k15k20k4 Oct5 Oct7 Oct8 Oct10 Oct11 Oct

Top 71% 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
Sun 4 Oct, 08:48 UTC25d 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

Wipe timing

What should you expect from wipe day on Sakuya lib?

An average of 0 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does Sakuya lib follow?

To tell the rhythm of Sakuya lib, 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 it runs now was made 25 days 5 hours ago.

Tags

Which tags does Sakuya lib carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp20 (Max players): The server holds 20 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): The server runs game build 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from Sakuya lib. 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 Sakuya lib?

These Rust Metrics lists carry Sakuya lib: 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 Sakuya lib hold among Rust servers?

Ranking for Sakuya lib: #16,000 on seven-day player hours, top 71% of all ranked servers.

How full does Sakuya lib get?

Status for Sakuya lib: offline. Last seen 25 days 4 hours ago.

Server

Which location does Sakuya lib run from?

No region tag on Sakuya lib. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 49.215.58.62:28015.

What Rust version is Sakuya lib on?

Reading: Sakuya lib, Rust network protocol 2634 and build 166652, Windows. Matching protocol is required to join. Let Steam update your game.

How reliable is Sakuya lib, and is it online now?

Reading: offline. Sakuya lib last answered 25 days 4 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 4 October 2026.

Rules and settings

How is Sakuya lib configured, and what rules are in force?

Reading the name gives no gather rate for Sakuya lib. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Sakuya lib?

Procedural map on Sakuya lib, made by the game's generator.

Connection

How can you get onto Sakuya lib?

To join: start Rust, press F1 and type client.connect 49.215.58.62:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp20,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp20
Max players The server holds 20 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build The server runs game build 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.