Rust Data

rustdata.spaceservers167.160.89.85:28017.ipynb

Run all rust-data · live

‹ All servers

Online 167.160.89.85:28015 checked 6m ago

[US|EU] Public Solo/Duo Server

Connect

srv = rust.server("167.160.89.85:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,404 # top 69%
last wipe 15d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123423:0008:0017:0002:0011:0020:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020023:0008:0017:0002:0011:0020: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 8 Oct. 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 best
RankRank in region
15k10k15k20k8 Oct12 Oct16 Oct19 Oct23 Oct27 Oct

Top 69% 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.

usual gap3.2 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Mon 12 OctThu 8 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 12 Oct, 00:19 UTC15d ago 2 NaN running 1
1 Thu 8 Oct, 20:30 UTC19d ago 3 halved by day 1 3.2 days 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

2800 · seed 346781
Map of [US|EU] Public Solo/Duo Server
map
Procedural Map
size
2800
seed
346781
Open on RustMaps

Server

srv.info()
address
167.160.89.85:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
12 Oct 2026, 00:19 UTC
hostname
–
first seen
8 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |US Main|NA · groups of 12+ · weekly · 249 on average35/250
1Rustoria.co - US MainNA · groups of 16+ · weekly · 232 on average54/250
2Rusty Moose |US Mondays|NA · groups of 12+ · weekly · 183 on average629/675
3Rustafied.com - US FridayNA · groups of 16+ · weekly · 154 on average21/100
4Rustoria.co - US MondaysNA · groups of 12+ · weekly · 144 on average557/575
5Rustopia.gg - US Main PremiumNA · groups of 16+ · weekly · 140 on average55/200

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does [US|EU] Public Solo/Duo Server rank?

Rank #15,404 on seven-day player hours for [US|EU] Public Solo/Duo Server, within the top 69% of all ranked servers.

What population does [US|EU] Public Solo/Duo Server carry?

The sample now reads 0 players for [US|EU] Public Solo/Duo Server, out of 50 slots. Over the last seven days it averaged 0 players.

Server facts

What does performance look like on [US|EU] Public Solo/Duo Server?

The 48-hour average is 112 server fps, with a low of 96. Buildings, deployables and all else in the world took the count as high as 40,926 entities. The memory field tops out at 2,915 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What is the Rust version on [US|EU] Public Solo/Duo Server?

Version Rust network protocol 2634 and build 167398 on Windows is reported by [US|EU] Public Solo/Duo Server. The protocol has to match before you can join, and Steam does the updating.

Is [US|EU] Public Solo/Duo Server up, and what does its uptime show?

[US|EU] Public Solo/Duo Server reports itself online at the current refresh. A restart about 15 days 19 hours ago is what its reported uptime implies. 168 of 168 hours up over the last 7 full days, or 100%. The first row Rust Data holds for it is dated 8 October 2026.

In which location is [US|EU] Public Solo/Duo Server hosted?

The name of [US|EU] Public Solo/Duo Server points to North America, even though no region tag 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 167.160.89.85:28015.

Settings and map

Which rules apply on [US|EU] Public Solo/Duo Server, and what settings?

No gather rate appears in the name: [US|EU] Public Solo/Duo Server. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. VAC, Valve's anti-cheat, is enabled.

Which map has [US|EU] Public Solo/Duo Server loaded?

Size 2,800, seed 346781: the procedural map on [US|EU] Public Solo/Duo Server, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipes and dates

When does [US|EU] Public Solo/Duo Server wipe, and how often?

The record for [US|EU] Public Solo/Duo Server holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 15 days 21 hours ago.

On [US|EU] Public Solo/Duo Server, what happens on wipe day?

Across recent wipes the busiest point averaged 2 players. The crowd on the latest wipe topped out 1 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 1.

Lists and tags

Which Rust Data filters and lists contain [US|EU] Public Solo/Duo Server?

These Rust Data lists include [US|EU] Public Solo/Duo Server: Rust community servers, unfiltered and North America Rust servers. It appears under these filters on the server list: Region: North America; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How should you read the server tags on [US|EU] Public Solo/Duo Server?

Read by the game's server browser, the tags [US|EU] Public Solo/Duo Server publishes are: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): Build number: 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

What is the way to join [US|EU] Public Solo/Duo Server?

In Rust, F1 opens the console: type client.connect 167.160.89.85:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp50,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players 50 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167398
Build Build number: 167398.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not 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.

Rust Data 69,659 players 11,803 servers online