Rust Server TrendsSeismic network · station log
Recording Stations11,732 Players69,328 Active3,614 Wipes · 3 h126 48 h

Station XX-14109 · no signal

Local Build

Offline 94.41.131.16:28015 checked 26d ago

Connect
Players now
1/ 10
10% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,109
top 60%
Last wipe
28d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-14109 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of 10 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

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. 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
15k10k15k20k1 Oct2 Oct4 Oct5 Oct7 Oct8 Oct

Top 60% of all ranked servers. 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
【南瓜】Build-Test EA · groups of 8+ · 10 on average
17/ 101
Raichu Staging | F1 Spawn | Noclip | DLC Unlocked EU · groups of 8+ · 1 on average
1/ 25
154/ 999
34/ 999
98/ 150
Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFA EU · groups of 30+ · weekly · 36 on average
54/ 100
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Local Build?

Local Build uses a procedural map, which the game generates.

Which settings and rules apply on Local Build?

No gather rate appears in the name of Local Build. At the game's default, groups can have up to 8 players. In survival mode, gather, build and raid in the standard game. You can raid and fight other players here. Under Community in the server browser, it runs as a community server. The server has VAC off, Valve's anti-cheat.

Population

How many players are recorded on Local Build right now?

No players are recorded on Local Build at this moment; it is offline, and the last sighting was 26 days 20 hours ago.

How does Local Build rank against other Rust servers?

Over the last seven days, Local Build recorded enough player hours to reach #14,109 worldwide, placing it in the top 60% of all ranked servers.

Server details

How reliably does Local Build stay online?

No contact with Local Build right now, and the last recorded contact was 26 days 20 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 1 October 2026 is when Rust Server Trends first recorded it.

Which region does Local Build run from?

No region is published by Local Build. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 94.41.131.16:28015 is the address it uses.

Which Rust version is Local Build running?

On Linux, Local Build runs Rust network protocol 2633 and build 165217. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe schedule

How often does Local Build wipe, and on which days?

Too few wipes of Local Build are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 28 days 11 hours.

Server tags

What do the server tags on Local Build mean?

These are the tags Local Build publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): 10 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs165217 (Build): It runs game build 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does Local Build appear?

These Rust Server Trends lists include Local Build: Rust build and creative servers, live and 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.

Connecting

How do you connect to Local Build?

You can connect by pressing F1 in Rust and typing client.connect 94.41.131.16:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp10
Max players 10 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2633
Protocol To connect, your game must be on the same protocol, 2633.
cs165217
Build It runs game build 165217.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is set for this server.

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.