Rust StatisticsWorking papers on every public Rust server · 53,885 players now

Local Custom Map Test

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 11h ago · 185.181.220.138:28015

Abstract

We describe the public Rust server Local Custom Map Test, reached at 185.181.220.138:28015. It is offline at the last check, against a seven-day mean of 1 and a peak of 21. It ranks #9,812 of all servers, the top 44%. It last wiped 12h ago.

Keywordsrust server

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now1/425% full
In the queue0no queue
Seven-day mean1peak 2, 48 h peak 2
Rank2#9,812top 44%
Last wipe12h agono schedule published
Next wipe3–no rhythm it keeps

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeakWipe
00.511.5220:0021:0022:00Wiped Tue 27 Oct, 20:08 UTCWIPE
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: Server performance. 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.

4Rank

The server stands in the top 44% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
12.5k5k7.5k10k21 Oct23 Oct24 Oct26 Oct27 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap3.6 daysbetween real wipes
On rhythm0%of its recent wipes
Wipe-day peak2players, last three wipes
00.511.52+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Wed 28 Oct, 21:4712h ago – – running 1
Tue 27 Oct, 20:081d ago – – – 1
Wed 21 Oct, 19:037d ago 2 – 6 d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of Local Custom Map Test
Figure 5: The map: Custom Map, size 4000, seed 1337.
Table 4: The server's published settings.
Address185.181.220.138:28015
Region–
Max players4
Group limit8, the default
Wipe schedule–
Last wipe28 Oct 2026, 21:47 UTC
Hostname–
First seen21 Oct 2026
MapCustom Map
Size4000
Seed1337

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are unmodded rust community servers [2] and predicted wipe schedule [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 519 on average368/400
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average328/350
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average34/250
Rustoria.co - EU MainEU · groups of 16+ · weekly · 276 on average34/250
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average48/100
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 244 on average166/200

Appendix AQuick answers

From the figures on this page.

Server details

A.1Is the performance of Local Custom Map Test smooth?

Its average server fps over the last 48 hours was 149, with a minimum of 149. Buildings, deployables and all other world objects counted together reached a maximum of 94,500 entities. Memory use peaked at 1,666 MB. Players experience lag when fps is low and the entity count is rising.

A.2What location does Local Custom Map Test have?

A region is not published by Local Custom Map Test. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 185.181.220.138:28015.

A.3What is the reliability of Local Custom Map Test, and is it online?

Right now, Local Custom Map Test is offline, and the last time it was seen was 11 hours ago. It last restarted around 15 minutes ago, according to its reported uptime. Its uptime over the last full days (7 days) was 2%, with 3 of 168 hours online. It was first observed on 21 October 2026 by Rust Statistics.

A.4What is the Rust version for Local Custom Map Test?

The version of Rust on Local Custom Map Test is network protocol 2635 and build 168909, and the operating system is Windows. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.5What schedule does Local Custom Map Test follow for wipes?

With irregular wipe times, Local Custom Map Test offers no next wipe to predict. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The world currently in use was created 12 hours ago.

A.6How would you describe wipe day on Local Custom Map Test?

Recent wipes saw an average peak of 2 players. The peak on the latest wipe came 0 hours after it began.

Player count

A.7What position does Local Custom Map Test occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts Local Custom Map Test at #9,812, within the top 44% of ranked servers.

A.8What is the population level of Local Custom Map Test?

Local Custom Map Test is not online now; 11 hours have passed since it was last seen. Over the last week the count averages 1 players and reaches 2 at its height. Of the last 48 hours, the peak hour falls at 22:00 UTC, with an average of 2 players.

Tags and filters

A.9How should the tags on Local Custom Map Test be interpreted?

The game's server browser reads gmrust (Game mode): This is survival as standard Rust plays; mp4 (Max players): 4 slots are available; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set, which Local Custom Map Test publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can Local Custom Map Test be found among the Rust Statistics lists and filters?

The Rust Statistics lists that Local Custom Map Test fits are: Rust community servers, measured. You will find it on the server list filtered by: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 24 hours.

Settings and map

A.11What are the settings and rules that govern Local Custom Map Test?

The name of Local Custom Map Test states no gather rate. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gathering, building and raiding, as the game is usually played. Fighting and raiding between players are both permitted. Community is its category in the server browser. The server has VAC on, Valve's anti-cheat.

A.12What map is in use on Local Custom Map Test?

The game generates Local Custom Map Test's procedural map at size 4,000, from seed 1337. Because size and seed determine the map, RustMaps can show it, linked from this page. The map is named Custom Map.

Connection

A.13What is the process for joining Local Custom Map Test?

Enter client.connect 185.181.220.138:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp4,ptrak,$r?,v2635,gmrust,cs168909,ts8.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp4Max players. 4 slots are available.
ts8Group limit. The team cap is 8, which is the game default.
v2635Protocol. Your game must run protocol 2635 to connect.
cs168909Build. This server runs game build 168909.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. A region code has not 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Unmodded rust community servers. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.