Rust Server TrendsSeismic network · station log
Recording Stations11,855 Players81,723 Active3,800 Wipes · 3 h365 48 h

Station XX-3750 · recording

GUILD_SAGI_NI_CHUI

Online 160.251.253.155:28015 checked 6m ago

moddedoxide
Connect
Players now
0/ 16
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
1
peak 6
Rank
#3,750
top 17%
Last wipe
27d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-3750 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 16 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
−1into Wed 08:00 UTC
Peak · 48 h
1most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.250.50.75116:0001:0010:0019:0004:0013:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020016:0001:0010:0019:0004:0013: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 24 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k24 Sep1 Oct8 Oct15 Oct22 Oct29 Oct

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

Expected events

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 gap
3.5 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
7players, last three wipes
crowd held
100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 2 OctSun 27 SepFri 25 Sep
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 7, 2 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 2 Oct, 10:39 UTC27d ago M0.8rising 7 – running 0
Sun 27 Sep, 11:58 UTC32d ago M0.3rising 7 held half 4.9 days 5
Fri 25 Sep, 12:33 UTC34d ago M0.8rising 7 – 2 days 1

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 149 on average
181/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
123/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
172/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 94 on average
85/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 86 on average
176/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 86 on average
237/ 700
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on GUILD_SAGI_NI_CHUI?

Generated by the game, the map on GUILD_SAGI_NI_CHUI is procedural, size 2,700 with seed 28287. You can view it on RustMaps from this page: the same size and seed produce the same map. Its map carries the name Custom Map.

Which settings and rules apply on GUILD_SAGI_NI_CHUI?

You will find no gather rate in the name of GUILD_SAGI_NI_CHUI. At the game's default, groups can have up to 8 players. It plays in survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.

Player counts

What is the current population on GUILD_SAGI_NI_CHUI?

0 of the 16 slots on GUILD_SAGI_NI_CHUI are filled right now. Averaged across the last seven days the population was 1 players, reaching a peak of 6. Averaged over the last 48 hours, the busiest hour was 07:00 UTC at 1 players.

How does GUILD_SAGI_NI_CHUI rank against other Rust servers?

On player hours for the past week, GUILD_SAGI_NI_CHUI sits at #3,750, which puts it inside the top 17% of every ranked server.

Operator and location

How reliably does GUILD_SAGI_NI_CHUI stay online?

GUILD_SAGI_NI_CHUI is up at the moment. The uptime it reports puts its last restart about 6 days 2 hours ago. Of the 168 hours in the last 7 full days, it was up for 167, or 99% of the time. Its earliest appearance in the records of Rust Server Trends dates to 24 September 2026.

How well does GUILD_SAGI_NI_CHUI perform under load?

Across the last 48 hours it averaged 140 server fps, with a floor of 95. Buildings, deployables and all the rest of the world's entities brought it to a high of 73,835. It reached a ceiling of 4,297 MB of memory. What you feel as lag is the combination of low fps and a rising entity count.

Where in the world is GUILD_SAGI_NI_CHUI hosted?

No region is published by GUILD_SAGI_NI_CHUI. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 160.251.253.155:28015.

Which Rust version is GUILD_SAGI_NI_CHUI running?

On Linux, GUILD_SAGI_NI_CHUI runs Rust network protocol 2635 and build 168909. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

What does wipe day look like on GUILD_SAGI_NI_CHUI?

The recent wipes averaged a busiest count of 7 players. 2 hours into the latest wipe, the crowd reached its peak. Until the next wipe the crowd remained above half that peak in 100% of its recent wipes.

On what timetable does GUILD_SAGI_NI_CHUI run its wipes?

No next wipe can be predicted for GUILD_SAGI_NI_CHUI, which wipes at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 27 days 4 hours.

Server tags

What do the server tags on GUILD_SAGI_NI_CHUI mean?

These are the tags GUILD_SAGI_NI_CHUI publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp16 (Max players): The server has 16 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does GUILD_SAGI_NI_CHUI appear?

You will find GUILD_SAGI_NI_CHUI on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Connecting

What steps get you onto GUILD_SAGI_NI_CHUI?

You can connect by pressing F1 in Rust and typing client.connect 160.251.253.155:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp16,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
mp16
Max players The server has 16 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build It runs game build 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code No region code is set for this server.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.