Rust Server TrendsSeismic network · station log
Recording Stations11,713 Players43,388 Active3,068 Wipes · 3 h103 48 h

Station XX-15986 · no signal

Bug Bench

Offline 87.255.27.36:28015 checked 22d ago

Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,986
top 71%
Last wipe
22d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15986 · 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 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
15k10k15k20k6 Oct7 Oct9 Oct10 Oct12 Oct13 Oct

Top 71% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak
0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 6 Oct, 12:21 UTC22d ago M0.0steady 0 – running 0

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
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 565 on average
220/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
129/ 200
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
28/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 289 on average
14/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 274 on average
23/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 251 on average
32/ 225
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Bug Bench?

Bug Bench uses a procedural map, which the game generates.

Which settings and rules apply on Bug Bench?

No gather rate appears in the name of Bug Bench. At the game's default, groups can have up to 8 players. In survival mode, the usual game of 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.

Live population

What is the current population on Bug Bench?

No players are recorded on Bug Bench at this moment; it is offline, and the last sighting was 22 days 6 hours ago.

How does Bug Bench rank against other Rust servers?

On player hours for the past week, Bug Bench sits at #15,986, which puts it inside the top 71% of every ranked server.

Operator and location

How reliably does Bug Bench stay online?

As recorded now, Bug Bench is not reachable, the last contact having been 22 days 6 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 6 October 2026 it was recorded for the first time by Rust Server Trends.

Which region does Bug Bench run from?

Nothing about a region comes from Bug Bench. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 87.255.27.36:28015.

What build of Rust does Bug Bench use?

On Windows, Bug Bench runs Rust network protocol 2634 and build 166652. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on Bug Bench?

The recent wipes averaged a busiest count of 0 players. 0 hours after the latest wipe, the crowd peaked.

On what timetable does Bug Bench run its wipes?

The rhythm of Bug Bench cannot yet be told: too few of its wipes are on record. 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 22 days 12 hours.

Server tags

What do the server tags on Bug Bench mean?

The game's server browser reads the tags Bug Bench publishes: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): Slots: 10; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166652 (Build): Game build: 166652; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set. 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 Bug Bench appear?

The Rust Server Trends lists that take in Bug Bench are: 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.

Connecting

How do you connect to Bug Bench?

To join, enter client.connect 87.255.27.36:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp10
Max players Slots: 10.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs166652
Build Game build: 166652.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$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.