Skip to the page
Network live 11,784 servers online 66,602 players aboard 198 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

Disclaimer

Online 157.85.91.165:27751 checked 7m ago

Tracking number · connect
Wipe progress · wiped 24d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –too few wipes seen yet
0/ 10 players now 0% full
07-day averagepeak –
#15,318ranktop 69%
24d agolast wipeno schedule published
–next wipetoo few wipes seen yet
Delivery history

Players, performance and rank

Players

AveragePeak
0123413:0022:0007:0015:0001:0010:00

Hourly average and peak, UTC.

Server performance

010020030040013:0022:0007:0015:0001:0010:00

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, measured since 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k3 Oct8 Oct13 Oct19 Oct24 Oct29 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

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.

0.9 daysusual gapbetween real wipes
1wipe-day peakplayers, last three wipes

The first 48 hours of its last wipes

Sun 4 OctSat 3 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes

every wipe as a delivery, newest first
  1. Sun 4 Oct, 19:50 UTC 20:50 UK · 24d ago
    Wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Sat 3 Oct, 21:19 UTC 22:19 UK · 25d ago
    Wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    0.9 days
    Players before
    1

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 parcels

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 514 on average 523 / 525
  2. Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average 385 / 450
  3. Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average 48 / 250
  4. Rustoria.co - EU MainEU · groups of 16+ · weekly · 276 on average 51 / 250
  5. Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average 54 / 100
  6. Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 241 on average 161 / 200
Help desk

Quick answers

From the figures on this page.

Player count

Where does Disclaimer place among Rust servers?

A seven-day player-hours count places Disclaimer at #15,318: the top 69% of every ranked server.

What is the current population on Disclaimer?

Checking now: 0 players on 10 slots at Disclaimer. For the last seven days the average player count was 0.

Map and rules

Which map is active on Disclaimer?

Generated by the game with seed 1901147971, the procedural map on Disclaimer is size 1,500. Size and seed match means the map matches, so you can view it on RustMaps from this page.

What settings and rules should you know for Disclaimer?

No gather rate appears in the name of Disclaimer. 8 players is the group limit, since the game's default applies. It runs survival, the usual game: build, gather, raid. You can raid and fight other players. The server browser files it under Community, as a community server. The VAC anti-cheat from Valve is enabled.

Operator and location

What is the location of Disclaimer?

There is no region published for Disclaimer. The location shown on Rust Wipe Tracker is the one a server gives; where the machine stands is not looked up. 157.85.91.165:27751 is its address.

Does Disclaimer perform well?

The 48-hour average for server fps stands at 236, never dipping below 219. Buildings, deployables and all the rest of the world pushed its entity count as high as 8,534. Memory use peaked at 2,630 MB. What players call lag is the mix of low fps and an entity count that keeps climbing.

How reliable is Disclaimer, and is it currently online?

Disclaimer is up and online at the moment. The uptime it reports puts its last restart at about 27 hours ago. 99% is the uptime for the last 7 full days, up for 167 of 168 hours. The first sighting of it by Rust Wipe Tracker came on 3 October 2026.

What Rust version is Disclaimer using?

The version on Disclaimer is Rust network protocol 2635 and build 168909, running on Linux. Steam keeps your game updated; it has to be on the same protocol to join.

Wipe schedule

What should you expect from wipe day on Disclaimer?

1 players is the average peak across its recent wipes. On the latest wipe, 2 hours passed before the crowd peaked.

On what schedule does Disclaimer reset its map?

To tell its rhythm we would need more of Disclaimer's wipes on record; there are too few yet. The monthly force wipe, when every Rust server starts a new world, falls next on Thursday 5 November at 19:00 UTC. The world it is running was made 24 days 16 hours.

Server tags

On Rust Wipe Tracker, which lists and filters is Disclaimer part of?

You will find Disclaimer on the following Rust Wipe Tracker lists: Aim training servers, live and Rust community servers, unmodded. These are the filters that bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How should you read the tags on Disclaimer?

gmrust (Game mode): Survival in standard Rust; mp10 (Max players): The server has 10 slots; ts8 (Group limit): Team limit: 8, the standard default; v2635 (Protocol): Protocol 2635 is required; a different version can't join; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): A region code isn't set are the tags Disclaimer publishes, and the server browser takes them as read. Players now, the queue and the world's creation time sit at the top of this page and come from the tags as well.

Connecting

What is the process to join Disclaimer?

Enter client.connect 157.85.91.165:27751 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you.

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players The server has 10 slots.
ts8
Group limit Team limit: 8, the standard default.
v2635
Protocol Protocol 2635 is required; a different version can't join.
cs168909
Build It runs game build 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code A region code isn't set.

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.