Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO X SRV11,658online PAX44,769playing OCC3,058with players WIPED 3H104
MODModded traffic
Callsign

TST15414=

testing

Online NA 157.85.86.76:21595 checked 10m ago

duo weekly wipes moddedcarbon
Clearance · join
Players now 0/ 20 0% full
7-day average0peak –
Rank#15,414top 69% · #1546 in NA
Last wipe3d agoweekly schedule
Next wipe3d 14hSat 31 Oct, 16:01 UTC
Track history

Players

AveragePeak
0123402:0011:0020:0006:0015:0000:00

Hourly average and peak, UTC.

Server performance

010020030040002:0011:0020:0006:0015:0000: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 16 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k16 Oct18 Oct21 Oct23 Oct26 Oct28 Oct

Top 69% of all ranked servers, top 82% in NA, and #381 of the duo servers (top 90%). Ranked on player hours over the last seven days.

Flight plan

Wipe schedule

from its schedule tag
ETD · next wipe

Next wipe Saturday 31 October, 16:01 UTC, in 3d 14h.

Its weekly schedule tag · low confidence

usual gap4.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

Coming wipes

  1. 3d 14hSat 31 Oct, 16:01 UTC
  2. 8d 17hThu 5 Nov, 19:00 UTCFW
  3. 10d 14hSat 7 Nov, 16:01 UTC
  4. 17d 14hSat 14 Nov, 16:01 UTC
  5. 24d 14hSat 21 Nov, 16:01 UTC
  6. 31d 14hSat 28 Nov, 16:01 UTC
  7. 36d 17hThu 3 Dec, 19:00 UTCFW
  8. 38d 14hSat 5 Dec, 16:01 UTC

The first 48 hours of its last wipes

Sat 24 OctSat 17 OctFri 16 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 24 Oct, 16:01 UTC3d ago 0 – running 0
Sat 17 Oct, 15:10 UTC10d ago 1 halved by day 1 7 days 1
Fri 16 Oct, 10:42 UTC11d ago 1 – 1.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.

Nearby traffic

Similar servers

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

  1. 01COM
    Callsign RST015NA · duo · weekly · 100 on average RustForNoobs.com | Solo/Duo | Weekly | US
    Players 40/100
  2. 02COM
    Callsign RST020NA · duo · weekly · 60 on average RustForNoobs.com | Mondays | Solo/Duo | US
    Players 264/275
  3. 03COM
    Callsign RST020NA · duo · weekly · 3 on average US RustLife.net | Solo/Duo | Fridays | Noob Friendly
    Players 3/100
  4. 04COM
    Callsign WRB015NA · duo · weekly · 3 on average WARBANDITS.GG |Solo/Duo|Weekly| JUST WIPED
    Players 4/100
  5. 05COM
    Callsign RST020NA · duo · weekly · 2 on average US RustLife.net | Solo/Duo | Mondays | Noob Friendly
    Players 5/100
  6. 06MOD
    Callsign WRB015NA · duo · 2x · weekly · 147 on average WARBANDITS.GG 2X |Solo/Duo|X2 JUST FULLWIPED
    Players 45/200
ATIS · this server

Quick answers

From the figures on this page.

Tags

Which Rust Tracker filters and lists carry testing?

Duo servers: group limit 2, Modded servers, tracked live and North America: live server tracking — the Rust Tracker lists that include testing. It comes up under these filters on the server list: Region: North America; Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: Duo; Wipe schedule: Weekly; Last wipe: In the last week.

What do the tags mean that testing is listed under?

These tags are published by testing for the game's server browser to read: gmvanilla (Game mode): Game mode: vanilla survival; mp20 (Max players): Slots: 20; ts2 (Group limit): Teams are capped at 2; v2635 (Protocol): Your game must be on protocol 2635 to connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): The region code is unset; ^w (Weekly): Every week it wipes; ^z (Modded): Plugins or settings alter the game, so it is listed under Modded; ^y (Carbon): Plugin framework: Carbon; NA (North America): The server browser lists it under North America. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.

Wipe Times

What happens on testing on wipe day?

At their busiest, recent wipes averaged 1 players. The peak on the latest wipe came 0 hours after it. Half the peak was held until the next wipe in 0% of its recent wipes. By day 1 the crowd dropped below half where it did not hold.

On what schedule does testing wipe?

The schedule of testing cannot be confirmed, with too few wipes on record: the prediction follows its tag. Due on Saturday 31 October at 16:01 UTC: its next wipe. This world has been running 3 days 9 hours. Tags list a weekly wipe schedule.

Location and Status

How reliable is testing, and is it online now?

testing is up and online at this moment. By its own uptime figure, the last restart was roughly 37 hours ago. 168 of 168 hours up over the last 7 full days: 100% uptime. Rust Tracker logged it first on 16 October 2026.

What Rust version is testing on?

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

What is performance like on testing?

Average server fps over the last 48 hours: 238, with a low of 223. Buildings, deployables and the rest of the world took it to a maximum of 7,087 entities. Memory peaked at 2,983 MB. Players feel lag when fps drops and the entity count climbs.

Which location is testing in?

Listed in North America under NA: that is testing by its own tags. Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 157.85.86.76:21595.

Population

What is the player count on testing?

Slots 20; players on board 0: that is testing now. Across the past seven days, 0 players on average.

What rank does testing carry among Rust servers?

Seven-day player hours: #15,414 overall for testing, top 69% of ranked servers, #1,546 in North America. Position #381 among duo servers.

Map and Rules

Which settings and rules are confirmed on testing?

Nothing in testing's name states a gather rate. A limit of 2 players applies per group (duo). It runs survival, gather, build and raid: the standard game. Raiding and PvP are permitted between players. Plugins or settings change the game, and the server browser lists it under Modded. Plugins on it: Carbon. VAC is on, Valve's anti-cheat.

Which map is confirmed for testing?

A procedural map of size 1,000 runs on testing, generated by the game from seed 50000. Look at it on RustMaps from this page: equal size and seed return the same map. Its map goes by the name Custom Map.

How to Join

What is the way to join testing?

Open the console in Rust with F1 after starting the game, then type client.connect 157.85.86.76:21595. Alternatively, Launch Rust here opens Rust via Steam and connects you. For the website, go to https://discord.com/invite/BGKzykfwEC.

Transponder codes

Server tags

What each one means.

Published as mp20,ptrak,$r?,v2635,^z,^y,^w,NA,gmvanilla,cs168909,ts2

Game

gmvanilla
Game mode Game mode: vanilla survival.
mp20
Max players Slots: 20.
ts2
Group limit Teams are capped at 2.
v2635
Protocol Your game must be on protocol 2635 to connect.
cs168909
Build This server runs game build 168909.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code The region code is unset.

Wipe schedule

^w
Weekly Every week it wipes.

Mods and access

^z
Modded Plugins or settings alter the game, so it is listed under Modded.
^y
Carbon Plugin framework: Carbon.

Region

NA
North America The server browser lists it under North America.

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.