Rust Server TrendsSeismic network · station log
Recording Stations11,535 Players86,112 Active4,004 Wipes · 3 h131 48 h

Station XX-16820 · no signal

build test

Offline 93.165.242.31:28815 checked 17d ago

Connect
Players now
0/ 1
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,820
top 70%
Last wipe
17d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-16820 · 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 1 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
15k10k15k20k4 Nov5 Nov6 Nov8 Nov9 Nov10 Nov

Top 70% 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
Thu 5 Nov, 19:00 UTC FW15d ago – – – – running –

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+ · 11 on average
21/ 101
Raichu Staging | F1 Spawn | Noclip | DLC Unlocked EU · groups of 8+ · 2 on average
7/ 25
Local Sandbox groups of 8+ · 1 on average
1/ 2
122/ 999
41/ 150
Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFA EU · groups of 30+ · weekly · 29 on average
20/ 100
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on build test?

A procedural map runs on build test, generated by the game.

Which settings and rules apply on build test?

The name of build test gives no gather rate. 9999 players is the most a group can hold. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. It is a community server, and the browser lists it under Community. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on build test?

build test is not responding at this moment and is offline, last seen 17 days 19 hours ago.

How does build test rank against other Rust servers?

Over the last seven days, build test recorded enough player hours to reach #16,820 worldwide, placing it in the top 70% of all ranked servers.

Server facts

How reliably does build test stay online?

No contact with build test right now, and the last recorded contact was 17 days 19 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 3 November 2026 is when Rust Server Trends first recorded it.

Where in the world is build test hosted?

A region is not published by build test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 93.165.242.31:28815.

What build of Rust does build test use?

build test is running Rust network protocol 2635 and build 168909 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe day

On what timetable does build test run its wipes?

On record so far are too few of build test's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 3 December at 19:00 UTC. 17 days 19 hours is how long the current world has been running.

Server tags

What do the server tags on build test mean?

These are the tags build test publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp1 (Max players): The server has 1 slots; ts9999 (Group limit): Each team can hold up to 9999; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $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 build test appear?

These Rust Server Trends lists include build test: 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.

Join the server

How do you connect to build test?

Enter client.connect 93.165.242.31:28815 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 mp1,ptrak,$r?,v2635,gmrust,cs168909,ts9999

Game

gmrust
Game mode You'll find standard Rust survival here.
mp1
Max players The server has 1 slots.
ts9999
Group limit Each team can hold up to 9999.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build Game build: 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$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.