Online 160.251.235.47:28015 checked 10m ago
TJA4-NEXUS
Connect
srv = rust.server("160.251.235.47:28017")
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 best
Top 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())
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 · 150 on average | 38/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 · 120 on average | 74/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 30/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 77/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 296/310 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does TJA4-NEXUS rank?
Over the last seven days TJA4-NEXUS sits at #15,276 on player hours, in the top 69% of ranked servers.
What population does TJA4-NEXUS carry?
TJA4-NEXUS reports 0 players at this refresh, with 100 slots configured. Over the last seven days it averaged 0 players.
Server data
What does performance look like on TJA4-NEXUS?
The 48-hour average is 104 server fps, with a low of 80. The entity count peaked at 29,427, covering buildings, deployables and the rest of the world. Memory peaked at 2,800 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What Rust version does TJA4-NEXUS run?
The build is Rust network protocol 2632 and build 160556 on Linux, run by TJA4-NEXUS. Steam updates your game for you, but the protocol must match to join.
Is TJA4-NEXUS up, and what does its uptime show?
The current sample puts TJA4-NEXUS online. A restart about 5 days 23 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 167 of 168, 99%. The first row Rust Data holds for it is dated 13 September 2026.
Where does TJA4-NEXUS sit?
There is no region published for TJA4-NEXUS. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 160.251.235.47:28015.
Rules, settings, map
Which rules apply on TJA4-NEXUS, and what settings?
You will not find a gather rate in the string TJA4-NEXUS. The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
What is the map on TJA4-NEXUS?
The game generates the map on TJA4-NEXUS: procedural, size 2,300, seed 5699. Because size and seed determine the map, it can be viewed on RustMaps via this page. Under map name you will find: Custom Map.
Wipe data
On what schedule does TJA4-NEXUS wipe?
Too few wipes are on record for TJA4-NEXUS to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 78 days 13 hours ago.
Lists and tags
Where does TJA4-NEXUS appear among Rust Data lists and filters?
On Rust Data, TJA4-NEXUS 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-NEXUS hold?
Read by the game's server browser, the tags TJA4-NEXUS publishes are: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2632 (Protocol): Protocol 2632 is required; a different game version cannot connect; cs160556 (Build): Build number: 160556; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to TJA4-NEXUS?
Enter client.connect 160.251.235.47:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.