Online NA 157.85.86.76:21595 checked 12m ago
testing
Connect
srv = rust.server("157.85.86.76:21596")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
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 16 Oct. 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 69% of all ranked servers, top 83% in NA, and #378 of the duo servers (top 90%). Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Saturday 31 October, 16:01 UTC, in 3d 18h. # Its weekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 3d 18h | Sat 31 Oct, 16:01 UTC | wipe |
| 1 | 8d 21h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 10d 18h | Sat 7 Nov, 16:01 UTC | wipe |
| 3 | 17d 18h | Sat 14 Nov, 16:01 UTC | wipe |
| 4 | 24d 18h | Sat 21 Nov, 16:01 UTC | wipe |
| 5 | 31d 18h | Sat 28 Nov, 16:01 UTC | wipe |
| 6 | 36d 21h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 7 | 38d 18h | Sat 5 Dec, 16:01 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 24 Oct, 16:01 UTC3d ago | 0 | NaN | running | 0 |
| 1 | Sat 17 Oct, 15:10 UTC10d ago | 1 | halved by day 1 | 7 days | 1 |
| 2 | Fri 16 Oct, 10:42 UTC11d ago | 1 | NaN | 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.
display(srv.map, srv.info())Map
1000 · seed 50000
- map
- Custom Map
- size
- 1000
- seed
- 50000
Server
srv.info()- address
- 157.85.86.76:21595
- region
- NA
- max players
- 20
- group limit
- duo
- wipe schedule
- weekly
- last wipe
- 24 Oct 2026, 16:01 UTC
- hostname
- –
- first seen
- 16 Oct 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | RustForNoobs.com | Solo/Duo | Weekly | US | NA · duo · weekly · 100 on average | 23/100 |
| 1 | RustForNoobs.com | Mondays | Solo/Duo | US | NA · duo · weekly · 60 on average | 175/200 |
| 2 | US RustLife.net | Solo/Duo | Fridays | Noob Friendly | NA · duo · weekly · 3 on average | 3/100 |
| 3 | WARBANDITS.GG |Solo/Duo|Weekly| JUST WIPED | NA · duo · weekly · 3 on average | 3/100 |
| 4 | US RustLife.net | Solo/Duo | Mondays | Noob Friendly | NA · duo · weekly · 2 on average | 3/100 |
| 5 | WARBANDITS.GG 2X |Solo/Duo|X2 JUST FULLWIPED | NA · duo · 2x · weekly · 146 on average | 36/200 |
Quick answers
From the figures on this page.
Population
What position does testing take in the server rankings?
On seven-day player hours testing is #15,400 overall and #1,550 in North America, inside the top 69% of all ranked servers. Its position in the duo group is #378.
What population does testing carry?
testing reports 0 players at this refresh, with 20 slots configured. Over the last seven days it averaged 0 players.
About the server
What does performance look like on testing?
The 48-hour average is 238 server fps, with a low of 223. The entity count peaked at 7,087, covering buildings, deployables and the rest of the world. Memory peaked at 2,983 MB. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does testing run?
The build is Rust network protocol 2635 and build 168909 on Linux, run by testing. Joining needs the same protocol on your game; Steam handles the update.
How reliable is testing, and is it online now?
Online is the state at the latest refresh for testing. The uptime it reports puts the last restart about 32 hours ago. 168 of 168 hours up over the last 7 full days, or 100%. Rust Data logged it first on 16 October 2026.
Where does testing sit?
The NA tag is what testing 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. You can reach it at 157.85.86.76:21595.
Settings and map
What rules and settings are recorded for testing?
No gather rate appears in the name: testing. duo sets the cap: 2 players per group. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Carbon. VAC is running: Valve's anti-cheat is on.
Which map has testing loaded?
Size 1,000, seed 50000: the procedural map on testing, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Under map name you will find: Custom Map.
Wipe data
On what schedule does testing wipe?
The prediction follows the tag, because testing's wipes on record are too few to confirm the schedule. Saturday 31 October at 16:01 UTC is when the next wipe is due. The world it runs now was generated 3 days 5 hours ago. The tags list wipes as weekly.
On testing, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began. Half the peak or more was held to the next wipe in 0% of recent wipes. The drop under half arrived by day 1 in the other cases.
Tags, lists
Which Rust Data filters and lists contain testing?
These Rust Data lists include testing: Rust servers with a duo group limit, Modded Rust servers and North America Rust servers. These filters bring it up 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.
Which meanings do the tags on testing hold?
These tags are published by testing and read by the game's server browser: gmvanilla (Game mode): Game mode: vanilla survival; mp20 (Max players): 20 slots in total; ts2 (Group limit): No team may exceed 2; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^w (Weekly): The interval is one week; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins; NA (North America): The server browser files it under North America. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into testing?
In Rust, F1 opens the console: type client.connect 157.85.86.76:21595. Launch Rust on this page does the same by opening the game through Steam and connecting. https://discord.com/invite/BGKzykfwEC is the website recorded for it.