Rust Server TrendsSeismic network · station log
Recording Stations11,802 Players69,058 Active3,653 Wipes · 3 h129 48 h

Station EU-4202 · recording

Alkad #3 (Max 2|Kits|Remove|TP)

Online EU 88.99.1.43:28035 checked 8m ago

duo biweekly wipes vanillamoddedoxide
Connect
Players now
0/ 100
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 3
Rank
#4,202
top 19% · #1502 in EU
Last wipe
12d ago
biweekly schedule
Next wipe
1d 13h
Fri 30 Oct, 11:02 UTC
Seismic record · station EU-4202 · 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 Tue 12:00 UTC
Peak · 48 h
2most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.511.5222:0007:0016:0001:0010:0020:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020022:0007:0016:0001:0010:0020: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
12k4k6k8k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 19% of all ranked servers, top 51% in EU, and #232 of the duo servers (top 55%). Ranked on player hours over the last seven days.

Expected events

Wipe schedule

fixed weekdays

Next wipe Friday 30 October, 11:02 UTC, in 1d 13h. Every other Friday at 11:02 UTC · medium confidence

usual gap
14 daysbetween real wipes
on rhythm
100%of its recent wipes
wipe-day peak
5players, last three wipes
crowd held
0%else halves by day 3.5

Coming wipes

  1. 1d 13hFri 30 Oct, 11:02 UTC
  2. 7d 21hThu 5 Nov, 19:00 UTCFW
  3. 15d 13hFri 13 Nov, 11:02 UTC
  4. 29d 13hFri 27 Nov, 11:02 UTC
  5. 35d 21hThu 3 Dec, 19:00 UTCFW
  6. 43d 13hFri 11 Dec, 11:02 UTC

The first 48 hours of its last wipes

Fri 16 OctFri 2 OctFri 18 Sep
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 30 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 16 Oct, 11:02 UTC12d ago M0.5rising 3 – running 0
Fri 2 Oct, 11:00 UTC26d ago M0.8rising 6 halved by day 6 14 days 0
Fri 18 Sep, 11:01 UTC40d ago M0.6rising 5 halved by day 1 14 days 1

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
RustOps - Solo/Duo | FULLWIPE 25/10 25.10 10/25 EU · duo · biweekly · 89 on average
34/ 215
Enjoy - Solo/Duo only, no BP wipes. True Vanilla. EU · duo · biweekly · 41 on average
22/ 165
Московский Duo/Solo | Для новичков EU · duo · biweekly · 11 on average
11/ 100
POLAR - EU Solo/Duo | Biweekly | No BP Wipes 10/15 15.10 EU · duo · biweekly · 4 on average
0/ 125
EU Rust for Solo's/Duo's BiWeekly Noob Friendly EU · duo · biweekly · 1 on average
0/ 40
TRAVELER DUO [MAX 2] Wipe 23.10 EU · duo · weekly · 27 on average
2/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Alkad #3 (Max 2|Kits|Remove|TP)?

Alkad #3 (Max 2|Kits|Remove|TP) runs a procedural map of size 3,500 with seed 1472934234, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on Alkad #3 (Max 2|Kits|Remove|TP)?

No gather rate appears in the name of Alkad #3 (Max 2|Kits|Remove|TP). The limit for a group is 2 players (duo). It plays in survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. Vanilla is the label it uses for itself: no changed rates, kits or rules: this is the game as Facepunch ships it. VAC, Valve's anti-cheat, is switched on.

Population

What is the current population on Alkad #3 (Max 2|Kits|Remove|TP)?

At this moment, Alkad #3 (Max 2|Kits|Remove|TP) records 0 players across 100 slots. Across seven days this server recorded an average of 0 players and a peak of 3. Averaged over the last 48 hours, the busiest hour was 13:00 UTC at 1 players.

How does Alkad #3 (Max 2|Kits|Remove|TP) rank against other Rust servers?

For player hours across the last seven days, Alkad #3 (Max 2|Kits|Remove|TP) takes #4,202 overall and #1,502 in Europe, inside the top 19% of all ranked servers. The ranking for duo puts it at #232.

Server details

How reliably does Alkad #3 (Max 2|Kits|Remove|TP) stay online?

Alkad #3 (Max 2|Kits|Remove|TP) is up at the moment. Going by the uptime figure it reports, it restarted about 15 hours ago. 168 of 168 hours in the last 7 full days were up time, 100% of the total. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.

Does Alkad #3 (Max 2|Kits|Remove|TP) hold a steady tick rate?

The 48-hour average is 80 server fps; 41 is the lowest observed. At its highest, it carried 72,222 entities: buildings, deployables and the world's other contents. Memory use peaked at 2,721 MB. Low fps together with a growing entity count is what players experience as lag.

Which region does Alkad #3 (Max 2|Kits|Remove|TP) run from?

With its EU tag, Alkad #3 (Max 2|Kits|Remove|TP) lists itself in Europe. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 88.99.1.43:28035.

What build of Rust does Alkad #3 (Max 2|Kits|Remove|TP) use?

Rust network protocol 2635 and build 168909 on Windows is what Alkad #3 (Max 2|Kits|Remove|TP) runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on Alkad #3 (Max 2|Kits|Remove|TP)?

5 players, on average, was the busiest crowd at its recent wipes. 30 hours into the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. It fell under half by day 3.5 in the wipes where it didn't hold.

On what timetable does Alkad #3 (Max 2|Kits|Remove|TP) run its wipes?

every other Friday at 11:02 UTC is how Alkad #3 (Max 2|Kits|Remove|TP) wipes. Friday 30 October at 11:02 UTC is when its next wipe is due. 12 days 10 hours is how long the current world has been running. Every two weeks it wipes, according to the schedule in its tags.

Lists and tags

What do the server tags on Alkad #3 (Max 2|Kits|Remove|TP) mean?

These are the tags Alkad #3 (Max 2|Kits|Remove|TP) publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): 100 slots are available; ts2 (Group limit): Each team can hold up to 2; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^b (Biweekly): The wipe cycle is two weeks; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; EU (Europe): The server browser files it under Europe. 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 Alkad #3 (Max 2|Kits|Remove|TP) appear?

You will find Alkad #3 (Max 2|Kits|Remove|TP) on the following Rust Server Trends lists: Duo Rust servers, group limit 2, EU Rust servers and Modded Rust servers, tracked live. You will find it under these filters on the server list: Region: Europe; Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: Duo; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

How to join

How do you connect to Alkad #3 (Max 2|Kits|Remove|TP)?

You can connect by pressing F1 in Rust and typing client.connect 88.99.1.43:28035 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. For the website, go to https://m.vk.com/rust_alkad.

Instrument codes

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^b,^v,EU,gmrust,cs168909,ts2,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
mp100
Max players 100 slots are available.
ts2
Group limit Each team can hold up to 2.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Difficulty

^v
Vanilla No changed rates, kits or rules: this is the game as Facepunch ships it.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

Region

EU
Europe The server browser files it under Europe.

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.