[SEA] SkullLand | PVE 2x Monthly Wipe

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

237 ms · Chicago

Jitter 4.6 ms

Last checked 5 m ago

0 / 75 players

Procedural Map

2x 13 days live Avg ping 227.7 ms Avg jitter 7 ms Wipe cycle 2.3 ±1.2 days

Visit website

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

Connect: 15.235.132.85:26613

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 15.235.132.85:26613

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 04.11.2026

Next wipe: (in 16 days) Force wipe

Last wipe: (10 d ago)

Wipe history

Wiped Days since previous
1.1
3.5
—

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 2 Nov 15 · 17:49 UTC Median daily peak 1.5 (median of daily peaks, not average population)

Observed daily peak

012Nov 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.

012345

Server info

Monthly Wipe https://discord.gg/zv2NXMV5m

Ping history from Chicago

236ms224msNov 4Nov 17

Jitter history

8.5ms0msNov 4Nov 17

Recent history from Chicago

Checked Status Ping Players
Online 237 ms 0
Online 228 ms 0
Online 231 ms 0
Online 232 ms 0
Online 252 ms 0
Online 220 ms 0
Online 230 ms 0
Online 214 ms 0
Online 232 ms 0
Online 232 ms 0
Online 215 ms 0
Online 231 ms 0
Online 217 ms 0
Online 225 ms 1
Online 237 ms 0
Online 228 ms 0
Online 231 ms 0
Online 215 ms 0
Online 230 ms 2
Online 228 ms 1
Online 213 ms 1
Online 232 ms 1
Online 233 ms 1
Online 223 ms 1
Online 229 ms 0
Online 226 ms 1
Online 229 ms 0
Online 237 ms 0
Online 231 ms 0

Other 2x servers in Singapore (low ping)

2x PvPvE | Raid 3PM-12AM | FULL WIPE 23/10

0/140

Last checked 4 m ago

Wiped 10 d ago

2x Gather5 avg wipe peakVanilla

Procedural Map

206 ms· Chicago

Jitter1.5 ms

| 2X | TEAM 8 | RAID 18:30-23:30 ICT

1/200

Last checked 9 s ago

Wiped 4 d ago

58% elapsed42% left

Next wipe in 2 days

2x Gather4 avg wipe peakVanilla

Procedural Map

210 ms· Chicago

Jitter3.5 ms

Beginners PVE 2X|Solo/Duo

8/80

Last checked 43 s ago

Wiped 11 d ago

2x GatherMax 216 avg wipe peakVanilla

Procedural Map

214 ms· Chicago

Jitter4.2 ms

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.