Rust Server Score · Report for the term · marked 30 October 2026 Pupil no. 47.194.150.81:28035

Name of server

Direct Protocol | Loopback Development

RegisterAbsent

Region–

Address47.194.150.81:28035

Last checked17d ago

Launch Rust and join

Overall grade

Not there yet

36 out of 100, the average of 2 subjects

Players now 0/ 4 0% full

7-day average0peak –

Rank#15,441top 71%

Last wipe17d agono schedule published

Next wipe–too few wipes seen yet

Subject	Mark	Teacher's comment
Populationplayers against slots, 7-day average	unmarked	No weekly average to mark yet.
Standingrank on player hours	29/ 100	Working its way up from the back of the class: #15,441 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	42/ 100	Slipped a little: down 2,419 places this week. Nothing a good wipe can't fix.

A term to build on. Strongest in momentum (F); 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 hourly history yet.

Hourly average and peak, UTC.

Server performance

This server has not answered a direct query in the last 48 hours.

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 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

·······

W······

·······

·····

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 peak1players, 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	Peak	Crowd	Lasted	Players before
Mon 12 Oct, 14:19 UTC17d 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

classmates: the same kind of game, then region, group limit, rate and wipes

Rusty Moose |EU Mondays|

EU · groups of 12+ · weekly · 482 on average

47 / 250

Rustoria.co - EU East Long

EU · groups of 12+ · monthly · 321 on average

78 / 200

Rusty Moose |EU Main|

EU · groups of 12+ · weekly · 284 on average

236 / 250

Rustafied.com - EU Friday

EU · groups of 16+ · weekly · 279 on average

9 / 100

Rustoria.co - EU Main

EU · groups of 16+ · weekly · 266 on average

289 / 325

Rustoria.co - EU East Medium

EU · groups of 12+ · biweekly · 257 on average

265 / 275

Quick answers

from the figures on this page

About the server

In what location does Direct Protocol | Loopback Development sit?

No region is published for Direct Protocol | Loopback Development. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 47.194.150.81:28035.

Is Direct Protocol | Loopback Development up, and how steady is its uptime?

The server is down: Direct Protocol | Loopback Development is offline now, with the last sighting 17 days 3 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 12 October 2026, Rust Server Score saw it for the first time.

On what Rust version does Direct Protocol | Loopback Development sit?

You will find Direct Protocol | Loopback Development on Rust network protocol 2634 and build 166652, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.

Wipe cycle

When does Direct Protocol | Loopback Development wipe, and how often?

The record holds too few of Direct Protocol | Loopback Development's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 17 days 12 hours.

What should you expect from wipe day on Direct Protocol | Loopback Development?

Across its recent wipes, the busiest moments averaged 1 players. 0 hours after the latest wipe began, the crowd hit its peak.

Player count

Where does Direct Protocol | Loopback Development place in the wider field of Rust servers?

Over the last seven days, Direct Protocol | Loopback Development has #15,441 for player hours, in the top 71% of all ranked servers.

What does the population on Direct Protocol | Loopback Development look like?

The last sighting of Direct Protocol | Loopback Development was 17 days 3 hours ago, and it is offline right now.

Tags and filters

What is meant by the tags on Direct Protocol | Loopback Development?

gmrust (Game mode): Survival in the standard Rust style; mp4 (Max players): Its slot count is 4; 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; cs166652 (Build): This runs on build 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set are the tags Direct Protocol | Loopback Development 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 Direct Protocol | Loopback Development?

Rust Server Score lists that include Direct Protocol | Loopback Development: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Server rules

What settings and rules apply on Direct Protocol | Loopback Development?

You will find no gather rate in the name of Direct Protocol | Loopback Development. The default of 8 players applies as the group cap. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. The server does not run VAC, Valve's anti-cheat.

Direct Protocol | Loopback Development runs which map?

The game generates a procedural map for Direct Protocol | Loopback Development.

How to join

How should you connect to Direct Protocol | Loopback Development?

Enter client.connect 47.194.150.81:28035 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 as mp4,ptrak,$r?,v2634,gmrust,cs166652,ts8

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.