Rust Server Analytics 102,455 players11,892 servers
All servers
Drill-through Server detail

Local Custom Map Test

Offline 185.181.220.138:28015 checked 5h ago

Drill-through
FilterServeris Local Custom Map Test
Attributes
Last refreshed
Players now 1/ 4
7-day average 1 peak 2
Rank #8,882 top 40%
Last wipe 6h ago no schedule published
Next wipe – no rhythm it keeps
Capacity 25% full

Players

average and peak, with its wipes marked
AveragePeakWipe
00.511.5220:0021:0022:0012:0013:00Wiped Tue 27 Oct, 20:08 UTCWIPE

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
Server fpsWipe
05010015020020:0021:0022:0012:0013:00Wiped Tue 27 Oct, 20:08 UTCWIPE

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 40% 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.

usual gap1.1 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak2players, 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

newest first
WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 12:28 UTC6h ago – – running 1
Wed 28 Oct, 21:47 UTC21h ago – – – 1
Tue 27 Oct, 20:08 UTC1d ago – – – 1
Wed 21 Oct, 19:03 UTC8d ago 2 – 6 days 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 servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 510 on average 315 / 375
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 317 on average 430 / 475
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 281 on average 958 / 1000
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 276 on average 45 / 100
eulongtest (private perf box) EU · groups of 14+ · monthly · 267 on average 480 / 8
Rustoria.co - EU Main EU · groups of 16+ · weekly · 266 on average 988 / 1000

Quick answers

from the figures on this page

Wipe data

On what cycle does Local Custom Map Test wipe?

The next wipe on Local Custom Map Test cannot be predicted, because it wipes at irregular times. The next force wipe, which every Rust server receives, is on Thursday 5 November at 19:00 UTC. 6 hours ago the current world was made.

On Local Custom Map Test, what happens on wipe day?

Across recent wipes the busiest point averaged 2 players. Peak population for the latest wipe came 0 hours after it began.

Server

Which location hosts Local Custom Map Test?

No region is published by Local Custom Map Test. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. 185.181.220.138:28015 is its address.

Which Rust version is Local Custom Map Test on?

The platform is Windows, with Rust network protocol 2635 and build 168909 running on Local Custom Map Test. Joining requires the same protocol on your game; Steam handles the update.

What uptime does Local Custom Map Test show, and is it up?

Last seen 5 hours ago, Local Custom Map Test now reports offline. Its reported uptime indicates a restart roughly 33 minutes ago. 2% uptime over the last 7 full days, equal to 3 of 168 hours. It entered Rust Server Analytics records on 21 October 2026.

What performance does Local Custom Map Test show?

Server fps averaged 146 over the last 48 hours, with a floor of 142. Buildings, deployables and all other world objects brought the entity total to 94,500. At its highest, memory use was 1,804 MB. Lag, for players, means low fps alongside a growing entity count.

Lists and tags

How should the tags on Local Custom Map Test be read?

The game's server browser reads the tags Local Custom Map Test publishes: gmrust (Game mode): Rust survival, standard ruleset; mp4 (Max players): Capacity of 4 slots; ts8 (Group limit): Team cap of 8, the stock game setting; v2635 (Protocol): Joining needs your game on protocol 2635; cs168909 (Build): Build number 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code has been set. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.

Where does Local Custom Map Test appear across Rust Server Analytics's lists and filters?

Among the Rust Server Analytics lists Local Custom Map Test fits are: Community Rust servers, live. It appears on the server list under the following filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 24 hours.

Player numbers

Against other Rust servers, how does Local Custom Map Test compare?

Player hours for the last seven days place Local Custom Map Test at #8,882, in the top 40% of the ranked field.

How many players does Local Custom Map Test carry?

No response from Local Custom Map Test at the latest check, with a last sighting 5 hours ago. Averaging 1 players across seven days, the server reached a peak of 2. Averaged over 48 hours, activity is highest at 22:00 UTC with 2 players.

Map and rules

What settings and rules does Local Custom Map Test use?

No gather rate is given in the name of Local Custom Map Test. The game's default 8-player group limit is in force. survival is the game mode, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. The Community category in the server browser lists it. Anti-cheat status: VAC on.

The map on Local Custom Map Test: which one is it?

Local Custom Map Test uses a procedural map of size 4,000 with seed 1337, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Named map: Custom Map.

Connection

How do you connect to Local Custom Map Test?

In the Rust console (F1), enter client.connect 185.181.220.138:28015. Launch Rust on this page also works, opening Rust through Steam and connecting you.

Server tags

what each one means

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

Game

gmrust
Game mode Rust survival, standard ruleset.
mp4
Max players Capacity of 4 slots.
ts8
Group limit Team cap of 8, the stock game setting.
v2635
Protocol Joining needs your game on protocol 2635.
cs168909
Build Build number 168909.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code No region code has been 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.