Skip to the page
Network live 11,618 servers online 32,056 players aboard 68 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

Local Custom Map Test

Offline 185.181.220.138:28015 checked 6h ago

Tracking number · connect
Wipe progress · wiped 7h ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –no rhythm it keeps
1/ 4 players now 25% full
17-day averagepeak 2
#9,816ranktop 44%
7h agolast wipeno schedule published
–next wipeno rhythm it keeps
Delivery history

Players, performance and rank

Players

AveragePeakWipe
00.511.5220:0021:0022:00Wiped Tue 27 Oct, 20:08 UTCWIPE

Hourly average and peak, UTC.

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 21 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k21 Oct23 Oct24 Oct26 Oct27 Oct29 Oct

Top 44% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

3.6 daysusual gapbetween real wipes
0%on rhythmof its recent wipes
2wipe-day peakplayers, last three wipes

The first 48 hours of its last wipes

00.511.52+0h+9h+19h+28h+38h+47h

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

Wipes

every wipe as a delivery, newest first
  1. Wed 28 Oct, 21:47 UTC 21:47 UK · 7h ago
    Wipe delivered
    Peak
    –
    Crowd
    –
    Lasted
    running
    Players before
    1
  2. Tue 27 Oct, 20:08 UTC 20:08 UK · 1d ago
    Wipe delivered
    Peak
    –
    Crowd
    –
    Lasted
    –
    Players before
    1
  3. Wed 21 Oct, 19:03 UTC 20:03 UK · 7d ago
    Wipe delivered
    Peak
    2
    Crowd
    –
    Lasted
    6 days
    Players before
    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 parcels

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 542 on average 154 / 250
  2. Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average 127 / 200
  3. Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average 15 / 250
  4. Rustoria.co - EU MainEU · groups of 16+ · weekly · 283 on average 17 / 250
  5. Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average 13 / 100
  6. Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 249 on average 43 / 200
Help desk

Quick answers

From the figures on this page.

Population

Where does Local Custom Map Test place among Rust servers?

A seven-day player-hours count places Local Custom Map Test at #9,816: the top 44% of every ranked server.

Is Local Custom Map Test busy at the moment?

The last sighting of Local Custom Map Test was 6 hours ago; it is offline right now. The seven-day figures show an average of 1 players and a peak of 2. Over the last 48 hours, the peak hour came at 22:00 UTC with an average of 2 players.

Server rules

Which map is active on Local Custom Map Test?

The game generates the procedural map on Local Custom Map Test at size 4,000 with seed 1337. Identical size and seed give an identical map: view it on RustMaps from this page. Its name for the map: Custom Map.

What settings and rules should you know for Local Custom Map Test?

The name of Local Custom Map Test gives no gather rate. 8 players is the group limit, since the game's default applies. It runs survival, gather and build and raid: the standard game. You can raid and fight other players. The server browser files it under Community, as a community server. VAC, Valve's anti-cheat, is switched on.

Operator and location

What is the location of Local Custom Map Test?

There is no region published for Local Custom Map Test. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. The address to connect to is 185.181.220.138:28015.

What is the performance like on Local Custom Map Test?

Averaged over the last 48 hours, server fps was 149, with a low of 149. The world held as many as 94,500 entities: buildings, deployables and the rest. 1,666 MB of memory was its top figure. What players call lag is the mix of low fps and an entity count that keeps climbing.

Is Local Custom Map Test up, and how good is its uptime?

Offline for now: Local Custom Map Test was last seen 6 hours ago. The uptime it reports puts its last restart at about 15 minutes ago. It was up 3 of 168 hours over the last 7 full days, 2% of the time. It was first seen by Rust Wipe Tracker on 21 October 2026.

On what Rust version does Local Custom Map Test operate?

Rust network protocol 2635 and build 168909 on Windows is what Local Custom Map Test runs. To join, your game must be on the same protocol; Steam handles that update for you.

Wipe schedule

How does Local Custom Map Test handle its wipe days?

The average busiest point of its recent wipes was 2 players. On the latest wipe, 0 hours passed before the crowd peaked.

How often does Local Custom Map Test wipe, and at what times?

There is no next wipe to predict for Local Custom Map Test: it wipes at irregular times. The monthly force wipe takes every Rust server with it, and Thursday 5 November at 19:00 UTC is the next one. You are playing a world created 7 hours.

Tags and filters

Where does Local Custom Map Test appear in Rust Wipe Tracker lists and filters?

These Rust Wipe Tracker lists take Local Custom Map Test: Rust community servers, unmodded. On the server list, apply Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 24 hours and it appears.

What is the meaning of the server tags on Local Custom Map Test?

Read off the game's server browser, the tags for Local Custom Map Test are: gmrust (Game mode): Survival in standard Rust; mp4 (Max players): Slot count: 4; ts8 (Group limit): 8 per team, which is the default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): No region code is set. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.

Connecting

What is the process to join Local Custom Map Test?

Enter client.connect 185.181.220.138:28015 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you.

Server tags

what each one means

Published as mp4,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp4
Max players Slot count: 4.
ts8
Group limit 8 per team, which is the default.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code No region code is set.

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.