[EU] SLIMI RUST | 2X | WEEKLY WIPE | PVP | Solo/Duo/Trio/Quad banner

[EU] SLIMI RUST | 2X | WEEKLY WIPE | PVP | Solo/Duo/Trio/Quad

Server admin? Sign in with Steam to claim this server.

121 ms · Chicago

Jitter 0 ms

Last checked 2 m ago

7 / 150 players

Custom Map

2x Max 4 62 days live Avg ping 119.5 ms Avg jitter 8.5 ms Wipe halving: 1 days Wipe cycle 5.1 ±2.6 days

Visit website

Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.

Connect: 45.81.254.151:28015

Share instant-connect link

Connecting…

Steam should be opening now. Didn't work? Use the button below, or connect manually further down.

Open Steam & Connect

How this works

  • Steam opens first — then Rust launches and connects automatically.
  • Be patient — it can take a moment, especially on first launch.
  • One click is enough — clicking multiple times won't help.
connect 45.81.254.151:28015

Steam link not working? This usually means your browser isn't set up to open steam:// links, or Steam isn't installed on this device. Connect manually instead:

  1. Launch Rust
  2. Press F1 to open the console
  3. Paste the command above (copy button next to it) and press Enter

First seen 15.09.2026

Next wipe: (in 6 days) Predicted

Last wipe: (20 h ago)

Wipe history

Wiped Days since previous
4
7.1
6.9
7
7
7
6.8
7.7
5.2
1.1
1
0.9
—

Player count history

Wipe timing behind this data is sometimes inferred rather than confirmed, so daily figures right around a wipe boundary can land on the wrong day. Accuracy improves over time as detection gets more precise.

7 30 90 days

Highest peak 44 Nov 16 · 16:29 UTC Median daily peak 20 (median of daily peaks, not average population)

Observed daily peak

Wipe01020304050Nov 14Nov 17

4 full · 0 partial · 0 offline · 4 no data

Population persistence across recent wipes

Each line follows one wipe cycle from the moment it started, lined up by days since that wipe rather than by calendar date — so you can compare how well this server held onto its population after different resets, independent of when each one happened.

050100150200

Ping history from Chicago

130ms115msOct 18Nov 17

Jitter history

16.2ms0msOct 18Nov 17

Recent history from Chicago

Checked Status Ping Players
Online 121 ms 7
Online 121 ms 2
Online 121 ms 0
Online 117 ms 0
Online 117 ms 7
Online 121 ms 11
Online 111 ms 21
Online 120 ms 29
Online 116 ms 3
Online 121 ms 2
Online 116 ms 3
Online 116 ms 1
Online 119 ms 1
Online 112 ms 0
Online 115 ms 3
Online 117 ms 6
Online 120 ms 5
Online 120 ms 17
Online 121 ms 11
Online 111 ms 8
Online 119 ms 3
Online 111 ms 1
Online 118 ms 0
Online 113 ms 1
Online 121 ms 0
Online 117 ms 6
Online 119 ms 7
Online 120 ms 17

Other 2x servers in Lithuania (low ping)

| Solo/Duo/Trio | Weekly | No Kits/P2W

0/100

Last checked 5 m ago

Wiped 4 d ago

68% elapsed32% left

Next wipe in 2 days

2x GatherMax 32 avg wipe peakVanilla

Procedural Map

118 ms· Chicago

Jitter3.5 ms

Monthly Main | No BP wipes | Noob Friendly | x2

14/200

Last checked 2 m ago

Wiped 11 d ago

42% elapsed58% left

Next wipe in 16 days

2x GatherNo BP wipe93 avg wipe peakVanilla

Helix Better FPS Map | x2

No Chicago reading yet

EU Solo/Duo – 50% Upkeep|Noob Friendly

11/125

Last checked 1 m ago

Wiped 11 d ago

2x GatherMax 247 avg wipe peakVanillaDiscord

No Chicago reading yet

Frequently asked questions

What does "wipe" mean in Rust?

A wipe resets a server's map and usually player progress too — bases, resources, and blueprints, unless the server keeps blueprints through wipes (shown here as "No BP wipe"). Most servers wipe on a regular schedule, often weekly.

What does "force wipe" mean?

Facepunch pushes a mandatory update on the first Thursday of each month that requires every Rust server to wipe, regardless of its own schedule — a "force wipe," distinct from a server's regular map wipe.

How do I know when this server wipes?

The "Next wipe" time above is extracted from the server's own published schedule. "High confidence" means the server stated an explicit date or time; "Predicted" means it's estimated from the server's typical cadence and isn't guaranteed.

How do I connect to this server?

Copy the server address above, open Rust's in-game console with F1, and run client.connect followed by the address — or connect directly through Steam's server browser using the same address.