Rust Server Analytics 34,229 players11,595 servers
All servers
Drill-through Server detail

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

Online EU 88.99.1.43:28035 checked 12m ago

Drill-through
FilterServeris Alkad #3 (Max 2|Kits|Remove|TP)
Attributes
duo biweekly wipes vanillamoddedoxide
Last refreshed
Players now 0/ 100
7-day average 1 peak 4
Rank #3,816 top 17% · #1416 in EU
Last wipe 11d ago biweekly schedule
Next wipe 2d 6h Fri 30 Oct, 11:02 UTC
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
00.511.5205:0014:0023:0009:0018:0003:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
05010015020005:0014:0023:0009:0018:0003: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 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 17% of all ranked servers, top 48% in EU, and #224 of the duo servers (top 53%). Ranked on player hours over the last seven days.

Wipe schedule

fixed weekdays

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

usual gap14 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak5players, last three wipes
crowd held0%else halves by day 3.5

Coming wipes

InWhen, UTCKind
2d 6hFri 30 Oct, 11:02 UTCits own
8d 14hThu 5 Nov, 19:00 UTCFW force wipe
16d 6hFri 13 Nov, 11:02 UTCits own
30d 6hFri 27 Nov, 11:02 UTCits own
36d 14hThu 3 Dec, 19:00 UTCFW force wipe
44d 6hFri 11 Dec, 11:02 UTCits own

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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 11:02 UTC11d ago 3 – running 0
Fri 2 Oct, 11:00 UTC25d ago 6 halved by day 6 14 days 0
Fri 18 Sep, 11:01 UTC39d ago 5 halved by day 1 14 days 1

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
ServerProfilePlayers now
RustOps - Solo/Duo | FULLWIPE 25/10 25.10 10/25 EU · duo · biweekly · 89 on average 14 / 215
Enjoy - Solo/Duo only, no BP wipes. True Vanilla. EU · duo · biweekly · 48 on average 1 / 165
Московский Duo/Solo | Для новичков EU · duo · biweekly · 11 on average 2 / 100
POLAR - EU Solo/Duo | Biweekly | No BP Wipes 10/15 15.10 EU · duo · biweekly · 4 on average 2 / 125
EU Rust for Solo's/Duo's BiWeekly Noob Friendly EU · duo · biweekly · 2 on average 1 / 40
Rustafied.com - EU Duo EU · duo · biweekly · 1 on average 0 / 100

Quick answers

from the figures on this page

Wipe cycle

On what cycle does Alkad #3 (Max 2|Kits|Remove|TP) wipe?

The wipe rhythm of Alkad #3 (Max 2|Kits|Remove|TP) is every other Friday at 11:02 UTC. Friday 30 October at 11:02 UTC is the date the next wipe falls on. The world now in play was created 11 days 17 hours ago. A wipe every two weeks is stated in its tags.

On Alkad #3 (Max 2|Kits|Remove|TP), what happens on wipe day?

Recent wipes averaged a busiest count of 5 players. The highest player count on the latest wipe arrived 30 hours in. Recent wipes held the crowd above half that peak until the next wipe in 0% of cases. By day 3.5 it had fallen below half where the hold failed.

Server details

Which location hosts Alkad #3 (Max 2|Kits|Remove|TP)?

The EU tag on Alkad #3 (Max 2|Kits|Remove|TP) lists it in Europe. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. The address of the server is 88.99.1.43:28035.

Which Rust version is Alkad #3 (Max 2|Kits|Remove|TP) on?

The platform is Windows, with Rust network protocol 2635 and build 168909 running on Alkad #3 (Max 2|Kits|Remove|TP). The protocol has to match before you can join; Steam updates it automatically.

Is Alkad #3 (Max 2|Kits|Remove|TP) up, and how steady is its uptime?

Alkad #3 (Max 2|Kits|Remove|TP) reports online at the current check. About 22 hours ago is when it last restarted, judged by its reported uptime. Of 168 hours in the last 7 full days, 168 were up: 100%. It entered Rust Server Analytics records on 13 September 2026.

Does Alkad #3 (Max 2|Kits|Remove|TP) perform well?

Over 48 hours the average held at 79 server fps, and the minimum was 41. Entity count reached 72,222, covering buildings, deployables and the rest of the world. Memory use reached 2,747 MB at peak. Lag, for players, means low fps alongside a growing entity count.

Lists and tags

How should the tags on Alkad #3 (Max 2|Kits|Remove|TP) be read?

The game's server browser reads the tags Alkad #3 (Max 2|Kits|Remove|TP) publishes: gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): Capacity of 100 slots; ts2 (Group limit): Team size is capped at 2; v2635 (Protocol): Joining needs your game on protocol 2635; cs168909 (Build): Build number 168909; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): The region code is blank; ^b (Biweekly): A two-week wipe cycle; ^v (Vanilla): Facepunch's game unchanged: no altered rates, kits or rules; ^o (Oxide): It runs Oxide (uMod) for plugins; ^z (Modded): Plugins or settings change the game, so it sits under Modded; EU (Europe): The server browser files it under Europe. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Where does Alkad #3 (Max 2|Kits|Remove|TP) appear across Rust Server Analytics's lists and filters?

The following Rust Server Analytics lists count Alkad #3 (Max 2|Kits|Remove|TP) among their servers: Duo Rust servers, EU Rust servers: live population data and Modded Rust servers: live data. These filters bring it up 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.

Player numbers

What position does Alkad #3 (Max 2|Kits|Remove|TP) hold in the server rankings?

Alkad #3 (Max 2|Kits|Remove|TP) holds #3,816 on seven-day player hours and #1,416 in Europe, inside the top 17% of the ranked field. In the duo peer group, the rank is #224.

How many players does Alkad #3 (Max 2|Kits|Remove|TP) carry?

Of 100 slots, 0 are filled on Alkad #3 (Max 2|Kits|Remove|TP) at this refresh. The seven-day mean is 1 players, against a peak of 4. Averaged over 48 hours, activity is highest at 19:00 UTC with 2 players.

Map and rules

How is Alkad #3 (Max 2|Kits|Remove|TP) configured, and what rules apply?

No gather rate is given in the name of Alkad #3 (Max 2|Kits|Remove|TP). A maximum of 2 players per group is set (duo). It runs survival, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. Plugins or settings modify the game, and it is listed as Modded. The plugin framework is Oxide. The server's own label is vanilla: facepunch's game unchanged: no altered rates, kits or rules. VAC, Valve's anti-cheat, is enabled.

The map on Alkad #3 (Max 2|Kits|Remove|TP): which one is it?

The game generates a procedural map of size 3,500 with seed 1472934234 for Alkad #3 (Max 2|Kits|Remove|TP). Size and seed fix the map, so a RustMaps view is available from this page.

How to join

How can a player join Alkad #3 (Max 2|Kits|Remove|TP)?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 88.99.1.43:28035. Find it online at https://m.vk.com/rust_alkad.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust format.
mp100
Max players Capacity of 100 slots.
ts2
Group limit Team size is capped at 2.
v2635
Protocol Joining needs your game on protocol 2635.
cs168909
Build Build number 168909.
ptrak
Networking Network layer: RakNet, Rust's default.
$r?
Region code The region code is blank.

Wipe schedule

^b
Biweekly A two-week wipe cycle.

Difficulty

^v
Vanilla Facepunch's game unchanged: no altered rates, kits or rules.

Mods and access

^o
Oxide It runs Oxide (uMod) for plugins.
^z
Modded Plugins or settings change the game, so it sits 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.