Rust Server TrendsSeismic network · station log
Recording Stations11,641 Players44,965 Active3,093 Wipes · 3 h105 48 h

Station XX-14206 · no signal

Local Builder Test

Offline 31.30.165.49:28015 checked 42d ago

Connect
Players now
0/ 2
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,206
no region published
Last wipe
43d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-14206 · 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
0of 2 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
15k10k15k20k20 Sep21 Sep22 Sep23 Sep
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
12/ 101
Raichu Staging | F1 Spawn | Noclip | DLC Unlocked EU · groups of 8+ · 2 on average
0/ 25
59/ 999
35/ 999
99/ 150
Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFA EU · groups of 30+ · weekly · 37 on average
1/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Local Builder Test?

The map on Local Builder Test is procedural, produced by the game.

Which settings and rules apply on Local Builder Test?

The name of Local Builder Test gives no gather rate. The group limit is 8 players, the game's default. 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. VAC, Valve's anti-cheat, is switched off.

Population

What is the current population on Local Builder Test?

A reading taken now finds Local Builder Test offline; the most recent activity was 42 days 18 hours ago.

How does Local Builder Test rank against other Rust servers?

Over the last seven days, Local Builder Test recorded enough player hours to reach #14,206 worldwide, placing it in the top – of all ranked servers.

Server details

How reliably does Local Builder Test stay online?

Local Builder Test is down at the moment; the last recorded contact was 42 days 18 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 15 September 2026 is when Rust Server Trends first recorded it.

Where in the world is Local Builder Test hosted?

No region is published by Local Builder Test. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 31.30.165.49:28015.

What build of Rust does Local Builder Test use?

Rust network protocol 2633 and build 163794 on Windows is what Local Builder Test runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

How often does Local Builder Test wipe, and on which days?

The rhythm of Local Builder Test cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 43 days 10 hours.

Server tags

What do the server tags on Local Builder Test mean?

The game's server browser reads the tags Local Builder Test publishes: gmrust (Game mode): Survival in standard Rust; mp2 (Max players): Slots: 2; 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; cs163794 (Build): Game build: 163794; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set. 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 Builder Test appear?

The Rust Server Trends lists that take in Local Builder Test are: Rust build and creative servers, live and Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How to join

How do you connect to Local Builder Test?

You can connect by pressing F1 in Rust and typing client.connect 31.30.165.49: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 mp2,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp2
Max players Slots: 2.
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.
cs163794
Build Game build: 163794.
ptrak
Networking The network layer is RakNet, the game's standard.
$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.

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.