A1243/ 2000 players
PvE#13,076
Testing Testing
Online NA 66.51.99.65:28010 checked 15m ago
biweekly wipes
moddedcarbonpve
players now0of 50 slots
7-day average0peak 3
rank#13,076top 59% · #1406 in NA
last wipe · restocked6h agobiweekly schedule
next wipe · restock13d 17hWed 28 Oct, 18:29 UTC
Players
Every five minutes, from the Steam server list.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 bestRankRank in region
Top 59% of all ranked servers, top 76% in NA. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Wednesday 28 October, 18:29 UTC, in 13d 17h. Its biweekly schedule tag · low confidence
14.6 daysusual gapbetween real wipes
0%on rhythmof its recent wipes
0wipe-day peakplayers, last three wipes
Coming wipes
- 13d 17hWed 28 Oct, 18:29 UTC
- 21d 17hThu 5 Nov, 19:00 UTCFW
- 27d 17hWed 11 Nov, 18:29 UTC
- 41d 17hWed 25 Nov, 18:29 UTC
The first 48 hours of its last wipes
Sat 3 OctTue 15 Sep
Players each hour, from the hour of the wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 14 Oct, 18:29 UTC6h ago | – | – | running | 0 |
| Sat 3 Oct, 13:58 UTC11d ago | – | – | 11.2 days | 0 |
| Tue 15 Sep, 14:33 UTC29d ago | 0 | – | 18 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.
Also on the shelf
Similar servers
The same kind of game, then region, group limit, rate and wipes.
A286/ 200 players
A327/ 45 players
B16/ 100 players
B23/ 75 players
B36/ 100 players
On the back of the pack
Quick answers
From the figures on this page.
Tags & lists
Can you explain the tags on Testing Testing?
Here are the tags Testing Testing lists, which the game's browser uses: gmrust (Game mode): Survival as standard Rust plays; mp50 (Max players): The cap is 50; ts8 (Group limit): The default cap is 8 per team; v2634 (Protocol): To join, your game version must line up with protocol 2634; cs167781 (Build): It runs on build 167781; ptrak (Networking): The game's usual network layer, RakNet, is used; $r? (Region code): Region code not set; ^b (Biweekly): Two-week wipe cycle; ^p (PvE): No player-on-player fighting: the danger comes from the world; ^z (Modded): Modded is its category, with plugins or settings changing the game; ^y (Carbon): The plugin framework here is Carbon; NA (North America): In the server browser it sits under North America. You will find its live player count, queue and world creation time in the tags too, displayed at the top here.
On Rust Vending Machine, which lists and filters can you find Testing Testing in?
These Rust Vending Machine lists include Testing Testing: Modded Rust servers, PvE Rust servers in stock and North America Rust servers. It shows under these filters on the server list: Region: North America; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours.
Map and rules
What map is in play on Testing Testing?
A procedural map, size 5,000 with seed 1337, generated by the game, is what Testing Testing runs. The map is the same for a given size and seed, so RustMaps can show it from this page. The map goes by: Custom Map.
What rules does Testing Testing enforce, and what settings does it run?
No gather rate is given in the name of Testing Testing. 8 players is the default group size, and that is the cap here. This server runs pve, other players are not fought. Plugins or settings change the game, so it is listed under Modded. You will find Carbon plugins running here. The server has VAC, Valve's anti-cheat, switched on.
About the server
What location is Testing Testing in?
With its NA tag, Testing Testing lists in North America. Rust Vending Machine reports the location a server claims, not where the machine actually sits. Find it at this address: 66.51.99.65:28010.
What is the uptime like on Testing Testing?
The shelves show Testing Testing in stock and online right now. The uptime counter points to a restart about 5 hours ago. Over 7 full days, the shelves were stocked for 168 of 168 hours (100%). The first sighting of it on Rust Vending Machine was 13 September 2026.
What is the performance like on Testing Testing?
Over the last 48 hours the average server fps was 54, with a low of 5. Up to 111,610 entities were in play, buildings, deployables and the rest of the world combined. The highest memory reading was 4,565 MB. Lag, as players feel it, is low fps plus a growing entity count.
What Rust version does Testing Testing run?
On Linux, Testing Testing is running Rust network protocol 2634 and build 167781. To get in, your game must match the protocol; Steam keeps that updated.
Player count
How does Testing Testing compare to other Rust servers in the rankings?
For player hours over the last seven days, Testing Testing is #13,076 across all ranked servers, in the top 59%, and #1,406 in North America.
Is Testing Testing busy at the moment?
You will find 0 players filling 50 slots in Testing Testing as things stand. It peaked at 3 this week, and the average was 0. Its busiest point in the last 48 hours was 18:00 UTC, averaging 1 players.
Wipe info
How often does Testing Testing wipe?
Too few wipes of Testing Testing are recorded to confirm its schedule, so its tag decides the prediction. It is due to wipe next on Wednesday 28 October at 18:29 UTC. 6 hours ago it made the world it is using now. The tags carry a two-weekly wipe schedule.
What can you expect on Testing Testing when wipe day comes?
The average busiest point of its recent wipes was 0 players.
Getting in
What steps do you take to join Testing Testing?
In the Rust console (F1), type client.connect 66.51.99.65:28010. You can also press Launch Rust on this page, which opens Steam and connects.
Server tags
what each one meansPublished as mp50,ptrak,$r?,v2634,^z,^y,^b,NA,^p,gmrust,cs167781,ts8
Game
gmrust
Game mode Survival as standard Rust plays.
mp50
Max players The cap is 50.
ts8
Group limit The default cap is 8 per team.
v2634
Protocol To join, your game version must line up with protocol 2634.
cs167781
Build It runs on build 167781.
ptrak
Networking The game's usual network layer, RakNet, is used.
$r?
Region code Region code not set.
Wipe schedule
^b
Biweekly Two-week wipe cycle.
Gameplay
^p
PvE No player-on-player fighting: the danger comes from the world.
Mods and access
^z
Modded Modded is its category, with plugins or settings changing the game.
^y
Carbon The plugin framework here is Carbon.
Region
NA
North America In the server browser it sits under North America.
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.