Rust Server Score · Report for the term · marked 29 October 2026 Pupil no. 24.134.191.89:28015

Name of server

:thinking:

RegisterAbsent

Region–

Address24.134.191.89:28015

Last checked6d ago

Launch Rust and join

Overall grade

Not there yet

19 out of 100, the average of 4 subjects

On the class lists: F (25), with population over 48 hours and no performance mark.

Players now 0/ 1 0% full

7-day average0peak –

Rank#15,358top 69%

Last wipe7d agono schedule published

Next wipe–no rhythm it keeps

Subject	Mark	Teacher's comment
Populationplayers against slots, 7-day average	0/ 100	A quiet classroom so far: 0 of 1 on average. Plenty of space to grow.
Standingrank on player hours	31/ 100	Working its way up from the back of the class: #15,358 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	0/ 100	Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago	45/ 100	Slipped a little: down 1,419 places this week. Nothing a good wipe can't fix.

A term to build on. Strongest in momentum (D); population 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 69% of all ranked servers. Ranked on player hours over the last seven days.

Attendance: the wipe record

5 wipe days in the last 16 weeks

·······

··WF···

···W···

W······

··W····

····

W wiped that day F the force wipe · today. From the wipes in the table below.

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap4.3 daysbetween real wipes

on rhythm20%of its recent wipes

wipe-day peak1players, last three wipes

crowd held0%else halves by day 1

The first 48 hours of its last wipes

Wed 21 OctMon 12 OctThu 8 Oct

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes

newest first

Wiped	Peak	Crowd	Lasted
Wed 21 Oct, 19:33 UTC7d ago	1	–	running
Mon 12 Oct, 20:48 UTC16d ago	1	halved by day 1	8.9 days
Thu 8 Oct, 13:40 UTC20d ago	1	–	4.3 days
Thu 1 Oct, 22:40 UTC FW27d ago	0	–	6.6 days
Thu 1 Oct, 06:41 UTC27d ago	0	–	0.7 days
Wed 30 Sep, 22:26 UTC28d ago	0	–	0.3 days

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 · 555 on average

161 / 250

Rustoria.co - EU East Long

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

97 / 200

Rusty Moose |EU Main|

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

15 / 250

Rustoria.co - EU Main

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

16 / 250

Rustafied.com - EU Friday

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

14 / 100

Rustoria.co - EU East Medium

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

17 / 200

Quick answers

from the figures on this page

Server facts

Which region is :thinking: based in?

:thinking: leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 24.134.191.89:28015 is the address to use.

How reliable is :thinking:, and is it up?

The server is down: :thinking: is offline now, with the last sighting 6 days 19 hours ago. For the last 7 full days, it was up 8 of 168 hours, or 5% of the time. On 30 September 2026, Rust Server Score saw it for the first time.

Which Rust version is :thinking: running?

Rust network protocol 2634 and build 167295 on Windows is what :thinking: runs. To join, your game must use the same protocol; Steam handles the update.

Resets

When does :thinking: wipe, and how often?

No next wipe can be predicted for :thinking:, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 7 days 7 hours have passed since this world was made.

What happens on :thinking: when wipe day arrives?

Recent wipes have peaked at 1 players on average. Peak numbers came 0 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. The crowd dropped below half by day 1 in the wipes where it did not hold.

Player numbers

Where does :thinking: place in the wider field of Rust servers?

Over the last seven days, :thinking: has #15,358 for player hours, in the top 69% of all ranked servers.

How many players does :thinking: usually have?

The last sighting of :thinking: was 6 days 19 hours ago, and it is offline right now. For the last seven days, the average number of players was 0.

Tags and filters

What is meant by the tags on :thinking:?

gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): 1 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167295 (Build): Build number: 167295; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server are the tags :thinking: publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.

Which Rust Server Score filters and lists feature :thinking:?

Rust Server Score lists that include :thinking:: 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; Last wipe: In the last 2 weeks.

Map and rules

How is :thinking: set up, and what rules does it keep?

Nothing in the name of :thinking: states a gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in 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 runs Valve's anti-cheat, VAC.

Getting in

How should you connect to :thinking:?

Enter client.connect 24.134.191.89:28015 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 mp1,ptrak,$r?,v2634,gmrust,cs167295,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.