Rust Server TrendsSeismic network · station log
Recording Stations11,610 Players35,756 Active2,903 Wipes · 3 h67 48 h

Station AF-4021 · recording

LowBlowZA

Online AF 41.193.57.20:28004 checked 12m ago

monthly wipes moddedoxide
Connect
Players now
0/ 40
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
1
peak 2
Rank
#4,021
top 18% · #10 in AF
Last wipe
22d ago
monthly schedule
Next wipe
8d 12h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station AF-4021 · CH Z

The last 48 hours, hour by hour

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

Players

AveragePeak
00.511.5207:0016:0001:0010:0019:0004:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040007:0016:0001:0010:0019:0004: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 4 Oct. 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
15k10k15k20k4 Oct9 Oct14 Oct18 Oct23 Oct28 Oct

Top 18% of all ranked servers, top 31% in AF. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 8d 12h. The force wipe · high confidence

usual gap
0.8 daysbetween real wipes
wipe-day peak
2players, last three wipes

Coming wipes

  1. 8d 12hThu 5 Nov, 19:00 UTCFW
  2. 36d 12hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

Mon 5 OctSun 4 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 5 Oct, 16:22 UTC22d ago M0.3rising 2 – running 0
Sun 4 Oct, 21:09 UTC23d ago M0.0steady 2 – 0.8 days 2

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
Intoxicated ZA Vanilla 3 - 01 Oct AF · groups of 8+ · monthly · 20 on average
3/ 150
ServerZ Rust Monthly ZA AF · groups of 8+ · monthly · 2 on average
0/ 50
Voodoo ZA AF · groups of 8+ · monthly · 1 on average
0/ 100
Intoxicated ZA Vanilla 1 - 15 Oct AF · groups of 8+ · biweekly · 8 on average
2/ 100
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 88 on average
31/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 83 on average
12/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on LowBlowZA?

LowBlowZA runs a procedural map of size 3,000 with seed 55847, produced 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 LowBlowZA?

The name of LowBlowZA gives no gather rate. At the game's default, groups can have up to 8 players. It plays in survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on LowBlowZA?

At this moment, LowBlowZA records 0 players across 40 slots. The seven-day average is 1 players, with a peak of 2. Averaged over the last 48 hours, the busiest hour was 10:00 UTC at 1 players.

How does LowBlowZA rank against other Rust servers?

For player hours across the last seven days, LowBlowZA takes #4,021 overall and #10 in Africa, inside the top 18% of all ranked servers.

Server facts

How reliably does LowBlowZA stay online?

As recorded now, LowBlowZA is running. The uptime it reports puts its last restart about 4 minutes ago. 168 of 168 hours in the last 7 full days were up time, 100% of the total. On 4 October 2026 it was recorded for the first time by Rust Server Trends.

Does LowBlowZA hold a steady tick rate?

Across the last 48 hours it averaged 217 server fps, with a floor of 74. At its highest, it carried 59,638 entities: buildings, deployables and the world's other contents. Memory use peaked at 2,589 MB. What you feel as lag is the combination of low fps and a rising entity count.

Which region does LowBlowZA run from?

In Africa LowBlowZA lists itself, with the tag AF. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 41.193.57.20:28004 is the address it uses.

Which Rust version is LowBlowZA running?

LowBlowZA is running Rust network protocol 2635 and build 168909 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe schedule

What does wipe day look like on LowBlowZA?

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

On what timetable does LowBlowZA run its wipes?

The force wipe is the only wipe LowBlowZA takes, once a month. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 22 days 10 hours is how long the current world has been running. The tags it publishes carry a monthly wipe schedule.

Server tags

What do the server tags on LowBlowZA mean?

The game's server browser reads the tags LowBlowZA publishes: gmrust (Game mode): The game mode is standard Rust survival; mp40 (Max players): Slots: 40; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^m (Monthly): It wipes monthly, together with the Facepunch force wipe; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; AF (Africa): The server browser files it under Africa. 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 LowBlowZA appear?

You will find LowBlowZA on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Region: Africa; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

Join the server

How do you connect to LowBlowZA?

Enter client.connect 41.193.57.20:28004 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. You can find its website at https://discord.com/invite/etAtqFcp4.

Instrument codes

Server tags

what each one means

Published as mp40,ptrak,$r?,v2635,^m,AF,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
mp40
Max players Slots: 40.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Wipe schedule

^m
Monthly It wipes monthly, together with the Facepunch force wipe.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

Region

AF
Africa The server browser files it under Africa.

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.