Rust Data LabData lab · live
Live readings Servers11,835 Players82,642 Populated3,762 Fresh wipes · 3h274 Sampled every 5 min

Element card · group Community · atomic number 16,000, its rank

Sakuya lib

Offline 49.215.58.62:28015 checked 25d ago

Join the experiment
Atomic mass · players now 0/ 20 0% full Room to join
7-day average0peak –
Rank · atomic number#16,000top 71%
Last wipe25d agono schedule published
Next wipe–too few wipes seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
No hourly history yet.

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
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.

Result 03

Rank

Result

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.

Reaction kinetics

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.

Reaction 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Ru Rusty Moose |E… 538
    Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 514 on average 538/ 575
  2. 2 Ru Rustoria.co - … 430
    Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average 430/ 475
  3. 3 Ru Rusty Moose |E… 167
    Rusty Moose |EU Main| EU · groups of 12+ · weekly · 290 on average 167/ 250
  4. 4 Ru Rustafied.com … 57
    Rustafied.com - EU Friday EU · groups of 16+ · weekly · 275 on average 57/ 100
  5. 5 Ru Rustoria.co - … 221
    Rustoria.co - EU Main EU · groups of 16+ · weekly · 275 on average 221/ 250
  6. 6 Ru Rustoria.co - … 304
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 236 on average 304/ 350

Quick answers

from the figures on this page

Server setup

What map is in play on Sakuya lib?

The map on Sakuya lib is procedural, made by the game.

How is Sakuya lib configured, and what rules apply?

Nothing in the name of Sakuya lib gives a gather rate. Groups top out at 8 players, the default for the game. Play runs as survival, gather, build and raid, as in the standard game. Raids and player fights are part of play here. The server browser lists it under Community. The VAC anti-cheat from Valve is enabled.

Server details

What region hosts Sakuya lib?

No region is published by Sakuya lib. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. 49.215.58.62:28015 is the address it uses.

Which Rust version is Sakuya lib on?

On Windows, Sakuya lib is running Rust network protocol 2634 and build 166652. Joining requires the same protocol on your game; Steam takes care of updating it.

How dependable is Sakuya lib for staying online?

Right now Sakuya lib is offline, with its last appearance 25 days 5 hours ago. For the last 7 full days, 0 of 168 hours were online, giving 0% uptime. It first appeared to Rust Data Lab on 4 October 2026.

Wipes and resets

What is the wiping pattern on Sakuya lib?

The record holds too few of Sakuya lib's wipes to show its rhythm. The monthly force wipe resets every Rust server; it next occurs on Thursday 5 November at 19:00 UTC. The world it is running now dates from 25 days 5 hours ago.

On Sakuya lib, what happens when wipe day arrives?

Averaged across its recent wipes, the busiest point drew 0 players. The latest wipe's peak fell 0 hours after it began.

Where it appears

How should you read the tags on Sakuya lib?

The game's server browser reads the tags Sakuya lib publishes, which are gmrust (Game mode): Survival in the standard Rust style; mp20 (Max players): Player slots: 20; ts8 (Group limit): This uses the game's default: 8 per team; v2634 (Protocol): Protocol 2634 is required; join only if your game matches it; cs166652 (Build): The game build is 166652; ptrak (Networking): This runs on RakNet, the standard layer; $r? (Region code): No region code is set. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

Where among the Rust Data Lab lists and filters does Sakuya lib come up?

The Rust Data Lab lists that include Sakuya lib are: Rust community servers, measured. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Against other Rust servers, where does Sakuya lib place?

The seven-day player-hours table has Sakuya lib at #16,000, in the top 71% of ranked servers.

How many players does Sakuya lib have at the moment?

The last recorded sighting of Sakuya lib was 25 days 5 hours ago, and it is offline now.

Connection

How can you connect to Sakuya lib?

Open the console with F1 in Rust and type client.connect 49.215.58.62:28015. The Launch Rust button on this page does the same job through Steam.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust style.
mp20
Max players Player slots: 20.
ts8
Group limit This uses the game's default: 8 per team.
v2634
Protocol Protocol 2634 is required; join only if your game matches it.
cs166652
Build The game build is 166652.
ptrak
Networking This runs on RakNet, the standard 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.