Working its way up from the back of the class: #16,733 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
47/ 100
D
Slipped a little: down 902 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing is the one to work on (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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
·······
·······
·······
····
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.
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 24 Sep, 15:43 UTC34d ago
0
–
running
0
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
No region is published for Bitte nicht DDoSn!. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 134.255.216.16:27015.
How dependable is Bitte nicht DDoSn!, and is it online at the moment?
You cannot join now: Bitte nicht DDoSn! is offline, last seen 32 days 15 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 14 September 2026, Rust Server Score saw it for the first time.
Which Rust version is Bitte nicht DDoSn! running?
Rust network protocol 2634 and build 165948 on Linux is what Bitte nicht DDoSn! runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does Bitte nicht DDoSn! wipe, and how often?
There are too few wipes on record for Bitte nicht DDoSn! to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 34 days 21 hours have passed since this world was made.
What should you expect from wipe day on Bitte nicht DDoSn!?
The average peak on its recent wipes was 0 players. The crowd on the latest wipe was largest 0 hours after it began.
Player count
What position does Bitte nicht DDoSn! hold in the rankings?
Over the last seven days, Bitte nicht DDoSn! has #16,733 for player hours, in the top 71% of all ranked servers.
What does the population on Bitte nicht DDoSn! look like?
It has been 32 days 15 hours since Bitte nicht DDoSn! was last seen, and it is offline right now.
Tags and filters
What do Bitte nicht DDoSn!'s tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp24 (Max players): 24 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs165948 (Build): This runs on build 165948; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server are the tags Bitte nicht DDoSn! publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show Bitte nicht DDoSn!?
These Rust Server Score lists count Bitte nicht DDoSn! among them: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
How is Bitte nicht DDoSn! set up, and what rules does it keep?
The name of Bitte nicht DDoSn! gives no gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on Bitte nicht DDoSn!?
A procedural map of size 3,000 and seed 100, generated by the game, is what Bitte nicht DDoSn! runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How do you get onto Bitte nicht DDoSn!?
Enter client.connect 134.255.216.16:27015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://horstblocks.de:443/login_up.php.
Server tags
what each one means
Published asmp24,ptrak,$r?,v2634,gmrust,cs165948,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp24
Max players24 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs165948
BuildThis runs on build 165948.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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. Strongest in momentum (D); standing is the one to work on (F).