RUST METRICSFlight deck · live data
Data live Servers11,598 Players34,006 Populated2,835 Fresh wipes 3 h67 Scan5 min
‹ All servers82.21.2.4:4110
Offline Full Queue Fresh wipe Wipe due No query

test 290011

Offline EA 82.21.2.4:4110 checked 4d ago

solo weekly wipes vanillaoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.8 1.5 2.2 3 PAX 1 /3

Players now

33% full 7-day avg7-day peak
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average1peak 1
Rank#13,146top 59% · #481 in EA
Last wipe4d agoweekly schedule
Next wipe2d 3hFri 30 Oct, 08:12 UTC
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 59% of all ranked servers, top 88% in EA, and #189 of the solo servers (top 87%). Ranked on player hours over the last seven days.

PLAN

Wipe schedule

fixed weekdays

Next wipe Friday 30 October, 08:12 UTC, in 2d 3h. Every Friday at 08:12 UTC · medium confidence

usual gap7 daysbetween real wipes
on rhythm80%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 3.5

Coming wipes

  1. WPT 1Fri 30 Oct, 08:12 UTC2d 3h
  2. WPT 2Thu 5 Nov, 19:00 UTC8d 14hFW
  3. WPT 3Fri 6 Nov, 08:12 UTC9d 3h
  4. WPT 4Fri 13 Nov, 08:12 UTC16d 3h
  5. WPT 5Fri 20 Nov, 08:12 UTC23d 3h
  6. WPT 6Fri 27 Nov, 08:12 UTC30d 3h
  7. WPT 7Thu 3 Dec, 19:00 UTC36d 14hFW
  8. WPT 8Fri 4 Dec, 08:12 UTC37d 3h

The first 48 hours of its last wipes

Fri 23 OctFri 16 OctFri 9 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 08:12 UTC4d ago 1 – running 0
Fri 16 Oct, 07:51 UTC11d ago 1 halved by day 2 7 days 0
Fri 9 Oct, 08:24 UTC18d ago 1 halved by day 5 7 days 0
Fri 2 Oct, 04:43 UTC25d ago 1 held half 7.2 days 0
Fri 25 Sep, 06:28 UTC32d ago 1 held half 6.9 days 2

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What should you expect from wipe day on test 290011?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours. Until the next wipe, the crowd stayed above half that peak in 50% of its recent wipes. It fell below half by day 3.5 when it didn't.

What wipe timing does test 290011 follow?

every Friday at 08:12 UTC is how test 290011 wipes. Friday 30 October at 08:12 UTC is when its next wipe is due. 4 days 20 hours ago the current world was made. The tags state a wipe schedule of one wipe a week.

Tags

Which tags does test 290011 carry, and what do they mean?

These are the tags test 290011 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp3 (Max players): The server holds 3 slots; ts1 (Group limit): Team cap: 1; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^w (Weekly): It wipes each week; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^o (Oxide): It runs Oxide, also known as uMod; EA (East Asia): East Asia is the browser category it sits in. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does test 290011 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry test 290011: Rust community servers: live readings, Solo-only Rust servers and Vanilla Rust servers, live. Check: filters. On the server list it appears under these: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Weekly ^w, Vanilla ^v and Oxide ^o; Group limit: Solo; Wipe schedule: Weekly; Last wipe: In the last week.

Player count

What position does test 290011 hold among Rust servers?

Ranked by seven-day player hours, test 290011 sits at #13,146 and #481 in Asia, inside the top 59%. The solo group places it at #189.

What player count does test 290011 carry?

Status for test 290011: offline. Last seen 4 days 20 hours ago. Seven-day check: 1 players on average. Peak reading: 1.

Operator and location

Which location does test 290011 run from?

test 290011 gives Asia as its location, with the EA tag. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 82.21.2.4:4110.

What Rust version is test 290011 on?

Reading: test 290011, Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on test 290011, and is it online?

Reading: offline. test 290011 last answered 4 days 20 hours ago. Uptime for the last 7 full days: 1 of 168 hours, or 1%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Map and rules

What rules does test 290011 enforce, and what are its settings?

No gather rate appears in the name: test 290011. Teams: none. The server is solo only. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: plugins. It runs Oxide of them. Vanilla is the label it uses: the stock game: Facepunch's rates, kits and rules, unchanged. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on test 290011?

Check: map. Procedural, size 3,500, seed 1337, generated by the game on test 290011. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Its map carries the name Custom Map.

Connection

What do you do to join test 290011?

To join: start Rust, press F1 and type client.connect 82.21.2.4:4110. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp3,ptrak,$r?,v2635,^w,^v,EA,gmrust,cs168909,ts1,^o

Game

gmrust
Game mode The game mode is plain Rust survival.
mp3
Max players The server holds 3 slots.
ts1
Group limit Team cap: 1.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Wipe schedule

^w
Weekly It wipes each week.

Difficulty

^v
Vanilla The stock game: Facepunch's rates, kits and rules, unchanged.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.

Region

EA
East Asia East Asia is the browser category it sits in.

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.