Rust HeatmapInfrared · players
IR live Players102,658 Servers11,891 Warm3,942 Fresh wipes · 3h337 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 0° now Linear · 0–16° · slots

GUILD_SAGI_NI_CHUI

Online 160.251.253.155:28015 checked 12m ago

moddedoxide
Sp1 · players now 0/ 16
0% full
Li1 · players, the last 48 hours · hourly average, UTCpeak 1°
Tue 19:00flare: a wipe in that hourThu 16:00
1
7-day average
peak 6
#3,822
rank
top 17%
27d ago
last wipe
no schedule published
–
next wipe
no rhythm it keeps
UTC checked 12m ago

Li2Players

AveragePeak
00.250.50.75119:0004:0013:0022:0007:0016:00

Hourly average and peak, UTC.

Li3Server performance

05010015020019:0004:0013:0022:0007:0016: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.

Li4Rank

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.

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

3.5 days
usual gap
between real wipes
0%
on rhythm
of its recent wipes
7
wipe-day peak
players, last three wipes
100%
crowd held
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.

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 10:39 UTC27d ago 7 – running 0
Sun 27 Sep, 11:58 UTC32d ago 7 held half 4.9 days 5
Fri 25 Sep, 12:33 UTC34d ago 7 – 2 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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit
no group limit · 151 on average
144 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
EU · groups of 8+ · weekly · 128 on average
133 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
EU · groups of 16+ · weekly · 118 on average
198 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
EU · groups of 16+ · monthly · 95 on average
83 / 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10
EU · groups of 16+ · monthly · 89 on average
227 / 700
RustSpain.com | EU Main
EU · groups of 12+ · weekly · 84 on average
346 / 350

LogQuick answers

from the figures on this page

Wipe day

What does wipe day look like on GUILD_SAGI_NI_CHUI?

The average peak across its recent wipes is 7 players. 2 hours into the latest wipe, player numbers topped out. Above half the peak until the next wipe: that held in 100% of its recent wipes.

What is the wipe schedule on GUILD_SAGI_NI_CHUI?

No next wipe can be predicted: GUILD_SAGI_NI_CHUI wipes when it chooses, at irregular times. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world it runs now dates from 27 days 7 hours ago.

Player counts

How busy is GUILD_SAGI_NI_CHUI?

Of 16 slots on GUILD_SAGI_NI_CHUI, 0 are in use right now. A seven-day average of 1 players, with a peak of 6. Its busiest point in the last 48 hours was 07:00 UTC, averaging 1 players.

How does GUILD_SAGI_NI_CHUI rank against other Rust servers?

Ranked #3,822 on seven-day player hours, GUILD_SAGI_NI_CHUI is in the top 17% of all ranked servers.

Rules and settings

Which map does GUILD_SAGI_NI_CHUI run?

The map on GUILD_SAGI_NI_CHUI is procedural, size 2,700 with seed 28287, generated by the game. You can look at the map on RustMaps from this page: the same size and seed give the same map. The name of the map is: Custom Map.

What are the rules and settings on GUILD_SAGI_NI_CHUI?

No gather rate appears in the name GUILD_SAGI_NI_CHUI. Groups can contain up to 8 players, the default in the game. The server runs survival, gather, build and raid in the standard game. Players can fight each other, and raids are allowed. Plugins or settings change the game, and it is listed under Modded in the server browser. Plugin count: Oxide. The server has VAC, Valve's anti-cheat, turned on.

Location and uptime

Which version of Rust does GUILD_SAGI_NI_CHUI run?

The build on GUILD_SAGI_NI_CHUI is Rust network protocol 2635 and build 168909, running on Linux. Steam updates your game for you, and the protocol has to match for you to join.

Is GUILD_SAGI_NI_CHUI online, and how reliable is it?

Online now: GUILD_SAGI_NI_CHUI. Its reported uptime dates the last restart to about 6 days 5 hours ago. It was up 167 of 168 hours across the last 7 full days, or 99% of the time. The first record of it on Rust Heatmap is 24 September 2026.

Where is GUILD_SAGI_NI_CHUI located?

No region is published by GUILD_SAGI_NI_CHUI. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. You can reach it at 160.251.253.155:28015.

Does GUILD_SAGI_NI_CHUI run smoothly?

It averaged 140 server fps over the last 48 hours, with a low of 95. The world held as many as 73,835 entities, buildings and deployables included. The highest memory use was 4,416 MB. Lag, as players experience it, comes from low fps and a rising entity count.

Tags

Which Rust Heatmap lists and filters include GUILD_SAGI_NI_CHUI?

The Rust Heatmap lists that GUILD_SAGI_NI_CHUI fits are: Modded Rust servers, by live population. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

What do the server tags on GUILD_SAGI_NI_CHUI mean?

gmrust (Game mode): Rust survival, standard rules; mp16 (Max players): The slot count is 16; ts8 (Group limit): At most 8 per team: the default the game ships with; v2635 (Protocol): Your game must match protocol 2635 to get in; cs168909 (Build): The game build here is 168909; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): The region code is blank; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by settings or plugins, so it sits under Modded are the tags GUILD_SAGI_NI_CHUI publishes, and the server browser reads them. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.

Connect

How do I join GUILD_SAGI_NI_CHUI?

To join by console, open it with F1 in Rust and enter client.connect 160.251.253.155:28015. Or press Launch Rust on this page, which connects you through Steam.

KeyServer tags

what each one means

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

Game

gmrust
Game mode Rust survival, standard rules.
mp16
Max players The slot count is 16.
ts8
Group limit At most 8 per team: the default the game ships with.
v2635
Protocol Your game must match protocol 2635 to get in.
cs168909
Build The game build here is 168909.
ptrak
Networking Standard game networking here, which is RakNet.
$r?
Region code The region code is blank.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded The game is changed by settings or plugins, so it sits 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.