Skip to the page
RUST ANALYTICS
LIVE37,558PLY11,461SRV
QUOTE 109.195.131.173:28015 Online checked 10m ago

ZedZalipNet [Classic] | Wipe: 29.10.2026

Players · last
0/ 100
+024h
0% full
Day range 0 2
7-day avg 1 peak 5
Players · 24 hourshourly average, then now · dashed: 24 hours ago
Launch Rust and join

Key statistics

the figures behind the quote
Players now
0/ 100
0% full
Change · 24h
+0
no reading a day ago
7-day average
1
peak 5
Rank
#3,767
top 17%
Rank · 7d ago
#2,947
820 places down
Last wipe
12d ago
no schedule published
Next wipe
–
no rhythm it keeps
Group limit
8
8, the default
Gather rate
–
no rate in the name
Score
118
player hours, last seven days
Map
4500
Procedural Map · seed 903463
First seen
13 Sep 2026
no hostname published

Players

AveragePeak
00.511.5208:0017:0002:0012:0021:0006:00

Hourly average and peak, UTC. Busiest hour of the two days: 2 players.

Server performance

05010015020008:0017:0002:0012:0021:0006: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.

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

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

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 days
between real wipes
on rhythm
0%
of its recent wipes
wipe-day peak
5
players, 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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 02:23 UTC12d ago 5 – running 0
Thu 1 Oct, 18:16 UTC FW12d ago 4 – 0.3 days 0
Thu 17 Sep, 15:15 UTC26d ago 5 halved by day 5 14.1 days 0

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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
#ServerLastChg 24hPlayers over the last 24 hours24h
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 407 on average261/250−15−5.5%
2Rusty Moose |EU Monthly|EU · groups of 12+ · monthly · 355 on average155/200+12+8.7%
3Rusty Moose |US Monthly|NA · groups of 12+ · monthly · 337 on average219/250+13+6.3%
4Rustoria.co - EU LongEU · groups of 14+ · monthly · 333 on average144/200−23−13.6%
5Rustoria.co - EU MainEU · groups of 16+ · weekly · 299 on average22/250−14−39.0%
6Rustafied.com - EU Long - LargeEU · groups of 16+ · monthly · 282 on average118/150−17−12.4%

Quick answers

from the figures on this page

Map and Rules

How is ZedZalipNet [Classic] | Wipe: 29.10.2026 configured in terms of rules and settings?

The name of ZedZalipNet [Classic] | Wipe: 29.10.2026 carries no gather rate. The default group size of 8 players applies here. survival is the mode, gather, build and raid in the standard game. PvP and raiding are enabled. You will find it under Community in the server browser: it is a community server. VAC, Valve's anti-cheat, is enabled.

What is the current map on ZedZalipNet [Classic] | Wipe: 29.10.2026?

ZedZalipNet [Classic] | Wipe: 29.10.2026 uses a procedural map of size 4,500 with seed 903463, generated by the game. Because size and seed determine the map, RustMaps offers a view of it from this page.

Activity

Where does ZedZalipNet [Classic] | Wipe: 29.10.2026 sit in the rankings?

For the last seven days, ZedZalipNet [Classic] | Wipe: 29.10.2026 holds rank #3,767 on player hours, in the top 17% of all ranked servers.

What is the population on ZedZalipNet [Classic] | Wipe: 29.10.2026?

On ZedZalipNet [Classic] | Wipe: 29.10.2026, 0 players are in now, out of 100 slots. Average players over seven days: 1; peak: 5. Over the last 48 hours, the peak hour was 15:00 UTC, averaging 2 players.

Wipe Cycle

What happens on wipe day at ZedZalipNet [Classic] | Wipe: 29.10.2026?

An average of 5 players marked the busiest point of its recent wipes. 41 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. If it did not hold, by day 5 the crowd dropped below half.

On what cycle does ZedZalipNet [Classic] | Wipe: 29.10.2026 wipe?

ZedZalipNet [Classic] | Wipe: 29.10.2026 wipes at times that do not follow a pattern, so no next wipe can be predicted. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. Its world now is 12 days 5 hours old.

Server Info

What is the location of ZedZalipNet [Classic] | Wipe: 29.10.2026?

No region is published by ZedZalipNet [Classic] | Wipe: 29.10.2026. Rust Analytics reports the location a server claims, not the machine's actual location. 109.195.131.173:28015 is its address.

Is ZedZalipNet [Classic] | Wipe: 29.10.2026 performing well?

Server fps over the last 48 hours: 109 on average, 82 at the lowest. At its peak it held 113,219 entities: buildings, deployables and the rest of the world. The memory ceiling reached 3,433 MB. What players feel as lag is low fps together with a rising entity count.

ZedZalipNet [Classic] | Wipe: 29.10.2026 is on which Rust version?

Rust network protocol 2634 and build 166494 on Windows is what ZedZalipNet [Classic] | Wipe: 29.10.2026 runs. The protocol has to match for you to join, and Steam applies that update.

Is ZedZalipNet [Classic] | Wipe: 29.10.2026 up, and how consistent is its uptime?

Online at this moment: ZedZalipNet [Classic] | Wipe: 29.10.2026. 4 hours ago is when it last restarted, judging by the uptime it reports. 100% is its uptime for the last 7 full days, 168 of 168 hours. The earliest Rust Analytics saw it was 13 September 2026.

Tags & Filters

How should you interpret the tags on ZedZalipNet [Classic] | Wipe: 29.10.2026?

These tags are published by ZedZalipNet [Classic] | Wipe: 29.10.2026 and read by the game's server browser: gmrust (Game mode): Rust's standard survival mode; mp100 (Max players): Capacity: 100 slots; ts8 (Group limit): Team size stays at the game default of 8; v2634 (Protocol): To join, your game needs protocol 2634; cs166494 (Build): Build 166494; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): No region code has been set. The tags also carry its current players, queue and world creation time; this page shows them at the top.

ZedZalipNet [Classic] | Wipe: 29.10.2026 appears in which of the lists and filters on Rust Analytics?

On Rust Analytics, ZedZalipNet [Classic] | Wipe: 29.10.2026 matches these lists: Rust community servers. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Joining the Server

What is the process to join ZedZalipNet [Classic] | Wipe: 29.10.2026?

Type client.connect 109.195.131.173:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode Rust's standard survival mode.
mp100
Max players Capacity: 100 slots.
ts8
Group limit Team size stays at the game default of 8.
v2634
Protocol To join, your game needs protocol 2634.
cs166494
Build Build 166494.
ptrak
Networking RakNet, the network layer the game ships with.
$r?
Region code No region code has been set.

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.