r2020-test
Offline 208.88.69.27:38389 checked 8d 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
- 984/ 100
- 246/ 400
- 210/ 245
- 123/ 100
- 520/ 1000
- 40/ 700
Quick answers
Tags and filters
Where does r2020-test appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry r2020-test are: Modded Rust servers. You can find it on the server list by these filters: 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 r2020-test?
r2020-test's game browser tags read: gmrust (Game mode): This is the standard Rust survival experience; mp1 (Max players): The slot count is 1; 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; cs167398 (Build): The build number is 167398; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): It has no region code; ^z (Modded): Plugins or settings make changes, so it's listed as Modded; ^y (Carbon): Plugins are handled by Carbon. 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 location is r2020-test in?
No region comes from r2020-test. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. The endpoint is 208.88.69.27:38389.
How reliable is r2020-test?
r2020-test is down at the moment; it was last up 8 days 4 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. 9 October 2026 is when Rust Going Deep first saw it.
What Rust version is r2020-test on?
On Linux, r2020-test runs Rust network protocol 2634 and build 167398. Steam handles the update; you just need your game on the matching protocol to join.
Wipe details
What schedule does r2020-test follow for wipes?
The wipes recorded for r2020-test are too few to reveal its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. This world has been running since 8 days 4 hours ago.
Settings and map
What settings and rules have been applied to r2020-test?
No gather rate appears in the name of r2020-test. Up to 8 players per group, which is the default. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. In the server browser it sits under Modded, where plugins or settings change the game. Plugins in use: Carbon. VAC is on: Valve's anti-cheat is active.
Player stats
Is r2020-test busy?
The last sighting of r2020-test was 8 days 4 hours ago; it is offline right now.
What's r2020-test's rank among Rust servers?
For player hours in the last seven days, r2020-test ranks #15,869, within the top 72% of ranked servers.
How to join
What's the process to join r2020-test?
Open Rust and press F1, then type client.connect 208.88.69.27:38389. Alternatively, click Launch Rust on this page to join via Steam.