Offline 47.194.150.81:28035 checked 16d ago
Direct Protocol | Loopback Development
Connect
srv = rust.server("47.194.150.81:28037")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not 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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 12 Oct, 14:19 UTC16d ago | 1 | NaN | 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 47.194.150.81:28035
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 12 Oct 2026, 14:19 UTC
- hostname
- –
- first seen
- 12 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 531 on average | 258/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 200/225 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 18/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 280 on average | 23/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 22/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 248 on average | 94/200 |
Quick answers
From the figures on this page.
Population data
What position does Direct Protocol | Loopback Development take in the server rankings?
Rank #15,441 on seven-day player hours for Direct Protocol | Loopback Development, within the top 71% of all ranked servers.
How full does Direct Protocol | Loopback Development run?
The current row shows Direct Protocol | Loopback Development offline; the last response was 16 days 7 hours ago.
Server facts
What is the Rust version on Direct Protocol | Loopback Development?
The build is Rust network protocol 2634 and build 166652 on Windows, run by Direct Protocol | Loopback Development. The protocol has to match before you can join, and Steam does the updating.
How reliable is Direct Protocol | Loopback Development, and is it up?
Direct Protocol | Loopback Development is offline at this refresh; the last response came 16 days 7 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 12 October 2026.
Which location does Direct Protocol | Loopback Development run from?
For Direct Protocol | Loopback Development, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 47.194.150.81:28035.
Map and rules
Which rules apply on Direct Protocol | Loopback Development, and what settings?
No gather rate appears in the name: Direct Protocol | Loopback Development. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is not running; Valve's anti-cheat is off.
Which map has Direct Protocol | Loopback Development loaded?
A procedural map runs on Direct Protocol | Loopback Development, generated by the game.
Wipe schedule
On what schedule does Direct Protocol | Loopback Development wipe?
A rhythm cannot be read from the wipes of Direct Protocol | Loopback Development on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 16 days 17 hours ago, and that is the one in play.
On Direct Protocol | Loopback Development, what happens on wipe day?
Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which Rust Data filters and lists contain Direct Protocol | Loopback Development?
On Rust Data, Direct Protocol | Loopback Development appears in these lists: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on Direct Protocol | Loopback Development hold?
These tags are published by Direct Protocol | Loopback Development and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp4 (Max players): The server lists 4 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Build number: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to Direct Protocol | Loopback Development?
In Rust, F1 opens the console: type client.connect 47.194.150.81:28035. Launch Rust on this page does the same by opening the game through Steam and connecting.