Offline 77.102.1.183:28011 checked 6d ago
test server
Connect
srv = rust.server("77.102.1.183:28018")
print(srv.connect_command)Right now
srv.summary()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. 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 65% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 22 Oct, 17:41 UTC6d ago | 1 | NaN | running | 0 |
| 1 | Sat 3 Oct, 00:47 UTC25d ago | 1 | NaN | 19.7 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 77.102.1.183:28011
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 22 Oct 2026, 17:50 UTC
- hostname
- –
- first seen
- 15 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 157 on average | 86/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 79/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 70/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 23/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 12/1000 |
Quick answers
From the figures on this page.
Population
What position does test server take in the server rankings?
Rank #14,336 on seven-day player hours for test server, within the top 65% of all ranked servers.
What population does test server carry?
The current row shows test server offline; the last response was 6 days 4 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
Server data
What Rust version does test server run?
Rust network protocol 2634 and build 167781 on Windows is what test server runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is test server, and is it online now?
test server is offline at this refresh; the last response came 6 days 4 hours ago. Over the last 7 full days the hours up number 5 of 168, 3%. Its earliest recorded date in Rust Data is 15 September 2026.
Which location does test server run from?
There is no region published for test server. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 77.102.1.183:28011 is its address.
Settings and map
What rules and settings are recorded for test server?
You will not find a gather rate in the string test server. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has test server selected?
A procedural map runs on test server, generated by the game.
Wipe data
When does test server wipe, and how often?
A rhythm cannot be read from the wipes of test server on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 6 days 4 hours ago.
On test server, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in.
Tags and filters
Which Rust Data filters and lists contain test server?
The Rust Data lists that test server fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on test server?
These tags are published by test server and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): 2 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Build number: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join test server?
Enter client.connect 77.102.1.183:28011 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.