Skip to the page
Network live 11,614 servers online 34,171 players aboard 69 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

ZedZalipNet [Classic] | Wipe: 29.10.2026

Online 109.195.131.173:28015 checked 9m ago

Tracking number · connect
Wipe progress · wiped 27d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –no rhythm it keeps
0/ 100 players now 0% full
07-day averagepeak 1
#7,323ranktop 33%
27d agolast wipeno schedule published
–next wipeno rhythm it keeps
Delivery history

Players, performance and rank

Players

AveragePeak
00.250.50.75107:0016:0001:0010:0020:0005:00

Hourly average and peak, UTC.

Server performance

05010015020007:0016:0001:0010:0020:0005: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
12.5k5k7.5k10k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 33% 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.

7.2 daysusual gapbetween real wipes
0%on rhythmof its recent wipes
5wipe-day peakplayers, last three wipes
0%crowd heldelse 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

every wipe as a delivery, newest first
  1. Fri 2 Oct, 02:23 UTC 03:23 UK · 27d ago
    Wipe delivered
    Peak
    5
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Thu 1 Oct, 18:16 UTC FW 19:16 UK · 27d ago
    Force wipe delivered
    Peak
    4
    Crowd
    –
    Lasted
    0.3 days
    Players before
    0
  3. Thu 17 Sep, 15:15 UTC 16:15 UK · 41d ago
    Wipe delivered
    Peak
    5
    Crowd
    halved by day 5
    Lasted
    14.1 days
    Players before
    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 parcels

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 537 on average 196 / 250
  2. Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average 182 / 200
  3. Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average 16 / 250
  4. Rustoria.co - EU MainEU · groups of 16+ · weekly · 281 on average 14 / 250
  5. Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average 15 / 100
  6. Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 248 on average 90 / 200
Help desk

Quick answers

From the figures on this page.

Population

Where does ZedZalipNet [Classic] | Wipe: 29.10.2026 place among Rust servers?

Over the past seven days, ZedZalipNet [Classic] | Wipe: 29.10.2026 has climbed to #7,323 for player hours, putting it in the top 33% of all ranked servers.

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

The current count is 0 players on 100 slots for ZedZalipNet [Classic] | Wipe: 29.10.2026. The seven-day figures show an average of 0 players and a peak of 1. The busiest hour over the last 48 hours was 09:00 UTC, averaging 1 players.

Rules and settings

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

The game generates the procedural map on ZedZalipNet [Classic] | Wipe: 29.10.2026 at size 4,500 with seed 903463. Identical size and seed give an identical map: view it on RustMaps from this page.

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

The name of ZedZalipNet [Classic] | Wipe: 29.10.2026 gives no gather rate. Up to 8 players can join a group, the default for the game. You get survival here, gather, build and raid, as the standard game goes. You can raid and fight other players. You will find it listed under Community in the server browser: it is a community server. The VAC anti-cheat from Valve is enabled.

Operator and location

In which region is ZedZalipNet [Classic] | Wipe: 29.10.2026 based?

No region is published by ZedZalipNet [Classic] | Wipe: 29.10.2026. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. The address to connect to is 109.195.131.173:28015.

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

The 48-hour average for server fps stands at 103, never dipping below 61. The world held as many as 111,176 entities: buildings, deployables and the rest. 3,170 MB of memory was its top figure. What players call lag is the mix of low fps and an entity count that keeps climbing.

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

You can find ZedZalipNet [Classic] | Wipe: 29.10.2026 online at present. About 3 hours ago is when it last restarted, judged by the uptime it gives. It was up 167 of 168 hours over the last 7 full days, 99% of the time. It was first seen by Rust Wipe Tracker on 13 September 2026.

What Rust version is ZedZalipNet [Classic] | Wipe: 29.10.2026 using?

The version on ZedZalipNet [Classic] | Wipe: 29.10.2026 is Rust network protocol 2635 and build 168909, running on Windows. Steam keeps your game updated; it has to be on the same protocol to join.

Map resets

How does ZedZalipNet [Classic] | Wipe: 29.10.2026 handle its wipe days?

At their busiest, its recent wipes drew an average of 5 players. On the latest wipe, 41 hours passed before the crowd peaked. Half the peak or more was held until the next wipe in 0% of recent wipes. By day 5 it had fallen below half where the crowd did not hold.

On what schedule does ZedZalipNet [Classic] | Wipe: 29.10.2026 reset its map?

There is no next wipe to predict for ZedZalipNet [Classic] | Wipe: 29.10.2026: it wipes at irregular times. The monthly force wipe takes every Rust server with it, and Thursday 5 November at 19:00 UTC is the next one. 27 days 4 hours have passed since this world was made.

Tags and listings

On Rust Wipe Tracker, which lists and filters is ZedZalipNet [Classic] | Wipe: 29.10.2026 part of?

You will find ZedZalipNet [Classic] | Wipe: 29.10.2026 on the following Rust Wipe Tracker lists: Rust community servers, unmodded. These are the filters that bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

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

gmrust (Game mode): Survival in standard Rust; mp100 (Max players): The server has 100 slots; ts8 (Group limit): Team limit: 8, the standard default; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): No region code is set are the tags ZedZalipNet [Classic] | Wipe: 29.10.2026 publishes, and the server browser takes them as read. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.

How to join

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

Use Launch Rust on this page to join, which opens Rust through Steam and connects you, or start Rust, press F1 and enter client.connect 109.195.131.173:28015.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp100
Max players The server has 100 slots.
ts8
Group limit Team limit: 8, the standard default.
v2635
Protocol Join only if your game runs protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Standard network layer here: RakNet.
$r?
Region code No region code is 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.