Rust PopulationField survey · Rust servers
Observing 90,153 players 11,869 servers 3,832 with someone on 374 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 8,895habitat unknownfirst seen 21 Oct 2026

Local Custom Map Test

Offline 185.181.220.138:28015 checked 1h ago

Measurements

Players now
1/ 4
= 1 player
25% full
7-day average
1
peak 2
Rank
#8,895
top 40%
Last wipe
2h ago
no schedule published
Next wipe
–
no rhythm it keeps
Obs. 1 · sightings

Players

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

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

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.

Obs. 3 · standing

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.

Obs. 4 · the wipe cycle

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.

1.1 days
usual gap
between real wipes
33%
on rhythm
of its recent wipes
2
wipe-day peak
players, 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.

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 12:28 UTC2h ago – – running 1
Wed 28 Oct, 21:47 UTC17h ago – – – 1
Tue 27 Oct, 20:08 UTC1d ago – – – 1
Wed 21 Oct, 19:03 UTC7d 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.

Field questions

Quick answers

from the figures on this page

Population

How does Local Custom Map Test rank against other Rust servers?

The last seven days of player hours place Local Custom Map Test at #8,895, within the top 40% of all ranked servers.

How busy is Local Custom Map Test?

We have no live count for Local Custom Map Test right now. It was last seen 1 hours ago. We counted an average of 1 players in the past week, with 2 at the busiest. Look at the last 48 hours and 22:00 UTC stands out: it averaged 2 players.

Lists and tags

What do the server tags on Local Custom Map Test mean?

What the game's server browser reads from Local Custom Map Test is this set of tags: gmrust (Game mode): Survival in the standard Rust style; mp4 (Max players): The server has 4 slots; ts8 (Group limit): This is the game default: at most 8 per team; v2635 (Protocol): The protocol is 2635; a different version will not connect; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): No region code is set. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.

Which Rust Population lists and filters include Local Custom Map Test?

On Rust Population, Local Custom Map Test is filed under these lists: Community servers, field-listed. Look for it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 24 hours.

Wipe notes

What does wipe day look like on Local Custom Map Test?

The busiest point of its recent wipes averaged 2 players. 0 hours after the latest wipe the crowd peaked.

What is the wipe schedule on Local Custom Map Test?

There is no next wipe to predict: Local Custom Map Test wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. Counted from 2 hours ago, that is how long the current world has stood.

Map and rules

Which map does Local Custom Map Test run?

The map on Local Custom Map Test is procedural, made by the game at size 4,000 from seed 1337. The map follows from its size and seed, and RustMaps shows it from this page. The name on the map is Custom Map.

What are the rules and settings on Local Custom Map Test?

The name tells you nothing about gather rates: Local Custom Map Test states none. No limit is set beyond the standard 8 players per group. survival is what it runs, raid, build and gather: the standard game. Fighting and raiding between players is allowed. You will find it under Community: it is a community server. VAC, Valve's anti-cheat, runs here.

About the server

Which version of Rust does Local Custom Map Test run?

Rust network protocol 2635 and build 168909 on Windows is what Local Custom Map Test uses. Your game needs the same protocol to join; Steam takes care of updating it.

Does Local Custom Map Test run smoothly?

It ran at 146 server fps on average over the last 48 hours, and never went below 142. Entities peaked at 94,500, including buildings, deployables and everything else. The highest memory usage was 1,804 MB. What players experience as lag comes from low fps and a rising entity count.

Is Local Custom Map Test online, and how reliable is it?

We last saw Local Custom Map Test 1 hours ago, and it is offline now. About 33 minutes ago, it restarted, according to its uptime. Over the last 7 full days, 3 of 168 hours were online, or 2%. The first sighting by Rust Population was on 21 October 2026.

Where is Local Custom Map Test located?

A region is not published by Local Custom Map Test. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. Connect at 185.181.220.138:28015.

How to join

How do I join Local Custom Map Test?

Either enter client.connect 185.181.220.138:28015 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected.

Key to its markings

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust style.
mp4
Max players The server has 4 slots.
ts8
Group limit This is the game default: at most 8 per team.
v2635
Protocol The protocol is 2635; a different version will not connect.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet is the network layer here, as standard for the game.
$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.