Jitters Test Server
Online NA 104.129.132.227:30015 checked 13m ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server performance
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.
Li4Rank
daily · 1 is bestTop 37% of all ranked servers, top 63% in NA. Ranked on player hours over the last seven days.
Bx1Wipe schedule
from its schedule tagNext wipe Wednesday 4 November, 10:20 UTC, in 5d 19h. Its weekly schedule tag · low confidence
Coming wipes
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.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players 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 UTC28d ago | 3° | halved by day 3 | 7.5 days | 0 |
| Sun 27 Sep, 23:42 UTC31d ago | 2° | held half | 3 days | 1 |
| Sun 27 Sep, 17:39 UTC31d ago | 2° | – | 0.3 days | 1 |
| Sat 26 Sep, 20:43 UTC32d ago | 2° | – | 0.9 days | 0 |
| Fri 25 Sep, 12:51 UTC34d ago | 4° | – | 1.3 days | 0 |
| Thu 24 Sep, 16:28 UTC34d ago | 4° | – | 0.8 days | 0 |
| Thu 24 Sep, 09:50 UTC35d ago | 4° | – | 0.3 days | 1 |
| Thu 24 Sep, 00:14 UTC35d ago | 4° | – | 0.4 days | 2 |
| Tue 22 Sep, 21:05 UTC36d ago | 3° | – | 1.1 days | 0 |
| Tue 22 Sep, 11:26 UTC37d ago | 3° | – | 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What does wipe day look like on Jitters Test Server?
Its recent wipes drew an average peak of 2 players. 23 hours after the latest wipe, the crowd peaked. Above half the peak until the next wipe: that held in 33% of its recent wipes. In the wipes that did not hold, numbers dropped below half by day 2.5.
What is the wipe schedule on Jitters Test Server?
Too few wipes are recorded on Jitters Test Server to confirm its schedule; the tag is what the prediction follows. Due on Wednesday 4 November at 10:20 UTC: the next wipe. The world in play now was made 15 days 4 hours ago. Its tags carry a weekly wipe schedule.
Population
How busy is Jitters Test Server?
Of 10 slots on Jitters Test Server, 0 are in use right now. Averaged over the past week: 0 players, peaking at 2.
How does Jitters Test Server rank against other Rust servers?
Top 37% of ranked servers and #1,176 in North America: that is Jitters Test Server at #8,151 for player hours over seven days.
Map and rules
Which map does Jitters Test Server run?
The map on Jitters Test Server is procedural, size 3,500 with seed 2244, generated by the game. From this page you can view the map on RustMaps, since the same size and seed give the same map.
What are the rules and settings on Jitters Test Server?
A gather rate is not given in the name Jitters Test Server. Groups can contain up to 8 players, the default in the game. The server runs pve, no combat against other players. Plugins or settings change the game, and it is listed under Modded in the server browser. Carbon plugins run on this server. The server has VAC, Valve's anti-cheat, turned on.
About the server
Which version of Rust does Jitters Test Server run?
Rust network protocol 2635 and build 169621 on Linux is what Jitters Test Server runs. To join, your game must match the protocol; Steam handles the update.
Is Jitters Test Server online, and how reliable is it?
The server is up at the moment: Jitters Test Server is online. The uptime it reports puts the last restart at about 7 hours ago. 167 of 168 hours up over the last 7 full days, which is 99%. It first appears in Rust Heatmap records on 13 September 2026.
Where is Jitters Test Server located?
The NA tag is how Jitters Test Server lists itself in North America. Rust Heatmap shows the location a server states. It does not look up the machine's location. To connect, use 104.129.132.227:30015.
Does Jitters Test Server run smoothly?
It averaged 60 server fps over the last 48 hours, with a low of 58. Entities peaked at 93,000, counting buildings, deployables and all the rest of the world. At its peak it held 2,624 MB of memory. Players feel lag when fps falls and the entity count climbs.
Lists and filters
Which Rust Heatmap lists and filters include Jitters Test Server?
Modded Rust servers, by live population, Best Rust PvE servers and North America server heatmap are the Rust Heatmap lists that Jitters Test Server fits. Filtering the list by 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 brings it up.
What do the server tags on Jitters Test Server mean?
These are the tags Jitters Test Server publishes for the game's server browser to read: gmrust (Game mode): Rust survival, standard rules; mp10 (Max players): The slot count is 10; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): Your game must match protocol 2635 to get in; cs169621 (Build): Build 169621; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): The region code is blank; ^w (Weekly): Wipes run weekly; ^p (PvE): The world provides the danger, since players do not fight each other; ^z (Modded): Listed as Modded, since settings or plugins change the game; ^y (Carbon): The plugin framework in use is Carbon; NA (North America): The server browser lists it under North America. Also in the tags, shown at the top of this page: players now, the queue and the time the world was made.
How to join
How do I join Jitters Test Server?
To join by console, open it with F1 in Rust and enter client.connect 104.129.132.227:30015. Or press Launch Rust on this page, which connects you through Steam.