Station XX-15563 · no signal
BedWars Dev
Offline 178.68.57.104:28015 checked 27d ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,563
- top 65%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 65% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 1 daysbetween real wipes
- wipe-day peak
- 2players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Wed 30 Sep, 22:05 UTC27d ago | M0.0■steady | 2 | – | running | 2 | |
| Tue 29 Sep, 21:19 UTC28d ago | M0.0▲rising | 2 | – | 1 days | 1 |
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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which settings and rules apply on BedWars Dev?
No gather rate appears in the name of BedWars Dev. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Carbon. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on BedWars Dev right now?
BedWars Dev is not responding at this moment and is offline, last seen 27 days 18 hours ago.
How does BedWars Dev rank against other Rust servers?
Over the last seven days, BedWars Dev recorded enough player hours to reach #15,563 worldwide, placing it in the top 65% of all ranked servers.
Server details
How reliably does BedWars Dev stay online?
As recorded now, BedWars Dev is not reachable, the last contact having been 27 days 18 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 29 September 2026.
Which region does BedWars Dev run from?
A region is not published by BedWars Dev. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 178.68.57.104:28015 is the address it uses.
What build of Rust does BedWars Dev use?
Rust network protocol 2633 and build 162929 on Windows is what BedWars Dev runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on BedWars Dev?
The recent wipes averaged a busiest count of 2 players. 1 hours into the latest wipe, the crowd reached its peak.
How often does BedWars Dev wipe, and on which days?
On record so far are too few of BedWars Dev's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 27 days 19 hours is how long the current world has been running.
Tags
What do the server tags on BedWars Dev mean?
These are the tags BedWars Dev publishes for the browser to read: 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; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs162929 (Build): Game build: 162929; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does BedWars Dev appear?
You will find BedWars Dev on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Join the server
What steps get you onto BedWars Dev?
To join, enter client.connect 178.68.57.104: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.
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.