Rust Server TrendsSeismic network · station log
Recording Stations11,706 Players60,014 Active3,275 Wipes · 3 h128 48 h

Station NA-12647 · no signal

Legion Network | Detroit US | Custom Map

Offline NA 51.222.244.171:25575 checked 2h ago

moddedoxide
Connect
Players now
0/ 50
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#12,647
top 57% · #1374 in NA
Last wipe
8d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station NA-12647 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 50 slots
Motion · 24 h
M0.0steady+0 players
Channel 1 · calibrated

Players

AveragePeak
0123402:0011:0021:0005:0014:0023:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040002:0011:0021:0005:0014:0023:00

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
15k10k15k20k21 Oct23 Oct25 Oct26 Oct28 Oct30 Oct

Top 57% of all ranked servers, top 74% in NA. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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
Friendly Seattle: No KOS | Chill | Noob Friendly NA · groups of 8+ · biweekly · 41 on average
54/ 100
[US] Enardo - Random Farming - Small One Grid | OneGrid NA · groups of 8+ · 30 on average
37/ 50
[NA] Willjum's Solo Only | Thursday Wipes NA · groups of 8+ · weekly · 26 on average
93/ 100
Rust Degens - US Vanilla | Fridays NA · groups of 8+ · weekly · 15 on average
6/ 150
[NA] Willjum's Casual Solo/Duo Monthly NA · groups of 8+ · monthly · 14 on average
18/ 175
Hempville 420 No Kos Low Decay / Limited PvP NA · groups of 8+ · monthly · 7 on average
9/ 90
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Legion Network | Detroit US | Custom Map?

Generated by the game, the map on Legion Network | Detroit US | Custom Map is procedural, size 4,000 with seed 1337. You can view it on RustMaps from this page: the same size and seed produce the same map. You will find the map named Custom Map.

Which settings and rules apply on Legion Network | Detroit US | Custom Map?

No gather rate appears in the name of Legion Network | Detroit US | Custom Map. The group limit is 8 players, the game's default. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.

Population

What is the current population on Legion Network | Detroit US | Custom Map?

Legion Network | Detroit US | Custom Map is not responding at this moment and is offline, last seen 2 hours ago. Across seven days this server recorded an average of 0 players and a peak of 1.

How does Legion Network | Detroit US | Custom Map rank against other Rust servers?

Legion Network | Detroit US | Custom Map is #1,374 in North America and #12,647 worldwide on the past week's player hours, within the top 57% of ranked servers.

Server details

How reliably does Legion Network | Detroit US | Custom Map stay online?

No contact with Legion Network | Detroit US | Custom Map right now, and the last recorded contact was 2 hours ago. Its reported uptime points to a restart about 6 days 21 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. 21 October 2026 is when Rust Server Trends first recorded it.

How well does Legion Network | Detroit US | Custom Map perform under load?

Across the last 48 hours it averaged 201 server fps, with a floor of 176. Buildings, deployables and all the rest of the world's entities brought it to a high of 98,262. Memory use peaked at 4,111 MB. What you feel as lag is the combination of low fps and a rising entity count.

Which region does Legion Network | Detroit US | Custom Map run from?

The NA tag is how Legion Network | Detroit US | Custom Map lists itself in North America. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 51.222.244.171:25575 is the address it uses.

What build of Rust does Legion Network | Detroit US | Custom Map use?

Rust network protocol 2635 and build 168909 on Linux is what Legion Network | Detroit US | Custom Map runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

How often does Legion Network | Detroit US | Custom Map wipe, and on which days?

On record so far are too few of Legion Network | Detroit US | Custom Map's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 8 days 23 hours is how long the current world has been running.

Server tags

What do the server tags on Legion Network | Detroit US | Custom Map mean?

The game's server browser reads the tags Legion Network | Detroit US | Custom Map publishes: gmrust (Game mode): Survival in standard Rust; mp50 (Max players): The server has 50 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; NA (North America): In the server browser it appears under North America. 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 Legion Network | Detroit US | Custom Map appear?

You will find Legion Network | Detroit US | Custom Map on the following Rust Server Trends lists: Modded Rust servers, tracked live and North America Rust servers. You will find it under these filters on the server list: Region: North America; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Connecting

How do you connect to Legion Network | Detroit US | Custom Map?

Enter client.connect 51.222.244.171:25575 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. For the website, go to https://discord.com/invite/jsSEd8JUn5.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,NA,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp50
Max players The server has 50 slots.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

Region

NA
North America In the server browser it appears under North America.

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.