Working its way up from the back of the class: #15,563 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
31/ 100
F
Lost ground: down 5,897 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to F.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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 best
RankRank in region
Top 65% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·WW····
·······
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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.
usual gap1 daysbetween real wipes
wipe-day peak2players, last three wipes
The first 48 hours of its last wipes
Wed 30 SepTue 29 Sep
Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 30 Sep, 22:05 UTC27d ago
2
–
running
2
Tue 29 Sep, 21:19 UTC28d ago
2
–
1 days
1
Peak: the most players in the first 48 hours. 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
classmates: the same kind of game, then region, group limit, rate and wipes
You'll find no region listed by BedWars Dev. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 178.68.57.104:28015 is the address to use.
How reliable is BedWars Dev, and is it up?
The server is down: BedWars Dev is offline now, with the last sighting 26 days 21 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 29 September 2026.
What Rust version is BedWars Dev on?
Rust network protocol 2633 and build 162929 on Windows is what BedWars Dev runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does BedWars Dev wipe, and how often?
BedWars Dev has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 26 days 23 hours.
What should you expect from wipe day on BedWars Dev?
Recent wipes have peaked at 2 players on average. Peak numbers came 1 hours into the latest wipe.
Player count
What position does BedWars Dev hold in the rankings?
In the top 65% of all ranked servers, BedWars Dev sits at #15,563 for player hours over the last seven days.
Is BedWars Dev a busy server?
It has been 26 days 21 hours since BedWars Dev was last seen, and it is offline right now.
Lists and filters
What do BedWars Dev's tags stand for?
You'll see BedWars Dev tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): 50 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs162929 (Build): The game build is 162929; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: Carbon in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does BedWars Dev appear in the Rust Server Score lists and filters?
Rust Server Score lists that include BedWars Dev: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Server rules
Which rules does BedWars Dev enforce, and what are its settings?
Nothing in the name of BedWars Dev states a gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. VAC, Valve's anti-cheat, is enabled.
Getting in
What is the way to join BedWars Dev?
Enter client.connect 178.68.57.104:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,gmrust,cs162929,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max players50 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs162929
BuildThe game build is 162929.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonPlugin framework: Carbon.
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.
A term to build on. Even marks across the subjects, from F to F.