ZedZalipNet [Classic] | Wipe: 29.10.2026
Online 109.195.131.173:28015 checked 12m ago
Server instruments
last reading Thu 00:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 61 · below 20 is lag, below 10 is badEntities
48 h range 108,363–111,176 · memory 3,073 MBUptime
22 h 56 min since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 35% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 5, 41 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 02:23 UTC26d ago | 5 | – | running | 0 |
| Thu 1 Oct, 18:16 UTC FW27d ago | 4 | – | 0.3 days | 0 |
| Thu 17 Sep, 15:15 UTC41d 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- 187/250
- 120/200
- 19/250
- 11/250
- 20/100
- 28/225
Quick answers
from the figures on this pageWipe timing
What happens on ZedZalipNet [Classic] | Wipe: 29.10.2026 when wipe day comes?
An average of 5 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 41 hours in. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. When it didn't hold, by day 5 it fell below half.
What wipe timing does ZedZalipNet [Classic] | Wipe: 29.10.2026 follow?
There is no next wipe to predict: ZedZalipNet [Classic] | Wipe: 29.10.2026 wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 26 days 23 hours ago.
Lists and filters
Which tags does ZedZalipNet [Classic] | Wipe: 29.10.2026 carry, and what do they mean?
These are the tags ZedZalipNet [Classic] | Wipe: 29.10.2026 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show ZedZalipNet [Classic] | Wipe: 29.10.2026?
These Rust Metrics lists carry ZedZalipNet [Classic] | Wipe: 29.10.2026: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
Where does ZedZalipNet [Classic] | Wipe: 29.10.2026 sit in the rankings?
Ranking for ZedZalipNet [Classic] | Wipe: 29.10.2026: #7,877 on seven-day player hours, top 35% of all ranked servers.
What player count does ZedZalipNet [Classic] | Wipe: 29.10.2026 carry?
0 of 100 slots are filled on ZedZalipNet [Classic] | Wipe: 29.10.2026 right now. Check: players over seven days. Average 0, peak 1. Average at the busiest hour was 1 players, at 09:00 UTC over the last 48 hours.
Operator and location
Which location does ZedZalipNet [Classic] | Wipe: 29.10.2026 run from?
No region comes from ZedZalipNet [Classic] | Wipe: 29.10.2026. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 109.195.131.173:28015.
What Rust version is ZedZalipNet [Classic] | Wipe: 29.10.2026 on?
Version check: Rust network protocol 2635 and build 168909 on Windows, run by ZedZalipNet [Classic] | Wipe: 29.10.2026. To get in, your game needs the same protocol; Steam applies the update.
What is the performance reading for ZedZalipNet [Classic] | Wipe: 29.10.2026?
Reading: 103 server fps on average across the last 48 hours. It never dropped below 61. Check: entities. The peak was 111,176, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 3,105 MB. Expect lag when fps falls and entities climb.
What is the uptime on ZedZalipNet [Classic] | Wipe: 29.10.2026, and is it online?
Check: connection. ZedZalipNet [Classic] | Wipe: 29.10.2026 is online at this moment. By its reported uptime, the last restart was roughly 22 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Check: first contact. Rust Metrics logged it on 13 September 2026.
Map and rules
How is ZedZalipNet [Classic] | Wipe: 29.10.2026 configured, and what rules are in force?
Reading the name gives no gather rate for ZedZalipNet [Classic] | Wipe: 29.10.2026. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
What map is ZedZalipNet [Classic] | Wipe: 29.10.2026 on?
Check: map. Procedural, size 4,500, seed 903463, generated by the game on ZedZalipNet [Classic] | Wipe: 29.10.2026. The map repeats when size and seed match. Open it on RustMaps from this page.
Connection
How can you get onto ZedZalipNet [Classic] | Wipe: 29.10.2026?
To join: start Rust, press F1 and type client.connect 109.195.131.173:28015. Or press Launch Rust here and Steam opens the game and connects you.