Skip to main content

Independent statistics on public Rust serversNot affiliated with Facepunch Studios

Latest count: 43,996 players on 11,654 servers
Rust CensusThe census of every public Rust server, counted and refreshed.

Statistical profileOnline

Jitters Test Server

NA 104.129.132.227:30015 checked 11m ago

weekly wipes moddedcarbonpve
Release date
Next release
In five minutes (03:25 UTC)
Source
Live server queries
Server address
104.129.132.227:30015
First recorded
13 September 2026

Connect to this server

Launch Rust and join

1. Main points

Players now

0/ 10

0% full

7-day average

0

peak 2

Rank

#8,184

top 37% · #1177 in NA

Last wipe

15d ago

weekly schedule

Next wipe

5d 6h

Wed 4 Nov, 10:20 UTC

Main points

  • There were 0 players on it, 0% of its 10 slots.
  • Over the last seven days it averaged 0 players, with a peak of 2.
  • It ranks #8,184 of all ranked servers, the top 37%, and #1177 in NA, on player hours over the last seven days.
  • Its current map went up 15d ago; the next wipe is expected Wednesday 4 November, 10:20 UTC, its weekly schedule tag.

2. Players

Figure 1: Players on Jitters Test Server

Players now and over time, UTC

AveragePeak
0123404:0013:0023:0008:0017:0002:00

Hourly average and peak, UTC.

Source: Live server queries, Rust Census

3. Server performance

Figure 2: Frame rate, entities and memory

From asking the server directly; low fps and a climbing entity count mean lag

02040608004:0013:0023:0008:0017:0002:00

Note

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.

4. Rank

Figure 3: Rank among all servers, daily

1 is best

RankRank in region
12.5k5k7.5k10k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

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

Source: Live server queries, Rust Census

5. Wipe schedule

Patternfrom its schedule tag

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

Usual gap

1.1 days

between real wipes

On rhythm

0%

of its recent wipes

Wipe-day peak

2

players, last three wipes

Crowd held

33%

else halves by day 2.5

Table 1: Coming wipes

Expected from its own rhythm and the force wipe

InDate and timeKind
5d 6hWed 4 Nov, 10:20 UTCOwn schedule
6d 15hThu 5 Nov, 19:00 UTCForce wipe FW
12d 6hWed 11 Nov, 10:20 UTCOwn schedule
19d 6hWed 18 Nov, 10:20 UTCOwn schedule
26d 6hWed 25 Nov, 10:20 UTCOwn schedule
33d 6hWed 2 Dec, 10:20 UTCOwn schedule
34d 15hThu 3 Dec, 19:00 UTCForce wipe FW
40d 6hWed 9 Dec, 10:20 UTCOwn schedule

Figure 4: The first 48 hours of its last wipes

Players each hour, from the hour of the wipe

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.

Source: Live server queries, Rust Census

6. Wipes

Table 2: Wipes, newest first

Every wipe seen on this server

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

Notes

  1. 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.
  2. A new world less than six hours after a wipe is a restart, not a wipe of its own.

Source: Live server queries, Rust Census

7. Map

Figure 5: Map of Jitters Test Server

3500 · seed 2244

Map of Jitters Test Server

Table 3: The world

As the server publishes it

MapProcedural Map
Size3500
Seed2244
Open on RustMaps

8. Server characteristics

Table 4: Characteristics of Jitters Test Server

What the server publishes and what was recorded

Address104.129.132.227:30015
RegionNA
Max players10
Group limit8, the default
Wipe scheduleweekly
Last wipe14 Oct 2026, 10:20 UTC
Hostname–
First seen13 Sep 2026

9. Similar servers

Table 5: Servers like this one

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

