StatusLive Servers online11,744 Players55,501 Populated3,172 Wiped · 3 h123 Interval5 min Date30 OCT 2026

DWG RG-S8920Server sheetchecked 11h ago

Local Custom Map Test

Offline 185.181.220.138:28015 checked 11h ago

Connect
Players now 1/ 4 25% full
7-day average1peak 2
Rank#8,920top 40%
Last wipe12h agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeakWipe
00.511.5221:0022:0012:0013:00Wiped Wed 28 Oct, 21:47 UTCWIPE

Hourly average and peak, UTC.

Fig. 1Players on Local Custom Map Test
Fig. 2

Server performance

Server fpsWipe
05010015020021:0022:0012:0013:00Wiped Wed 28 Oct, 21:47 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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k21 Oct23 Oct25 Oct26 Oct28 Oct30 Oct

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

Fig. 3Rank on player hours, daily
Schedule

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

Tue 27 OctWed 21 Oct
00.511.52+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 12:28 UTC12h ago – – running 1
Wed 28 Oct, 21:47 UTC1d ago – – – 1
Tue 27 Oct, 20:08 UTC2d ago 2 – 1.1 days 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 491 on average
72 / 250
02
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average
106 / 200
03
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 284 on average
327 / 350
04
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 277 on average
20 / 100
05
Rustoria.co - EU MainEU · groups of 16+ · weekly · 266 on average
419 / 450
06
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 253 on average
304 / 325
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

How reliable is Local Custom Map Test, and is it online now?

The current state of Local Custom Map Test is offline, with the last sighting 11 hours ago. The uptime it reports puts the last restart at about 33 minutes ago. For the last 7 full days the record is 5 of 168 hours up, 3% of the time. First seen by Rust Graphs on 21 October 2026.

How does Local Custom Map Test perform, as measured?

Average server fps over the last 48 hours is 146; the lowest was 142. Counted at its highest: 94,500 entities, buildings, deployables and the rest of the world included. 1,804 MB is the memory peak. A climbing entity count and low fps are the source of what players feel as lag.

What location is recorded for Local Custom Map Test?

No region is published by Local Custom Map Test. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 185.181.220.138:28015.

What Rust version is recorded for Local Custom Map Test?

On Windows, Local Custom Map Test runs Rust network protocol 2635 and build 168909. Steam updates your game, which must be on the same protocol for you to join.

Population

What player count is recorded on Local Custom Map Test?

Local Custom Map Test is not responding at the latest refresh; the last record of it online is 11 hours ago. Averaged across seven days, the player count is 1, with a peak of 2. The 48-hour peak falls at 22:00 UTC, averaging 2 players.

What rank has been recorded for Local Custom Map Test?

Over the last seven days, Local Custom Map Test records #8,920 for player hours: the top 40% of all ranked servers.

Wipe data

On Local Custom Map Test, what does the data show for wipe day?

At their busiest, its recent wipes drew 2 players on average. At 25 hours after the latest wipe the crowd was at its peak.

Which times and days are wipes plotted at on Local Custom Map Test?

Local Custom Map Test wipes at times that follow no pattern, so no next wipe can be predicted. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. 12 hours ago the current world was made.

Settings

What settings and rules apply on Local Custom Map Test?

No gather rate is stated in the name of Local Custom Map Test. The group limit is 8 players, the game's default. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. The server browser lists it under Community. Anti-cheat: VAC, from Valve, is on.

What is the map for Local Custom Map Test?

Size 4,000 with seed 1337: that is the procedural map Local Custom Map Test runs, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map. The name of the map reads: Custom Map.

Filters

On Rust Graphs, which lists and filters contain Local Custom Map Test?

The Rust Graphs lists that carry Local Custom Map Test are: Rust community servers, plotted. On the server list, these filters bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 24 hours.

On Local Custom Map Test, what is meant by each tag?

The game's server browser reads these tags from Local Custom Map Test: gmrust (Game mode): Standard survival, as Rust plays; mp4 (Max players): The slot count is 4; ts8 (Group limit): The default team size of 8 applies; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

Joining the server

How is Local Custom Map Test joined?

Enter client.connect 185.181.220.138:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Standard survival, as Rust plays.
mp4
Max players The slot count is 4.
ts8
Group limit The default team size of 8 applies.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not 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.

KeyTag string decoded