Direct Protocol | Loopback Development
Offline 47.194.150.81:28035 checked 16d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 71% 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.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 12 Oct, 14:19 UTC16d ago | 1 | – | 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
the same kind of game, then region, group limit, rate and wipes- 393/400
- 346/350
- 38/250
- 32/250
- 47/100
- 151/200
Quick answers
from the figures on this pageReset cycle
What happens on Direct Protocol | Loopback Development when wipe day comes?
At their busiest, its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.
What wipe timing does Direct Protocol | Loopback Development follow?
The rhythm of Direct Protocol | Loopback Development's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 16 days 20 hours ago the current world was made.
Lists and filters
Which tags does Direct Protocol | Loopback Development carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp4 (Max players): 4 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): Build 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from Direct Protocol | Loopback Development. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does Direct Protocol | Loopback Development appear in Rust Metrics lists and filters?
These Rust Metrics lists carry Direct Protocol | Loopback Development: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
What position does Direct Protocol | Loopback Development hold among Rust servers?
Player hours over seven days put Direct Protocol | Loopback Development at #15,441, in the top 71% of all ranked servers.
What player count does Direct Protocol | Loopback Development carry?
Status for Direct Protocol | Loopback Development: offline. Last seen 16 days 10 hours ago.
Server
Where does Direct Protocol | Loopback Development sit?
Reading: location. Direct Protocol | Loopback Development gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 47.194.150.81:28035.
What Rust version is Direct Protocol | Loopback Development on?
Reading: Direct Protocol | Loopback Development, Rust network protocol 2634 and build 166652, Windows. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on Direct Protocol | Loopback Development, and is it online?
Reading: offline. Direct Protocol | Loopback Development last answered 16 days 10 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 12 October 2026.
Settings and map
How is Direct Protocol | Loopback Development configured, and what rules are in force?
Reading the name gives no gather rate for Direct Protocol | Loopback Development. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. VAC is off. That is Valve's anti-cheat.
What map is Direct Protocol | Loopback Development on?
Procedural map on Direct Protocol | Loopback Development, made by the game's generator.
How to join
How do you connect to Direct Protocol | Loopback Development?
To join: start Rust, press F1 and type client.connect 47.194.150.81:28035. Or press Launch Rust here and Steam opens the game and connects you.