ServerCharacteristicsPlayers
RustMode PvE | 10/29 | No Tech Tree | Skills | Raids | EventsNA · groups of 150+ · weekly · 4 on average11 / 50
[US] Northnet 1x PVE | Events | Raids | No Tech Tree | Custom WNA · groups of 8+ · 1x · weekly · 2 on average8 / 75
[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 245 on average264 / 2000
Chrayntopia ♡ ︎PvE | RP | PvPNA · groups of 8+ · biweekly · 102 on average92 / 200
[US] RustEZ Scourge PvE | Zombies | No Raiding | No KillingNA · groups of 8+ · monthly · 48 on average52 / 200
Hex US PVE Monthly 1X BiWeekly 5X | RPG | Custom Weapons | JetNA · no group limit · 1x · monthly · 38 on average80 / 100

10. Quick answers

From the figures on this page.

Wipe records

This release records the wipe timetable for Jitters Test Server: what is it?

The prediction for Jitters Test Server follows its tag, since too few of its wipes are on record to confirm the schedule. On Wednesday 4 November at 10:20 UTC the next wipe is expected. 15 days 17 hours have passed since this world was made. The tags list a wipe schedule of one week.

How is wipe day run on Jitters Test Server?

Recent wipes drew an average peak of 2 players. On the latest wipe, 23 hours passed before the crowd peaked. Half that peak was held until the next wipe in 33% of its recent wipes. The fall below half came by day 2.5 in those cases where it did not hold.

Server details

What does the record show for the uptime and current status of Jitters Test Server?

This release records Jitters Test Server as online. About 20 hours ago is when it last restarted, according to the uptime it reports. A total of 167 of 168 hours were up over 7 full days, which is 99% of the time. The first sighting of it by Rust Census was on 13 September 2026.

Does Jitters Test Server hold a steady frame rate and connection?

The figures for the last 48 hours give an average of 60 server fps and a minimum of 59. The world carried up to 93,000 entities, including buildings, deployables and all else. Memory use reached 2,545 MB at its peak. Players feel low fps and a rising entity count as lag.

Which location does Jitters Test Server run from?

In North America Jitters Test Server lists itself, with its NA tag. Rust Census does not look up where the machine stands; it shows where a server says it is. 104.129.132.227:30015 is its address.

On which Rust version does Jitters Test Server operate?

This release lists Jitters Test Server on Rust network protocol 2635 and build 169621, running on Linux. The same protocol is required for your game to join, and Steam updates it for you.

Player counts

What population has been recorded on Jitters Test Server?

The present count is 0 players on Jitters Test Server, out of 10 slots. Averaged over seven days: 0 players, with a peak of 2.

How does Jitters Test Server compare with other servers in the rankings?

This release ranks Jitters Test Server at #8,184 for seven-day player hours, #1,177 in North America, inside the top 37% of ranked servers.

Tags, lists

Where does Jitters Test Server appear among the Rust Census lists and filters?

Included in these Rust Census lists is Jitters Test Server: Modded Rust servers, counted, Rust PvE servers, listed and North America: servers listed. It appears 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.

What is meant by each tag shown on Jitters Test Server?

Read by the game's server browser, Jitters Test Server publishes these tags: gmrust (Game mode): The game mode is standard survival as Rust runs it; mp10 (Max players): Slots: 10; ts8 (Group limit): Teams are capped at 8, the default the game ships with; v2635 (Protocol): To connect, your game version must match protocol 2635; cs169621 (Build): Game build: 169621; ptrak (Networking): RakNet is used, the standard network layer of the game; $r? (Region code): A region code has not been set; ^w (Weekly): Wipes are run every week; ^p (PvE): There is no player combat here; the danger comes from the world; ^z (Modded): Modded: the game is changed by plugins or settings; ^y (Carbon): Carbon, a plugin framework, is installed; NA (North America): North America is the region under which the browser lists it. The tags also hold the current player count, the queue and the world's creation time, which appear at the top of this page.

Map and rules

What map is listed for Jitters Test Server?

Size 3,500 and seed 2244: that is the procedural map on Jitters Test Server, generated by the game. The same size and seed produce the same map; RustMaps shows it from this page.

On Jitters Test Server, what rules and settings are in force?

The name of Jitters Test Server carries no gather rate. The group cap stands at 8 players, the default for the game. It runs pve, no fighting other players. Plugins or settings change the game, and the browser lists it under Modded. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.

Connecting

What steps are needed to join Jitters Test Server?

Enter client.connect 104.129.132.227:30015 in the console, opened with F1 after starting Rust; alternatively, Launch Rust on this page opens Rust through Steam and connects you.

11. Server tags

What each tag this server publishes means: a glossary.

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

Game

gmrustGame mode The game mode is standard survival as Rust runs it.
mp10Max players Slots: 10.
ts8Group limit Teams are capped at 8, the default the game ships with.
v2635Protocol To connect, your game version must match protocol 2635.
cs169621Build Game build: 169621.
ptrakNetworking RakNet is used, the standard network layer of the game.
$r?Region code A region code has not been set.

Wipe schedule

^wWeekly Wipes are run every week.

Gameplay

^pPvE There is no player combat here; the danger comes from the world.

Mods and access

^zModded Modded: the game is changed by plugins or settings.
^yCarbon Carbon, a plugin framework, is installed.

Region

NANorth America North America is the region under which the browser lists it.

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.