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

Station XX-15450 · no signal

Bed Placement Validation

Offline 61.228.47.205:28115 checked 9d ago

Connect
Players now
0/ 1
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,450
top 70%
Last wipe
18d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-15450 · 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
15k10k15k20k12 Nov13 Nov15 Nov16 Nov18 Nov19 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
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
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 403 on average
591/ 600
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 295 on average
591/ 600
Rusty Moose |US Monthly| NA · groups of 12+ · monthly · 275 on average
119/ 200
Rustoria.co - EU Long EU · groups of 14+ · monthly · 248 on average
252/ 250
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 233 on average
75/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 232 on average
580/ 600
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Bed Placement Validation?

A procedural map runs on Bed Placement Validation, generated by the game.

Which settings and rules apply on Bed Placement Validation?

No gather rate appears in the name of Bed Placement Validation. Groups hold up to 8 players, which is the default for the game. survival is the game mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Community, as a community server. The server has VAC off, Valve's anti-cheat.

Live population

How many players are recorded on Bed Placement Validation right now?

Bed Placement Validation is not responding at this moment and is offline, last seen 9 days 10 hours ago.

How does Bed Placement Validation rank against other Rust servers?

The last seven days of player hours place Bed Placement Validation at #15,450, in the top 70% of all ranked servers.

Operator and location

How reliably does Bed Placement Validation stay online?

As recorded now, Bed Placement Validation is not reachable, the last contact having been 9 days 10 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 12 November 2026 it was recorded for the first time by Rust Server Trends.

Which region does Bed Placement Validation run from?

Nothing about a region comes from Bed Placement Validation. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 61.228.47.205:28115.

Which Rust version is Bed Placement Validation running?

Rust network protocol 2636 and build 170545 on Windows is what Bed Placement Validation runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

On what timetable does Bed Placement Validation run its wipes?

On record so far are too few of Bed Placement Validation'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. The present world dates from 18 days 22 hours.

Tags

What do the server tags on Bed Placement Validation mean?

The game's server browser reads the tags Bed Placement Validation publishes: gmrust (Game mode): Survival in standard Rust; mp1 (Max players): 1 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2636 (Protocol): To connect, your game must be on the same protocol, 2636; cs170545 (Build): The game build is 170545; 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. 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 Bed Placement Validation appear?

The Rust Server Trends lists that take in Bed Placement Validation 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.

How to join

What steps get you onto Bed Placement Validation?

To join, enter client.connect 61.228.47.205:28115 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 mp1,ptrak,$r?,v2636,gmrust,cs170545,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp1
Max players 1 slots are available.
ts8
Group limit Teams max out at 8, the default set by the game.
v2636
Protocol To connect, your game must be on the same protocol, 2636.
cs170545
Build The game build is 170545.
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.