A Simple Rust Server

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

No reading yet from Chicago

Server admin? We haven't been able to get a ping reading for your server from Chicago yet, which can keep it from ranking well for players browsing that region. This usually means a firewall or DDoS-protection rule is blocking the brief, unsolicited connection check we send to your game port — the same kind of lightweight check the game client itself uses, separate from your server's normal browser-listing info. Allowing that check through on your game port should let us start measuring and showing an accurate ping for your server there.

Last checked 2 m ago

1 / 150 players

Procedural Map

1 day live Avg ping 140.3 ms Avg jitter 3 ms

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

Connect: 37.26.136.61: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 37.26.136.61: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 01.10.2026

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 1 Oct 1 · 21:47 UTC Median daily peak 1 (median of daily peaks, not average population)

Observed daily peak

01Oct 1Oct 3

3 full · 0 partial · 0 offline · 28 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.

Not enough wipe history yet to compare cycles — this fills in as more wipes complete.

Ping history from Chicago

141ms140.2msOct 1Oct 3

Jitter history

3.1ms1msOct 1Oct 3

Recent history from Chicago

Checked Status Ping Players
Offline 139 ms —
Offline 145 ms —
Offline 139 ms —
Offline 139 ms —
Offline 144 ms —
Offline 136 ms —
Offline 138 ms —
Offline 139 ms —
Offline 139 ms —
Offline 145 ms —
Offline 137 ms —
Offline 140 ms —
Offline 141 ms —
Offline 147 ms —
Offline 138 ms —
Offline 141 ms —
Offline 137 ms —
Offline 142 ms —
Offline 140 ms —

Other servers in Moldova (low ping)

NooBServeR | Classic ++

0/150

Last checked 2 m ago

Wiped 1 d ago

27% elapsed73% left

Next wipe in 5 days

Max 44 avg wipe peakVanilla

Procedural Map

137 ms· Chicago

Jitter2.8 ms

4/200

Last checked 2 m ago

Wiped 1 d ago

3 avg wipe peakVanilla

Procedural Map

138 ms· Chicago

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.