Rust Server TrendsSeismic network · station log
Recording Stations11,706 Players60,014 Active3,275 Wipes · 3 h160 48 h

Station NA-8189 · recording

Jitters Test Server

Online NA 104.129.132.227:30015 checked 25m ago

weekly wipes moddedcarbonpve
Connect
Players now
0/ 10
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 2
Rank
#8,189
top 37% · #1175 in NA
Last wipe
15d ago
weekly schedule
Next wipe
5d 9h
Wed 4 Nov, 10:20 UTC
Seismic record · station NA-8189 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 10 slots
Motion · 24 h
M0.0steady+0 players
Channel 1 · calibrated

Players

AveragePeak
0123401:0010:0020:0005:0014:0023:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

02040608001:0010:0020:0005:0014:0023: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 17 Sep. 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
12.5k5k7.5k10k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 37% of all ranked servers, top 63% in NA. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

from its schedule tag

Next wipe Wednesday 4 November, 10:20 UTC, in 5d 9h. Its weekly schedule tag · low confidence

usual gap
1.1 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
2players, last three wipes
crowd held
33%else halves by day 2.5

Coming wipes

  1. 5d 9hWed 4 Nov, 10:20 UTC
  2. 6d 18hThu 5 Nov, 19:00 UTCFW
  3. 12d 9hWed 11 Nov, 10:20 UTC
  4. 19d 9hWed 18 Nov, 10:20 UTC
  5. 26d 9hWed 25 Nov, 10:20 UTC
  6. 33d 9hWed 2 Dec, 10:20 UTC
  7. 34d 18hThu 3 Dec, 19:00 UTCFW
  8. 40d 9hWed 9 Dec, 10:20 UTC

The first 48 hours of its last wipes

Wed 14 OctThu 8 OctWed 30 Sep
01234+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 14 Oct, 10:20 UTC15d ago M0.0rising 1 – running 0
Thu 8 Oct, 10:56 UTC21d ago M0.0rising 1 halved by day 2 6 days 0
Wed 30 Sep, 22:46 UTC29d ago M0.5rising 3 halved by day 3 7.5 days 0
Sun 27 Sep, 23:42 UTC32d ago M0.0rising 2 held half 3 days 1
Sun 27 Sep, 17:39 UTC32d ago M0.0rising 2 – 0.3 days 1
Sat 26 Sep, 20:43 UTC33d ago M0.3rising 2 – 0.9 days 0
Fri 25 Sep, 12:51 UTC34d ago M0.6rising 4 – 1.3 days 0
Thu 24 Sep, 16:28 UTC35d ago M0.6rising 4 – 0.8 days 0
Thu 24 Sep, 09:50 UTC35d ago M0.5rising 4 – 0.3 days 1
Thu 24 Sep, 00:14 UTC36d ago M0.3rising 4 – 0.4 days 2

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
RustMode PvE | 10/29 | No Tech Tree | Skills | Raids | Events NA · groups of 150+ · weekly · 4 on average
15/ 50
[US] Northnet 1x PVE | Events | Raids | No Tech Tree | Custom W NA · groups of 8+ · 1x · weekly · 2 on average
7/ 75
[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo NA · no group limit · biweekly · 250 on average
294/ 2000
Chrayntopia ♡ ︎PvE | RP | PvP NA · groups of 8+ · biweekly · 104 on average
100/ 200
[US] RustEZ Scourge PvE | Zombies | No Raiding | No Killing NA · groups of 8+ · monthly · 48 on average
55/ 200
Hex US PVE Monthly 1X BiWeekly 5X | RPG | Custom Weapons | Jet NA · no group limit · 1x · monthly · 37 on average
112/ 125
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Jitters Test Server?

Jitters Test Server runs a procedural map of size 3,500 with seed 2244, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on Jitters Test Server?

You will find no gather rate in the name of Jitters Test Server. Groups hold up to 8 players, which is the default for the game. In pve mode, no combat against other players. Plugins or settings alter the game here; the browser lists it as Modded. Carbon is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on Jitters Test Server?

At this moment, Jitters Test Server records 0 players across 10 slots. Across seven days this server recorded an average of 0 players and a peak of 2.

How does Jitters Test Server rank against other Rust servers?

The last seven days of player hours place Jitters Test Server at #8,189, in the top 37% of all ranked servers and #1,175 in North America.

Server details

How reliably does Jitters Test Server stay online?

As recorded now, Jitters Test Server is running. Going by the uptime figure it reports, it restarted about 17 hours ago. Of the 168 hours in the last 7 full days, it was up for 143, or 85% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

How well does Jitters Test Server perform under load?

Its average server fps over the last 48 hours was 60, and it never dropped below 59. Buildings, deployables and all the rest of the world's entities brought it to a high of 93,000. Its highest memory use was 2,545 MB. What you feel as lag is the combination of low fps and a rising entity count.

Which region does Jitters Test Server run from?

The NA tag is how Jitters Test Server lists itself in North America. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 104.129.132.227:30015 is the address it uses.

What build of Rust does Jitters Test Server use?

On Linux, Jitters Test Server runs Rust network protocol 2635 and build 169621. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

What does wipe day look like on Jitters Test Server?

2 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 23 hours after the wipe. The crowd stayed above half that peak until the next wipe in 33% of its recent wipes. It fell under half by day 2.5 in the wipes where it didn't hold.

How often does Jitters Test Server wipe, and on which days?

The prediction follows its tag, because too few of Jitters Test Server's wipes are on record to confirm its schedule. Wednesday 4 November at 10:20 UTC is when its next wipe is due. 15 days 14 hours is how long the current world has been running. Its tags state a weekly wipe schedule.

Tags

What do the server tags on Jitters Test Server mean?

Tags published by Jitters Test Server and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp10 (Max players): The server has 10 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs169621 (Build): Game build: 169621; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^w (Weekly): Wipes happen weekly; ^p (PvE): The danger comes from the world, not from other players; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here; NA (North America): North America is the region it's listed under in the browser. 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 Jitters Test Server appear?

These Rust Server Trends lists include Jitters Test Server: Modded Rust servers, tracked live, Rust PvE servers and North America Rust servers. You will find it under these filters on the server list: Region: North America; Type: Modded; Game mode: PvE; Server tag: Weekly ^w, PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Weekly.

Connecting

How do you connect to Jitters Test Server?

Enter client.connect 104.129.132.227:30015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,^z,^y,^w,NA,^p,gmrust,cs169621,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players The server has 10 slots.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs169621
Build Game build: 169621.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Wipe schedule

^w
Weekly Wipes happen weekly.

Gameplay

^p
PvE The danger comes from the world, not from other players.

Mods and access

^z
Modded Plugins or settings alter the game, so it's listed under Modded.
^y
Carbon Carbon is the plugin framework running here.

Region

NA
North America North America is the region it's listed under in the browser.

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.