Rust Server TrendsSeismic network · station log
Recording Stations11,636 Players31,247 Active2,768 Wipes · 3 h72 48 h

Station XX-9816 · no signal

Local Custom Map Test

Offline 185.181.220.138:28015 checked 6h ago

Connect
Players now
1/ 4
25% full
Motion · 24 h
M0.0rising
+1 players on the day
7-day average
1
peak 2
Rank
#9,816
top 44%
Last wipe
7h ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-9816 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
1of 4 slots
Motion · 24 h
M0.0rising+1 players
Sharpest hour
+1into Wed 21:00 UTC
Peak · 48 h
2most players in any hour
Events picked
2wipes on this record, in red
Channel 1 · calibrated

Players

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

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k21 Oct23 Oct24 Oct26 Oct27 Oct29 Oct

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

Expected events

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
3.6 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
2players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 28 Oct, 21:47 UTC7h ago – – – – running 1
Tue 27 Oct, 20:08 UTC1d ago – – – – – 1
Wed 21 Oct, 19:03 UTC7d ago M0.0rising 2 – 6 days 1

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 542 on average
144/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
132/ 200
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
15/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 283 on average
22/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 274 on average
12/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 249 on average
49/ 200
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Local Custom Map Test?

The procedural map on Local Custom Map Test is size 4,000 with seed 1337, generated by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map. Its map carries the name Custom Map.

Which settings and rules apply on Local Custom Map Test?

No gather rate appears in the name of Local Custom Map Test. The group limit is 8 players, the game's default. It plays in survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. It is a community server, and the browser lists it under Community. The server has VAC on, Valve's anti-cheat.

Player counts

How many players are recorded on Local Custom Map Test right now?

A reading taken now finds Local Custom Map Test offline; the most recent activity was 6 hours ago. Across seven days this server recorded an average of 1 players and a peak of 2. The busiest point in the last 48 hours came at 22:00 UTC, averaging 2 players.

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

Over the last seven days, Local Custom Map Test recorded enough player hours to reach #9,816 worldwide, placing it in the top 44% of all ranked servers.

Server details

How reliably does Local Custom Map Test stay online?

No contact with Local Custom Map Test right now, and the last recorded contact was 6 hours ago. Its reported uptime points to a restart about 15 minutes ago. Of the 168 hours in the last 7 full days, it was up for 3, or 2% of the time. Its earliest appearance in the records of Rust Server Trends dates to 21 October 2026.

Does Local Custom Map Test hold a steady tick rate?

Its average server fps over the last 48 hours was 149, and it never dropped below 149. At its highest, it carried 94,500 entities: buildings, deployables and the world's other contents. Its highest memory use was 1,666 MB. Low fps together with a growing entity count is what players experience as lag.

Which region does Local Custom Map Test run from?

A region is not published by Local Custom Map Test. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 185.181.220.138:28015 is the address it uses.

Which Rust version is Local Custom Map Test running?

Local Custom Map Test is running Rust network protocol 2635 and build 168909 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

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

2 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.

On what timetable does Local Custom Map Test run its wipes?

There is no next wipe to predict at Local Custom Map Test, since its wipes fall at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 7 hours is how long the current world has been running.

Tags

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

These are the tags Local Custom Map Test publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp4 (Max players): Slots: 4; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): It runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does Local Custom Map Test appear?

The Rust Server Trends lists that take in Local Custom Map Test are: Rust community servers without the side modes. These filters bring it up 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.

How to join

What steps get you onto Local Custom Map Test?

Enter client.connect 185.181.220.138:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp4
Max players Slots: 4.
ts8
Group limit Teams max out at 8, the default set by the game.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build It runs game build 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.