Rust Server TrendsSeismic network · station log
Recording Stations11,743 Players57,957 Active3,448 Wipes · 3 h134 48 h

Station XX-14442 · no signal

huski1

Offline 125.65.90.209:28015 checked 17d ago

biweekly wipes pve
Connect
Players now
1/ 5
20% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,442
top 65%
Last wipe
17d ago
biweekly schedule
Next wipe
8d 19h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station XX-14442 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of 5 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k10 Oct11 Oct13 Oct14 Oct16 Oct17 Oct

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

Expected events

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 8d 19h. The force wipe

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
[EU/GER] Rust Norddeutschland PVE EU · groups of 8+ · biweekly · 18 on average
8/ 100
|US|BunnysBoomBoomRoom|PvE| NA · groups of 8+ · biweekly · 7 on average
11/ 50
[EU/GER] Der Aussenposten PvE | Vanilla | Beginners Welcome EU · groups of 8+ · biweekly · 4 on average
1/ 75
【流星】PVE|仿官原倍|休闲养老|萌新天堂 EA · groups of 18+ · biweekly · 2 on average
1/ 100
Rumble Bees PvE | Quests | Prestige | MORE groups of 8+ · biweekly · 2 on average
0/ 100
[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo NA · no group limit · biweekly · 244 on average
312/ 2000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on huski1?

huski1 uses a procedural map, which the game generates.

Which settings and rules apply on huski1?

You will find no gather rate in the name of huski1. At the game's default, groups can have up to 8 players. pve is the game mode, no player-versus-player fighting. Under Community in the server browser, it runs as a community server. VAC, Valve's anti-cheat, is switched off.

Population

How many players are recorded on huski1 right now?

No players are recorded on huski1 at this moment; it is offline, and the last sighting was 17 days 13 hours ago.

How does huski1 rank against other Rust servers?

On player hours for the past week, huski1 sits at #14,442, which puts it inside the top 65% of every ranked server.

Operator and location

How reliably does huski1 stay online?

As recorded now, huski1 is not reachable, the last contact having been 17 days 13 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 10 October 2026.

Where in the world is huski1 hosted?

No region is published by huski1. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 125.65.90.209:28015 is the address it uses.

What build of Rust does huski1 use?

huski1 is running Rust network protocol 2634 and build 167398 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

On what timetable does huski1 run its wipes?

From the force wipe the next wipe of huski1 is estimated. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. 17 days 17 hours is how long the current world has been running. Its tags state that it wipes every two weeks.

Lists and tags

What do the server tags on huski1 mean?

These are the tags huski1 publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp5 (Max players): 5 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167398 (Build): Game build: 167398; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^b (Biweekly): A wipe comes every second week; ^p (PvE): You won't fight other players here; the world is what threatens you. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does huski1 appear?

These Rust Server Trends lists include huski1: Rust community servers without the side modes and Rust PvE servers. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: Biweekly ^b and PvE ^p; Group limit: 5 or more; Wipe schedule: Every two weeks.

Join the server

How do you connect to huski1?

To join, enter client.connect 125.65.90.209:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,^b,^p,gmrust,cs167398,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp5
Max players 5 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs167398
Build Game build: 167398.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Wipe schedule

^b
Biweekly A wipe comes every second week.

Gameplay

^p
PvE You won't fight other players here; the world is what threatens you.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.