Rust Server TrendsSeismic network · station log
Recording Stations11,829 Players89,289 Active4,008 Wipes · 3 h37 48 h

Station XX-7897 · recording

ZedZalipNet [Classic] | Wipe: 29.10.2026

Online 109.195.131.173:28015 checked 2h ago

Connect
Players now
0/ 100
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#7,897
top 36%
Last wipe
26d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-7897 · CH Z

The last 48 hours, hour by hour

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

Players

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

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020020: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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 36% 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
7.2 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
5players, last three wipes
crowd held
0%else halves by day 5

The first 48 hours of its last wipes

Fri 2 OctThu 1 OctThu 17 Sep
01234+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 2 Oct, 02:23 UTC26d ago M0.7rising 5 – running 0
Thu 1 Oct, 18:16 UTC FW27d ago M0.6rising 4 – 0.3 days 0
Thu 17 Sep, 15:15 UTC41d ago M0.7rising 5 halved by day 5 14.1 days 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
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 552 on average
636/ 675
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
485/ 525
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 299 on average
59/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 298 on average
36/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 270 on average
138/ 200
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 256 on average
255/ 300
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on ZedZalipNet [Classic] | Wipe: 29.10.2026?

The procedural map on ZedZalipNet [Classic] | Wipe: 29.10.2026 is size 4,500 with seed 903463, generated by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on ZedZalipNet [Classic] | Wipe: 29.10.2026?

You will find no gather rate in the name of ZedZalipNet [Classic] | Wipe: 29.10.2026. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Community, as a community server. The server has VAC on, Valve's anti-cheat.

Population

How many players are recorded on ZedZalipNet [Classic] | Wipe: 29.10.2026 right now?

0 of the 100 slots on ZedZalipNet [Classic] | Wipe: 29.10.2026 are filled right now. Averaged across the last seven days the population was 0 players, reaching a peak of 1. Averaged over the last 48 hours, the busiest hour was 09:00 UTC at 1 players.

How does ZedZalipNet [Classic] | Wipe: 29.10.2026 rank against other Rust servers?

The last seven days of player hours place ZedZalipNet [Classic] | Wipe: 29.10.2026 at #7,897, in the top 36% of all ranked servers.

Server facts

How reliably does ZedZalipNet [Classic] | Wipe: 29.10.2026 stay online?

ZedZalipNet [Classic] | Wipe: 29.10.2026 is up at the moment. Going by the uptime figure it reports, it restarted about 14 hours ago. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. 13 September 2026 is when Rust Server Trends first recorded it.

How well does ZedZalipNet [Classic] | Wipe: 29.10.2026 perform under load?

Across the last 48 hours it averaged 104 server fps, with a floor of 61. At its highest, it carried 111,176 entities: buildings, deployables and the world's other contents. Its highest memory use was 3,105 MB. What you feel as lag is the combination of low fps and a rising entity count.

Which region does ZedZalipNet [Classic] | Wipe: 29.10.2026 run from?

No region is published by ZedZalipNet [Classic] | Wipe: 29.10.2026. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 109.195.131.173:28015.

What build of Rust does ZedZalipNet [Classic] | Wipe: 29.10.2026 use?

On Windows, ZedZalipNet [Classic] | Wipe: 29.10.2026 runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

What does wipe day look like on ZedZalipNet [Classic] | Wipe: 29.10.2026?

On average, the busiest point of its recent wipes drew 5 players. The peak on the most recent wipe came 41 hours after the wipe. Half that peak was held until the next wipe in 0% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 5.

How often does ZedZalipNet [Classic] | Wipe: 29.10.2026 wipe, and on which days?

No next wipe can be predicted for ZedZalipNet [Classic] | Wipe: 29.10.2026, 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. 26 days 17 hours is how long the current world has been running.

Tags

What do the server tags on ZedZalipNet [Classic] | Wipe: 29.10.2026 mean?

Tags published by ZedZalipNet [Classic] | Wipe: 29.10.2026 and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): Slots: 100; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): The game build is 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. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does ZedZalipNet [Classic] | Wipe: 29.10.2026 appear?

You will find ZedZalipNet [Classic] | Wipe: 29.10.2026 on the following Rust Server Trends lists: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How to join

How do you connect to ZedZalipNet [Classic] | Wipe: 29.10.2026?

To join, enter client.connect 109.195.131.173:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is standard Rust survival.
mp100
Max players Slots: 100.
ts8
Group limit Teams max out at 8, the default set by the game.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build The game build is 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.

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.