Rust Server TrendsSeismic network · station log
Recording Stations11,665 Players44,308 Active3,062 Wipes · 3 h99 48 h

Station XX-15258 · no signal

My Build Test

Offline 72.56.49.202:28015 checked 10d ago

Connect
Players now
0/ 1
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,258
top 70%
Last wipe
10d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-15258 · 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
15k10k15k20k17 Oct18 Oct20 Oct21 Oct23 Oct24 Oct

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
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
10/ 101
Raichu Staging | F1 Spawn | Noclip | DLC Unlocked EU · groups of 8+ · 1 on average
1/ 25
80/ 999
160/ 999
53/ 150
Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFA EU · groups of 30+ · weekly · 35 on average
12/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on My Build Test?

A procedural map runs on My Build Test, generated by the game.

Which settings and rules apply on My Build Test?

The name of My Build 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. Under Community in the server browser, it runs as a community server. The server has VAC on, Valve's anti-cheat.

Population

What is the current population on My Build Test?

A reading taken now finds My Build Test offline; the most recent activity was 10 days 6 hours ago.

How does My Build Test rank against other Rust servers?

The last seven days of player hours place My Build Test at #15,258, in the top 70% of all ranked servers.

Operator and location

How reliably does My Build Test stay online?

As recorded now, My Build Test is not reachable, the last contact having been 10 days 6 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 17 October 2026.

Where in the world is My Build Test hosted?

A region is not published by My Build Test. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 72.56.49.202:28015 is the address it uses.

Which Rust version is My Build Test running?

Rust network protocol 2634 and build 167781 on Windows is what My Build Test runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

On what timetable does My Build Test run its wipes?

On record so far are too few of My Build Test's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 10 days 6 hours.

Tags

What do the server tags on My Build Test mean?

These are the tags My Build Test publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp1 (Max players): The server has 1 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): Game build: 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $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 My Build Test appear?

You will find My Build Test on the following Rust Server Trends lists: Rust build and creative servers, live and Rust community servers without the side modes. You will find it under these filters 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 2 weeks.

Connecting

How do you connect to My Build Test?

You can connect by pressing F1 in Rust and typing client.connect 72.56.49.202: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 mp1,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp1
Max players The server has 1 slots.
ts8
Group limit Teams max out at 8, the default set by the game.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs167781
Build Game build: 167781.
ptrak
Networking The network layer is RakNet, the game's standard.
$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.