Online 64.31.32.5:28015 checked 8m ago
TJA4-TEST
Connect
srv = rust.server("64.31.32.5:28016")
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, measured since 17 Sep. 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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
2000 · seed 1337
- map
- Procedural Map
- size
- 2000
- seed
- 1337
Server
srv.info()- address
- 64.31.32.5:28015
- region
- –
- max players
- 1000
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 31 Aug 2026, 14:03 UTC
- hostname
- –
- first seen
- 13 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 · 163 on average | 47/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 62/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 58/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 15/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 17/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does TJA4-TEST rank?
Rank #15,409 on seven-day player hours for TJA4-TEST, within the top 69% of all ranked servers.
How full does TJA4-TEST run?
TJA4-TEST reports 0 players at this refresh, with 1,000 slots configured. Over the last seven days it averaged 0 players.
About the server
How smoothly does TJA4-TEST run?
Averaged over 48 hours: 219 server fps, never under 159. The entity count peaked at 14,833, covering buildings, deployables and the rest of the world. A high of 4,846 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
Which Rust version is TJA4-TEST on?
Rust network protocol 2632 and build 161125 on Linux is what TJA4-TEST runs. Steam updates your game for you, but the protocol must match to join.
How reliable is TJA4-TEST, and is it up?
Online is the state at the latest refresh for TJA4-TEST. A restart about 7 days 16 hours ago is what its reported uptime implies. 168 of 168 hours up over the last 7 full days, or 100%. The first row Rust Data holds for it is dated 13 September 2026.
In which location is TJA4-TEST hosted?
There is no region published for TJA4-TEST. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 64.31.32.5:28015 is its address.
Rules, settings, map
Which settings and rules does TJA4-TEST run?
You will not find a gather rate in the string TJA4-TEST. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has TJA4-TEST selected?
The game generates the map on TJA4-TEST: procedural, size 2,000, seed 1337. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
When does TJA4-TEST wipe, and how often?
Too few wipes are on record for TJA4-TEST to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 57 days 9 hours ago, and that is the one in play.
Tags, lists
Which Rust Data filters and lists contain TJA4-TEST?
On Rust Data, TJA4-TEST appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on TJA4-TEST hold?
The game's server browser reads these tags from TJA4-TEST: gmrust (Game mode): Rust survival in its standard form; mp1000 (Max players): 1,000 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2632 (Protocol): Protocol 2632 is required; a different game version cannot connect; cs161125 (Build): The server runs build 161125; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join TJA4-TEST?
In Rust, F1 opens the console: type client.connect 64.31.32.5:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.