testtest
Offline 64.188.80.99:28015 checked 2d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server 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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
- 1000/ 100
- 168/ 400
- 127/ 245
- 132/ 100
- 369/ 1000
- 28/ 700
Quick answers
Tags and listings
Where does testtest appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry testtest are: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on testtest?
gmvanilla (Game mode): It's vanilla survival; mp1 (Max players): There are 1 slots on this server; ts8 (Group limit): The default team size of 8 applies here; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs167781 (Build): It's on build 167781; ptrak (Networking): Standard RakNet networking; $r? (Region code): It has no region code; ^z (Modded): You'll see it in Modded, since plugins or settings modify the game; ^y (Carbon): Plugins are handled by Carbon — that is the tag list testtest puts out for the game's server browser. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
About the server
What's the location of testtest?
No region comes from testtest. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. To connect, use 64.188.80.99:28015.
How reliable is testtest?
testtest is down at the moment; it was last up 2 days 2 hours ago. Of the 24 hours in the last 1 full day, 0 were online. That is 0% uptime. The first sighting by Rust Going Deep was on 15 October 2026.
What Rust version is testtest on?
The version on testtest is Rust network protocol 2634 and build 167781, on Windows. The protocol must match to join; Steam will update your game.
Wipe details
What schedule does testtest follow for wipes?
Too few wipes are on record for testtest to show its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. 12 days 8 hours is how long ago this world came into being.
Map and rules
What settings and rules have been applied to testtest?
No gather rate appears in the name of testtest. 8 players is the group cap, the game's default. survival is the game mode, gather, build and raid, the standard game. Fighting and raiding between players is allowed. Plugins or settings change the game, so the browser lists it as Modded. Carbon plugins are running here. VAC is on: Valve's anti-cheat is active.
What's the map on testtest?
testtest uses a game-generated procedural map.
Player stats
What's the population like on testtest?
Right now testtest is offline, with its last appearance 2 days 2 hours ago. Over the past week it has drawn 0 players on average.
What's testtest's rank among Rust servers?
Over the last seven days, testtest is #15,858 by player hours, among the top 72% of all ranked servers.
Getting in
What's the way to join testtest?
To join, open Rust, hit F1, and enter client.connect 64.188.80.99:28015. Or click Launch Rust on this page to open the game through Steam and connect.