Station XX-15441 · no signal
Direct Protocol | Loopback Development
Offline 47.194.150.81:28035 checked 16d ago
- Players now
- 0/ 4
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,441
- top 71%
- Last wipe
- 16d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 4 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 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.
- wipe-day peak
- 1players, last three wipes
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 12 Oct, 14:19 UTC16d ago | M0.0▲rising | 1 | – | running | 0 |
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 pageServer rules
Which map is running on Direct Protocol | Loopback Development?
A procedural map runs on Direct Protocol | Loopback Development, generated by the game.
Which settings and rules apply on Direct Protocol | Loopback Development?
No gather rate appears in the name of Direct Protocol | Loopback Development. At the game's default, groups can have up to 8 players. In survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser, it runs as a community server. Anti-cheat is off: VAC, from Valve.
Live population
What is the current population on Direct Protocol | Loopback Development?
No players are recorded on Direct Protocol | Loopback Development at this moment; it is offline, and the last sighting was 16 days 8 hours ago.
How does Direct Protocol | Loopback Development rank against other Rust servers?
On player hours for the past week, Direct Protocol | Loopback Development sits at #15,441, which puts it inside the top 71% of every ranked server.
Server details
How reliably does Direct Protocol | Loopback Development stay online?
As recorded now, Direct Protocol | Loopback Development is not reachable, the last contact having been 16 days 8 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 12 October 2026.
Which region does Direct Protocol | Loopback Development run from?
Nothing about a region comes from Direct Protocol | Loopback Development. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 47.194.150.81:28035.
What build of Rust does Direct Protocol | Loopback Development use?
Rust network protocol 2634 and build 166652 on Windows is what Direct Protocol | Loopback Development 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 Direct Protocol | Loopback Development?
The recent wipes averaged a busiest count of 1 players. 0 hours after the latest wipe, the crowd peaked.
On what timetable does Direct Protocol | Loopback Development run its wipes?
The rhythm of Direct Protocol | Loopback Development cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 16 days 18 hours.
Lists and tags
What do the server tags on Direct Protocol | Loopback Development mean?
Tags published by Direct Protocol | Loopback Development and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp4 (Max players): The server has 4 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166652 (Build): It runs game build 166652; 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. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Direct Protocol | Loopback Development appear?
These Rust Server Trends lists include Direct Protocol | Loopback Development: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How to join
How do you connect to Direct Protocol | Loopback Development?
Enter client.connect 47.194.150.81:28035 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects 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.