RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h18 Scan5 min
‹ All servers162.43.37.158:28015
Online Full Queue Fresh wipe Wipe due No query

yubisake fingers

Online 162.43.37.158:28015 checked 2h ago

COM 1 · connect

Server instruments

last reading Wed 17:00 UTC
0 1.2 2.5 3.8 5 PAX 0 /5

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS 236 SERVER FPS

Server fps

48 h low 135 · below 20 is lag, below 10 is bad
0 5 10 15 20 ENT 4,941 ×1000

Entities

48 h range 4,862–7,157 · memory 1,258 MB
1239 ET SINCE RESTART 10D 21H

Uptime

10 days 21 hours since its last restart, at the last reading
7-day average0peak –
Rank#15,373top 69%
Last wipe19d agono schedule published
Next wipe–too few wipes seen yet
Memory1,258MBat the last reading
REC 1

Players

AveragePeak
0123420:0005:0014:0023:0008:0017:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040020:0005:0014:0023:0008:0017:00

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 Sep28 Sep5 Oct13 Oct20 Oct28 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.

usual gap19.3 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Thu 8 OctSat 19 Sep
00.250.50.751+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
Thu 8 Oct, 21:23 UTC19d ago 0 – running 0
Sat 19 Sep, 14:26 UTC39d ago 2 halved by day 1 19.3 days 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 should you expect from wipe day on yubisake fingers?

The busiest point of its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. It fell below half by day 1 when it didn't.

When does yubisake fingers wipe?

To tell the rhythm of yubisake fingers, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 19 days 22 hours ago the current world was made.

Tag meanings

How should you read the tags on yubisake fingers?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): The server runs game build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from yubisake fingers. 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 yubisake fingers?

Rust Metrics lists featuring yubisake fingers: 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

Where does yubisake fingers sit in the rankings?

Ranking for yubisake fingers: #15,373 on seven-day player hours, top 69% of all ranked servers.

How full does yubisake fingers get?

Current headcount on yubisake fingers: 0 players, 5 slots available. Seven-day reading: 0 players on average.

Server

Which location does yubisake fingers run from?

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

What Rust version is yubisake fingers on?

Version check: Rust network protocol 2634 and build 167781 on Linux, run by yubisake fingers. To get in, your game needs the same protocol; Steam applies the update.

Is performance on yubisake fingers within range?

Over the last 48 hours the average was 230 server fps; the floor was 135. Reading: 7,157 entities at the highest. That covers buildings, deployables and everything else. Reading: 1,410 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.

How reliable is yubisake fingers, and is it online now?

yubisake fingers reports online. Status: normal. Reading: uptime. About 10 days 21 hours ago it restarted, on its own count. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Rules and settings

What settings and rules apply on yubisake fingers?

No gather rate appears in the name: yubisake fingers. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. 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 yubisake fingers?

Check: map. Procedural, size 1,500, seed 34567, generated by the game on yubisake fingers. View it on RustMaps from this page: matching size and seed give an identical map.

How to join

How can you get onto yubisake fingers?

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

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players The server holds 5 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build The server runs game build 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none 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.