Rust Server TrendsSeismic network · station log
Recording Stations11,841 Players77,907 Active3,836 Wipes · 3 h160 48 h

Station XX-13136 · no signal

My Build Server

Offline 78.37.179.103:28015 checked 14d ago

Connect
Players now
1/ 50
2% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#13,136
top 61%
Last wipe
14d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-13136 · 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 50 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
15k10k15k20k13 Oct14 Oct16 Oct17 Oct19 Oct20 Oct

Top 61% 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
7/ 101
Raichu Staging | F1 Spawn | Noclip | DLC Unlocked EU · groups of 8+ · 1 on average
2/ 25
172/ 999
110/ 999
27/ 150
Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFA EU · groups of 30+ · weekly · 35 on average
19/ 100
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on My Build Server?

My Build Server uses a procedural map, which the game generates.

Which settings and rules apply on My Build Server?

You will find no gather rate in the name of My Build Server. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, gather, build and raid in the standard game. You can raid and fight other players here. It is a community server, and the browser lists it under Community. Anti-cheat is off: VAC, from Valve.

Player counts

What is the current population on My Build Server?

A reading taken now finds My Build Server offline; the most recent activity was 14 days 3 hours ago.

How does My Build Server rank against other Rust servers?

Over the last seven days, My Build Server recorded enough player hours to reach #13,136 worldwide, placing it in the top 61% of all ranked servers.

Operator and location

How reliably does My Build Server stay online?

No contact with My Build Server right now, and the last recorded contact was 14 days 3 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 13 October 2026 is when Rust Server Trends first recorded it.

Which region does My Build Server run from?

Nothing about a region comes from My Build Server. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 78.37.179.103:28015.

What build of Rust does My Build Server use?

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

Wipe day

How often does My Build Server wipe, and on which days?

Too few wipes of My Build Server are on record yet to show its rhythm. 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 14 days 3 hours.

Tags

What do the server tags on My Build Server mean?

The game's server browser reads the tags My Build Server publishes: gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): 50 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): It runs 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 Server appear?

You will find My Build Server on the following Rust Server Trends lists: 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.

Connecting

How do you connect to My Build Server?

Enter client.connect 78.37.179.103:28015 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 mp50,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp50
Max players 50 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs167781
Build It runs 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.