RUST METRICSFlight deck · live data
Data live Servers11,636 Players31,247 Populated2,768 Fresh wipes 3 h72 Scan5 min
‹ All servers109.254.23.88:28015
Online Full Queue Fresh wipe Wipe due No query

SAKUTIDE RUST | x0.5/x1 | WEEKLY

Online 109.254.23.88:28015 checked 12m ago

0.5x moddedcarbon
COM 1 · connect

Server instruments

last reading Thu 04:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 137 SERVER FPS

Server fps

48 h low 59 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 95,187 ×1000

Entities

48 h range 36,693–97,415 · memory 2,989 MB
1239 ET SINCE RESTART 09:24

Uptime

9 h 24 min since its last restart, at the last reading
7-day average0peak 1
Rank#5,657top 25%
Last wipe10h agono schedule published
Next wipe–no rhythm it keeps
Memory2,989MB48 h peak 1 players
REC 1

Players

AveragePeakWipe
00.250.50.75106:0013:0020:0012:0021:0004:00Wiped Wed 28 Oct, 16:10 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
010020030040006:0013:0020:0012:0021:0004:00Wiped Wed 28 Oct, 16:10 UTCWIPE

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 20 Oct. 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 Oct22 Oct24 Oct25 Oct27 Oct29 Oct

Top 25% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Thu 22 OctTue 20 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 28 Oct, 16:10 UTC13h ago – – running 1
Thu 22 Oct, 19:47 UTC6d ago 1 held half 5.8 days 0
Tue 20 Oct, 18:20 UTC8d ago 1 held half 2.1 days 1

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 SAKUTIDE RUST | x0.5/x1 | WEEKLY?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in. Until the next wipe, the crowd stayed above half that peak in 100% of its recent wipes.

How often does SAKUTIDE RUST | x0.5/x1 | WEEKLY wipe, and when?

There is no next wipe to predict: SAKUTIDE RUST | x0.5/x1 | WEEKLY wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 10 hours ago.

Tags

How should you read the tags on SAKUTIDE RUST | x0.5/x1 | WEEKLY?

Tags published by SAKUTIDE RUST | x0.5/x1 | WEEKLY, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^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 SAKUTIDE RUST | x0.5/x1 | WEEKLY appear in Rust Metrics lists and filters?

Rust Metrics lists featuring SAKUTIDE RUST | x0.5/x1 | WEEKLY: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 24 hours.

Population

What position does SAKUTIDE RUST | x0.5/x1 | WEEKLY hold among Rust servers?

Ranking for SAKUTIDE RUST | x0.5/x1 | WEEKLY: #5,657 on seven-day player hours, top 25% of all ranked servers.

What is the population on SAKUTIDE RUST | x0.5/x1 | WEEKLY?

Current headcount on SAKUTIDE RUST | x0.5/x1 | WEEKLY: 0 players, 50 slots available. Seven-day check: 0 players on average. Peak reading: 1. The last 48 hours peaked at 09:00 UTC, averaging 1 players at that hour.

Operator and location

Where does SAKUTIDE RUST | x0.5/x1 | WEEKLY sit?

No region tag on SAKUTIDE RUST | x0.5/x1 | WEEKLY. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 109.254.23.88:28015.

What Rust version is SAKUTIDE RUST | x0.5/x1 | WEEKLY on?

Rust network protocol 2635 and build 168909 on Windows is the build SAKUTIDE RUST | x0.5/x1 | WEEKLY runs. To get in, your game needs the same protocol; Steam applies the update.

How does SAKUTIDE RUST | x0.5/x1 | WEEKLY perform?

Reading: 204 server fps on average across the last 48 hours. It never dropped below 59. Check: entities. The peak was 97,415, counting buildings, deployables and the rest of the world. Reading: 2,989 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

Is SAKUTIDE RUST | x0.5/x1 | WEEKLY up, and how often does it stay up?

Reading: online. SAKUTIDE RUST | x0.5/x1 | WEEKLY answers right now. By its reported uptime, the last restart was roughly 9 hours ago. Reading: 67% uptime over the last 7 full days. It was up 113 of 168 hours. Reading: first seen 20 October 2026, recorded by Rust Metrics.

Rules and settings

What rules does SAKUTIDE RUST | x0.5/x1 | WEEKLY enforce, and what are its settings?

Gather rate check: 0.5x. That comes from the name SAKUTIDE RUST | x0.5/x1 | WEEKLY. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Plugin count: Carbon. Anti-cheat reading: VAC on, Valve's system.

Which map is live on SAKUTIDE RUST | x0.5/x1 | WEEKLY?

From seed 281026, the game generates the procedural map on SAKUTIDE RUST | x0.5/x1 | WEEKLY. Its size is 4,000. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

How can you get onto SAKUTIDE RUST | x0.5/x1 | WEEKLY?

Press F1 in Rust and enter client.connect 109.254.23.88:28015. 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?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players The server holds 50 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.