☠

Torn Activity Tracker

Configure

A Public API key is all that is needed. By default your key is kept only for the current browser session and is sent to this server only to proxy requests to the Torn API. It is never stored or logged by this server. Tick "Remember key" to save it in this browser's local storage between sessions.

Bypasses cached member stats and fetches live data from Torn for every member. Expect longer run times for large factions.

Snapshot
Fetching activity for all members. If this is the first time you are analyzing this faction (or it has been a while), this may take several minutes depending on the number of members.

Refreshing ALL may take up to 2 minutes depending on the number of members.

Faction 1
Faction 2

Strength vs Activity

Battle-stat estimate against average daily activity over the past 60 days. The median lines split members into practical war-planning groups.

No battle-stat and activity data available.

High threat: strong and active targets to plan around. Power in reserve: strong but less active members. Ready support: active lower-stat members who may chain or assist. Low priority: lower-stat and less active members.

Strength vs War Commitment

Battle-stat estimate against each member's share of the faction's total ranked war attacks over the past 60 days. A member who landed 24 of the faction's 300 total attacks is at 8%. The axis maximum is the highest individual share across both factions. The median lines split members into practical war-planning groups.

Note: members who were not part of the faction during any ranked war in the past 60 days are excluded (e.g. recent recruits). Members present in a war but with zero attacks appear at 0%.

No battle-stat and ranked war data available.

Core fighters: strong and consistently shows up — highest priority targets. Power in reserve: strong but rarely commits to wars. Committed support: lower stats but reliably participates. Low priority: lower stats and rarely commits.

Member Threat Assessment

Members classified by combining battle-stat strength, 60-day daily activity, and share of faction ranked war attacks. Thresholds are the global median across all members of both factions combined. Click any category to expand the member list.

No data available.

Faction Radar Summary

Normalised faction comparison across combat strength, activity, ELO, recent war turnout, and repeat-core commitment.

Faction radar needs two factions with comparable data.

Avg BS: mean estimated battle stat. Members without an estimate are excluded. Weighted BS: battle-stat estimates weighted by each member's avg hours/day — a 6h/day player counts 6x more than a 1h/day player. Reflects realistic combat pressure from active members. Avg activity: mean of each member's avg hours/day = (timeplayed now - timeplayed 60 days ago) / 60 / 3600, averaged across all members with data. Avg ELO: mean Torn attacking ELO from current personal stats. Recent turnout: mean unique members with at least one hit in the last two ranked wars in the 60-day window (or one war if that is all they fought). This is who showed up, not who 1%s every war. Repeat core: % of the current roster who met the meaningful-hit bar in every ranked war in the 60-day window. The bar is the easier of 1% of that faction's attacks in the war, or the 25th percentile of members who attacked. Small wars stay on 1%; large spread-out wars do not require a linearly higher hit count. A faction that fought more wars has a harder bar. This is not unique attackers in the last war. Scale: each axis is normalised to 0-100 against the higher of the two faction values.

Battle Stat Tiers

Member counts by estimated battle-stat band. Estimates are current, not a 60-day snapshot.

No battle-stat estimates available.

Activity Distribution

Member counts by average hours played per day, measured over the past 60 days.

Inactive means fewer than 30 minutes per day on average. A member who played heavily for a few days but was otherwise absent may still appear in a higher band if their 60-day average exceeds the threshold.

No activity data available.

Faction Scanner Activity

Overlaid scanner activity for each faction. Hourly buckets (TCT / UTC); hover for exact times. Membership counts use a stored roster snapshot, not live Torn data.

Time range

No faction scanner activity data available.

Active %: distinct members with at least one scanner hit in the bucket, divided by roster size. Hover for raw active player counts.