Rust Server TrendsSeismic network · station log
Recording Stations11,617 Players35,650 Active2,906 Wipes · 3 h66 48 h

Station XX-14749 · no signal

Zache Local Build Server

Offline 31.111.112.161:28015 checked 12d ago

moddedoxide
Connect
Players now
0/ 4
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,749
top 68%
Last wipe
24d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-14749 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 4 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k27 Sep2 Oct7 Oct12 Oct17 Oct22 Oct

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

Expected events

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 peak
1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sat 3 Oct, 17:35 UTC24d ago M0.0rising 1 – running 0

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
29/ 999
97/ 999
66/ 150
Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFA EU · groups of 30+ · weekly · 34 on average
364/ 400
AQRUX RUST BUILD | CREATIVE | SANDBOX EU · groups of 8+ · monthly · 23 on average
15/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which settings and rules apply on Zache Local Build Server?

No gather rate appears in the name of Zache Local Build Server. Groups hold up to 8 players, which is the default for the game. survival is the game 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. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.

Population

What is the current population on Zache Local Build Server?

Zache Local Build Server is not responding at this moment and is offline, last seen 12 days 6 hours ago.

How does Zache Local Build Server rank against other Rust servers?

Over the last seven days, Zache Local Build Server recorded enough player hours to reach #14,749 worldwide, placing it in the top 68% of all ranked servers.

Operator and location

How reliably does Zache Local Build Server stay online?

No contact with Zache Local Build Server right now, and the last recorded contact was 12 days 6 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 27 September 2026.

Where in the world is Zache Local Build Server hosted?

No region is published by Zache Local Build Server. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 31.111.112.161:28015.

Which Rust version is Zache Local Build Server running?

Rust network protocol 2634 and build 166652 on Linux is what Zache Local Build Server runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on Zache Local Build Server?

The recent wipes averaged a busiest count of 1 players. 1 hours into the latest wipe, the crowd reached its peak.

On what timetable does Zache Local Build Server run its wipes?

On record so far are too few of Zache Local Build Server's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 24 days 12 hours.

Server tags

What do the server tags on Zache Local Build Server mean?

These are the tags Zache Local Build Server publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp4 (Max players): 4 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166652 (Build): Game build: 166652; 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): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed 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 Zache Local Build Server appear?

The Rust Server Trends lists that take in Zache Local Build Server are: Modded Rust servers, tracked live and Rust build and creative servers, live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How to join

What steps get you onto Zache Local Build Server?

You can connect by pressing F1 in Rust and typing client.connect 31.111.112.161: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 mp4,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp4
Max players 4 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs166652
Build Game build: 166652.
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 Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed 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.