AB test
Offline 97.94.248.135:28015 checked 31d 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 bestWipe 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
- 1/ 100
- 74/ 400
- 49/ 245
- 125/ 100
- 82/ 1000
- 5/ 700
Quick answers
Tags and search
Where does AB test appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry AB test are: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on AB test?
The server browser shows these tags for AB test: gmrust (Game mode): Survival, as standard Rust does it; mp1 (Max players): It holds 1 players; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs163794 (Build): The build number is 163794; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): No region is set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): You'll see it in Modded, since plugins or settings modify the game. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
About the server
What's the location of AB test?
AB test does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. You can reach it at 97.94.248.135:28015.
How reliable is AB test?
AB test is down at the moment; it was last up 31 days 2 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. 16 September 2026 is when Rust Going Deep first saw it.
What Rust version is AB test on?
On Windows, AB test runs Rust network protocol 2633 and build 163794. Steam handles the update; you just need your game on the matching protocol to join.
Wipe details
What schedule does AB test follow for wipes?
The wipes recorded for AB test are too few to reveal its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. 31 days 8 hours is how long ago this world came into being.
Settings and map
What settings and rules have been applied to AB test?
The name of AB test contains no gather rate. Up to 8 players per group, which is the default. survival is the game mode, gather, build and raid, the standard game. You can fight and raid other players. Plugins or settings change the game, so the browser lists it as Modded. You will find Oxide plugins installed. VAC, Valve's anti-cheat, is enabled.
Which map is active on AB test?
A procedural map, generated by the game, is in play on AB test.
Player count
Is AB test busy?
The last sighting of AB test was 31 days 2 hours ago; it is offline right now.
What position does AB test hold in the server rankings?
For player hours in the last seven days, AB test ranks #15,512, within the top – of ranked servers.
Getting in
What's the way to join AB test?
Open Rust and press F1, then type client.connect 97.94.248.135:28015. Alternatively, click Launch Rust on this page to join via Steam.