Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO N SRV11,701online PAX54,561playing OCC3,263with players WIPED 3H144
MODModded traffic
Callsign

RST9846=

RustServer_22027

Online 160.251.136.57:28015 checked 10m ago

moddedoxide
Clearance · join
Players now 0/ 70 0% full
7-day average0peak 1
Rank#9,846top 44%
Last wipe19h agono schedule published
Next wipe–no rhythm it keeps
Track history

Players

AveragePeakWipe
00.250.50.75116:0005:0011:0019:0001:0008:00Wiped Tue 27 Oct, 16:31 UTCWIPEWiped Tue 27 Oct, 22:56 UTCWIPEWiped Wed 28 Oct, 14:42 UTCWIPE

Hourly average and peak, UTC.

Server performance

Server fpsWipe
010020030040016:0005:0011:0019:0001:0008:00Wiped Tue 27 Oct, 16:31 UTCWIPEWiped Tue 27 Oct, 22:56 UTCWIPEWiped Wed 28 Oct, 14:42 UTCWIPE

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

Rank

daily · 1 is best
RankRank in region
15k10k15k20k5 Oct10 Oct14 Oct19 Oct23 Oct29 Oct

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

Flight plan

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 gap1.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 2.5

The first 48 hours of its last wipes

Wed 14 OctTue 13 OctThu 8 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, 1 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 28 Oct, 14:42 UTC19h ago – – running 0
Tue 27 Oct, 22:56 UTC1d ago – – – 0
Tue 27 Oct, 16:31 UTC1d ago – – – 0
Wed 14 Oct, 14:25 UTC14d ago 1 halved by day 4 13.1 days 0
Tue 13 Oct, 17:15 UTC15d ago 1 – 0.9 days 0
Thu 8 Oct, 00:37 UTC21d ago 1 halved by day 1 5.7 days 0
Tue 6 Oct, 04:18 UTC23d ago 1 – 1.8 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.

Nearby traffic

Similar servers

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

  1. 01MOD
    Callsign SHC102no group limit · 149 on average ShockRust | Blue | NoLimit
    Players 130/500
  2. 02MOD
    Callsign STR581EU · groups of 8+ · weekly · 128 on average МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
    Players 122/100
  3. 03MOD
    Callsign RTR811EU · groups of 16+ · weekly · 118 on average RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
    Players 192/225
  4. 04MOD
    Callsign RUS021EU · groups of 16+ · monthly · 93 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
    Players 73/700
  5. 05MOD
    Callsign RST016EU · groups of 12+ · weekly · 88 on average RustSpain.com | EU Main
    Players 10/200
  6. 06MOD
    Callsign RUS021EU · groups of 16+ · monthly · 84 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10
    Players 17/1000
ATIS · this server

Quick answers

From the figures on this page.

Tags

Which Rust Tracker filters and lists carry RustServer_22027?

On Rust Tracker, RustServer_22027 sits in these lists: Modded servers, tracked live. These filters surface it on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.

What do the tags mean that RustServer_22027 is listed under?

These tags are published by RustServer_22027 for the game's server browser to read: gmrust (Game mode): Standard survival mode for Rust; mp70 (Max players): Capacity: 70 slots; ts8 (Group limit): Team limit is 8, the game default; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): The region code is unset; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is listed under Modded. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.

Wipe Times

What should you expect on RustServer_22027 when wipe day lands?

Recent wipes averaged a peak of 1 players. 1 hours after the latest wipe, the crowd peaked. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. By day 2.5 the crowd dropped below half where it did not hold.

When does RustServer_22027 wipe?

Irregular wipe times at RustServer_22027: there is no next wipe to predict. Next monthly force wipe: Thursday 5 November at 19:00 UTC. Every Rust server goes with it. 19 hours since this world was made.

Server Details

How reliable is RustServer_22027, and is it online now?

Tracking shows RustServer_22027 online as of now. The uptime it reports puts the last restart about 17 hours ago. Uptime stood at 15% for the last 7 full days, 25 of 168 hours online. The first sighting by Rust Tracker was 5 October 2026.

Which Rust build is RustServer_22027 running?

Rust network protocol 2635 and build 168909 on Linux is what RustServer_22027 runs. To join, your game must be on the same protocol; Steam handles the update.

How smoothly does RustServer_22027 run?

For the last 48 hours it averaged 140 server fps; the floor was 60. Peak entity count: 123,278, covering buildings, deployables and all else in the world. Memory peaked at 3,930 MB. Players feel lag when fps drops and the entity count climbs.

Where does RustServer_22027 sit?

Region: none published by RustServer_22027. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. Connect on 160.251.136.57:28015.

Population

What is the player count on RustServer_22027?

Slots 70; players on board 0: that is RustServer_22027 now. Peak of 1 in the last seven days, average 0 players. Peak traffic in the last 48 hours came at 15:00 UTC, averaging 1 players.

Where does RustServer_22027 sit in the server rankings?

On player hours over seven days, RustServer_22027 ranks #9,846, inside the top 44% of all ranked servers.

Map and Rules

Which settings and rules are confirmed on RustServer_22027?

The name of RustServer_22027 carries no gather rate. Up to 8 players per group, the game's default. survival is the game mode, gather, build, raid, as the game intends. Raiding and PvP are permitted between players. Plugins or settings change the game, and the server browser lists it under Modded. Oxide plugins run on it. VAC is on, Valve's anti-cheat.

Which map is confirmed for RustServer_22027?

Generated by the game from seed 1337, the procedural map on RustServer_22027 measures 4,500. Look at it on RustMaps from this page: equal size and seed return the same map. Its map goes by the name Custom Map.

Connect

What is the way to join RustServer_22027?

To connect: start Rust, press F1, enter client.connect 160.251.136.57:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join.

Transponder codes

Server tags

What each one means.

Published as mp70,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Standard survival mode for Rust.
mp70
Max players Capacity: 70 slots.
ts8
Group limit Team limit is 8, the game default.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking RakNet is the network layer — the game's standard.
$r?
Region code The region code is unset.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it is listed under Modded.

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.