Rust Server IndexCard catalogue of Rust servers

Holdings11,757 servers71,129 players212 fresh wipes

Call no.8912 Off the shelf · offline

Local Custom Map Test

Offline 185.181.220.138:28015 checked 9h ago

Subjects
Players now
1/ 4
25% full
7-day average
1
peak 2
Rank
#8,912
top 40%
Last wipeWiped29 OCT2026 · 10h ago
10h ago · no schedule published
Next wipe
–
no rhythm it keeps
Call slipPaste it into the F1 console
Record sheet A · appended

Players

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

Hourly average and peak, UTC.

Record sheet B · appended

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.

Record sheet C · appended

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.

Record sheet D · loan terms

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

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

Record sheet E · date due

Wipes

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

Shelf list · shelved beside it

Similar servers

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

EU
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 499 on average
140/ 250
EU
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average
173/ 250
EU
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 283 on average
535/ 675
EU
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 277 on average
29/ 100
EU
Rustoria.co - EU MainEU · groups of 16+ · weekly · 266 on average
619/ 775
EU
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 248 on average
523/ 625
Reference desk

Quick answers

From the figures on this page.

Rules and settings

What settings and rules does Local Custom Map Test run?

No gather rate appears in the name Local Custom Map Test. The default group limit of 8 players applies. The server runs survival, building, gathering and raiding in the standard game. Fighting and raiding other players is permitted. Filed under Community in the server browser, it is a community server. VAC is on: Valve's anti-cheat is enabled.

Which map is in use on Local Custom Map Test?

Local Custom Map Test runs a procedural map of size 4,000 with seed 1337, generated by the game. The map can be seen on RustMaps from this page, because the same size and seed give the same map. Filed under map name: Custom Map.

Tags and filters

Where does Local Custom Map Test appear among the Rust Server Index lists and filters?

The Rust Server Index lists that include Local Custom Map Test are Community Rust servers, indexed. These filters on the server list 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.

How should you read the tags listed for Local Custom Map Test?

Filed under these tags, as published by Local Custom Map Test and read by the game's server browser: gmrust (Game mode): Survival on standard Rust rules; mp4 (Max players): Player cap: 4; ts8 (Group limit): The team limit is 8, as in the standard game; v2635 (Protocol): Joining needs you on game protocol 2635; cs168909 (Build): It runs build 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): No region code has been set. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.

Wipe dates

How does a wipe day run on Local Custom Map Test?

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

Which wipe timetable does Local Custom Map Test follow?

There is no next wipe to predict for Local Custom Map Test, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. Its present world dates from 10 hours.

Population

How is Local Custom Map Test ranked compared with the rest?

Filed under rankings: #8,912 for Local Custom Map Test on seven-day player hours, top 40% overall.

What does the player count on Local Custom Map Test look like?

At present Local Custom Map Test is offline; its last sighting was 9 hours ago. The seven-day average is 1 players; the peak reached 2. Filed under busiest hour: 22:00 UTC in the last 48 hours, averaging 2 players.

Server facts

What version does Local Custom Map Test use?

Rust network protocol 2635 and build 168909, on Windows, is what Local Custom Map Test runs. To join you need the same protocol; Steam handles the update.

What is the uptime and current status of Local Custom Map Test?

As of now Local Custom Map Test is offline, with its last appearance 9 hours ago. Its reported uptime gives the last restart as roughly 33 minutes ago. Uptime for the last 7 full days came to 2%, 3 hours out of 168. It was first recorded by Rust Server Index on 21 October 2026.

What is performance like on Local Custom Map Test?

Server fps held at 146 on average across the last 48 hours, never dropping below 142. The entity count reached 94,500, covering buildings, deployables and all else in the world. The peak memory figure stood at 1,804 MB. What players feel as lag is low fps together with a rising entity count.

What is the location of Local Custom Map Test?

There is no region on record for Local Custom Map Test; it publishes none. What Rust Server Index shows is the stated location, not the machine's actual position, which it does not look up. You will reach it at 185.181.220.138:28015.

How to join

What steps lead onto Local Custom Map Test?

Enter client.connect 185.181.220.138:28015 in the console, opened with F1. Or join on this page with Launch Rust, which opens Rust through Steam and connects you.

Subject headings explained

Server tags

What each one means.

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

Game

gmrust
Game mode Survival on standard Rust rules.
mp4
Max players Player cap: 4.
ts8
Group limit The team limit is 8, as in the standard game.
v2635
Protocol Joining needs you on game protocol 2635.
cs168909
Build It runs build 168909.
ptrak
Networking The standard RakNet layer carries the connection.
$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.