Online NA 104.129.132.227:30015 checked 12m ago
Jitters Test Server
Connect
srv = rust.server("104.129.132.227:30017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 37% of all ranked servers, top 63% in NA. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Wednesday 4 November, 10:20 UTC, in 5d 12h. # Its weekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 5d 12h | Wed 4 Nov, 10:20 UTC | wipe |
| 1 | 6d 20h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 12d 12h | Wed 11 Nov, 10:20 UTC | wipe |
| 3 | 19d 12h | Wed 18 Nov, 10:20 UTC | wipe |
| 4 | 26d 12h | Wed 25 Nov, 10:20 UTC | wipe |
| 5 | 33d 12h | Wed 2 Dec, 10:20 UTC | wipe |
| 6 | 34d 20h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 7 | 40d 12h | Wed 9 Dec, 10:20 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 23 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 14 Oct, 10:20 UTC15d ago | 1 | NaN | running | 0 |
| 1 | Thu 8 Oct, 10:56 UTC21d ago | 1 | halved by day 2 | 6 days | 0 |
| 2 | Wed 30 Sep, 22:46 UTC28d ago | 3 | halved by day 3 | 7.5 days | 0 |
| 3 | Sun 27 Sep, 23:42 UTC31d ago | 2 | held half | 3 days | 1 |
| 4 | Sun 27 Sep, 17:39 UTC32d ago | 2 | NaN | 0.3 days | 1 |
| 5 | Sat 26 Sep, 20:43 UTC33d ago | 2 | NaN | 0.9 days | 0 |
| 6 | Fri 25 Sep, 12:51 UTC34d ago | 4 | NaN | 1.3 days | 0 |
| 7 | Thu 24 Sep, 16:28 UTC35d ago | 4 | NaN | 0.8 days | 0 |
| 8 | Thu 24 Sep, 09:50 UTC35d ago | 4 | NaN | 0.3 days | 1 |
| 9 | Thu 24 Sep, 00:14 UTC35d ago | 4 | NaN | 0.4 days | 2 |
| 10 | Tue 22 Sep, 21:05 UTC37d ago | 3 | NaN | 1.1 days | 0 |
| 11 | Tue 22 Sep, 11:26 UTC37d ago | 3 | NaN | 0.4 days | 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. A new world less than six hours after a wipe is a restart, not a wipe of its own.
display(srv.map, srv.info())Map
3500 · seed 2244
- map
- Procedural Map
- size
- 3500
- seed
- 2244
Server
srv.info()- address
- 104.129.132.227:30015
- region
- NA
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- weekly
- last wipe
- 14 Oct 2026, 10:20 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | RustMode PvE | 10/29 | No Tech Tree | Skills | Raids | Events | NA · groups of 150+ · weekly · 4 on average | 14/50 |
| 1 | [US] Northnet 1x PVE | Events | Raids | No Tech Tree | Custom W | NA · groups of 8+ · 1x · weekly · 2 on average | 6/75 |
| 2 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 253 on average | 250/2000 |
| 3 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 106 on average | 89/200 |
| 4 | [US] RustEZ Scourge PvE | Zombies | No Raiding | No Killing | NA · groups of 8+ · monthly · 48 on average | 41/200 |
| 5 | [US] RustEZ Survival PvE | No Decay | No Raiding | No Killing | NA · groups of 8+ · monthly · 37 on average | 39/200 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Jitters Test Server rank?
Ranked #8,169 on seven-day player hours, Jitters Test Server is #1,175 in North America and in the top 37% of all ranked servers.
How many players does Jitters Test Server hold at once?
Jitters Test Server reports 0 players at this refresh, with 10 slots configured. Over the last seven days it averaged 0 players and peaked at 2.
Server facts
How smoothly does Jitters Test Server run?
Averaged over 48 hours: 60 server fps, never under 58. The entity count peaked at 93,000, covering buildings, deployables and the rest of the world. Memory peaked at 2,624 MB. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is Jitters Test Server on?
Rust network protocol 2635 and build 169621 on Linux is what Jitters Test Server runs. Joining needs the same protocol on your game; Steam handles the update.
Is Jitters Test Server up, and what does its uptime show?
Online is the state at the latest refresh for Jitters Test Server. Count back 14 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. Its earliest recorded date in Rust Data is 13 September 2026.
In which location is Jitters Test Server hosted?
The NA tag is what Jitters Test Server uses to list itself in North America. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 104.129.132.227:30015 is its address.
Settings and map
Which rules apply on Jitters Test Server, and what settings?
No gather rate appears in the name: Jitters Test Server. Eight players per group: that is the game's default, and it applies here. Recorded as pve, no combat between players. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Carbon. Anti-cheat status: VAC on.
What is the map on Jitters Test Server?
The game generates the map on Jitters Test Server: procedural, size 3,500, seed 2244. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
When does Jitters Test Server wipe, and how often?
The tag sets the prediction: Jitters Test Server has too few wipes on record to confirm its schedule. Wednesday 4 November at 10:20 UTC is when the next wipe is due. A new world was started 15 days 11 hours ago, and that is the one in play. A weekly wipe schedule is published in its tags.
On Jitters Test Server, what happens on wipe day?
Recent wipes averaged 2 players at their peak. Peak population on the latest wipe came 23 hours in. Recent wipes kept the crowd above half the peak until the next wipe 33% of the time. The drop under half arrived by day 2.5 in the other cases.
Lists and tags
Which Rust Data filters and lists contain Jitters Test Server?
These Rust Data lists include Jitters Test Server: Modded Rust servers, Rust PvE servers and North America Rust servers. 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.
How should you read the server tags on Jitters Test Server?
Read by the game's server browser, the tags Jitters Test Server publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs169621 (Build): Build number: 169621; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^w (Weekly): A wipe every week; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins; NA (North America): North America is its listing in the server browser. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
How can I connect to Jitters Test Server?
Enter client.connect 104.129.132.227:30015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.