TornHelper

About TornHelper

Find targets, size them up and run wars with your faction. Here is what it does and what happens to your data.

A community tool. Not affiliated with Torn City or Torn Ltd.

At a glance

What it is

  • Targets: find players worth hitting and see their estimated stats.
  • Wars: a shared board, claims and a hospital list for your faction.
  • Free, and built on Torn's official API.

What it never does

  • No actions: you click Attack yourself.
  • No scraping: only Torn's official API.
  • No ads and no analytics.
  • No surprises: your key is only used for what you switch on.

Where your data lives: see Privacy and data use below.

What you can do

All of this is built and live. The badge shows the lowest Torn key level that works.

Targets

Find someone worth hitting.

  • Chain (Open)Key level: Limited

    Targets ranked by estimated fair fight, with a chain timer.

  • Levelling (Open)Key level: Public

    Inactive high-level players with live status, from our database, a search of Torn or Baldr's lists.

  • Bounties (Open)Key level: Public + Limited for FF

    Open bounties with live status.

  • Revenge (Open)Key level: Limited

    Who attacked you, so you can hit back.

Scout and Faction HQ

Look up an enemy, and fight together with your faction.

  • Scout (Open)Key level: Public + Limited for FF

    The enemy faction's members with estimates, fair fight and status.

  • Faction HQ (Open)Key level: PublicFaction mode

    Your faction's own space: war room, faction log and who gets in. A leader sets it up.

  • Faction log (Open)Key level: PublicFaction mode

    Claim a target with "I'm hitting this one" and see who hits whom.

  • War room (Open)Key level: PublicFaction mode

    A live board shared by your faction. A leader switches it on.

Lists

Keep the players you care about.

  • Your lists (Open)Key level: Public

    Your own target lists: private, faction or by link.

Tools

Small helpers around the site and on torn.com.

  • Userscript (Open)Key level: Public + Limited for FF

    Estimates and fair fight on torn.com.

  • Chain watch (Open)Key level: Public

    Chain timer alerts, with a live strip on every page.

  • Dock (Open)Key level: Public

    A small chain and war view you can pop out.

  • Keyboard shortcutsKey level: Browser only

    Ctrl K jumps anywhere. ? shows every shortcut.

  • PauseKey level: Browser only

    One switch that stops all Torn requests.

  • Settings (Open)Key level: Browser only

    Theme, colours, page width and row density.

The userscript

A small add-on for torn.com. It works in Tampermonkey on a computer and in TornPDA on a phone.

What it adds on torn.com

  • A badge on namesNext to player names on any page with profile links: faction lists, hospital, attack logs and more.
  • Colour tells the oddsFair fight is coloured: green from 2.5, lime from 2, yellow from 1.5, red below.
  • Hover for detailsShows estimated stats, how sure the estimate is and how many attacks it rests on. Unsure badges look fainter.
  • A box on profiles and attacksIn the bottom right corner: fair fight, estimated stats and how sure it is.
  • Target list side tabOptional and off by default: a small tab at the edge of Torn that shows who on one of your lists you can attack now, as plain links you press yourself.
  • Honest gapsNo badge for players with no estimate yet. The box says so.

What it needs

Your key

  • No key or Public: estimates only.
  • Limited (or Custom with basic, battlestats and attacks): adds fair fight.
  • TornPDA fills your key in for you.

What it sends

  • Player IDs from the page, to ask our server for estimates. No key.
  • Your key only if you share attacks (about every 30 minutes) or turn on the target list side tab (about every 6 hours): one request each time, not stored.
  • Sharing stays off until you have saved the script's settings once.

Install in 3 steps

  1. Get a script manager. Tampermonkey or Violentmonkey on a computer, or TornPDA on a phone.
  2. Install the script. Open the userscript page and confirm. In TornPDA: Settings, Advanced browser settings, Manage scripts, "+", Remote load/update.
  3. Set it up. Open any player profile in Torn and click Set up in the TornHelper box. Add a Limited key for fair fight.

Open the userscript page

Questions

Using TornHelper

Where do I start?

Start with Levelling, which needs no key. Connect a key later for the rest.

  • Look: Targets, then Levelling, lists inactive high-level players. It works without an API key.
  • Chain or Levelling: Chain ranks targets by estimated fair fight and shows your faction's chain timer, for fast, safe hits. Levelling is for finding inactive high-level players. Bounties and Revenge are the other two modes on the Targets page: open bounties, and who attacked you.
  • Connect: create a key in Torn's settings and paste it on the API key page. Limited access is enough. It adds live status, Chain, Lists and Torn search.
  • Attack: the button opens Torn's attack page and you do the click yourself.
What is fair fight, and why does it matter?

Fair fight is Torn's attack bonus. It runs from 1.00 to 3.00 and is higher against stronger targets.

  • Estimated fair fight is worked out from the stats TornHelper guesses for the target.
  • Needs a key that can read your battle stats (Limited or higher).
  • Treat it as a guide: see the accuracy question below.
Are the estimates accurate, and why does a target have none?

They are rough, so treat them as a guide.

  • Why: Torn never shows other players' battle stats, so TornHelper works them out from fair fight in attacks that players share.
  • More attacks on a target make its estimate more reliable than a single one.
  • Players who train a lot move away from old estimates.
  • Spread: the estimate assumes the four stats are evenly spread, so a lopsided build can have more.
  • No estimate: nobody has shared an attack on that player yet. TornHelper shows nothing rather than a made-up number. It appears once an attack on them has been shared, and you can help by turning on sharing in Settings.
Why is a status or number out of date?

Status comes from Torn when a target is checked, so it can be a little old.

  • Checks pause when TornHelper is paused or near Torn's limit.
  • Reload the page to check its targets again.
  • Estimates change only when new attacks are shared.
Where does the Baldr list come from?

From Baldr's levelling list, kept up to date by OranWeb.

Your key and your data

How does TornHelper use my key, and which level do I need?

Your browser talks to Torn directly with your key. Public is enough for most things, and Limited adds fair fight.

  • It reads player status, your battle stats, bounties, and your faction's war and chain.
  • In the war room your browser also reads the enemy faction for your faction, taking turns with other members.
  • Our server only sees the key if you share attacks, turn on faction mode or lists, or turn on automatic sync.
  • Public: status checks, bounties, your own lists and lists shared by link, the chain timer and the war member list.
  • Limited (or Custom with battlestats and attacks): fair fight, sharing your attacks and Revenge mode. Signing in to an account, faction mode and the war room need a Limited key, or a Custom one with at least battlestats.
  • War feed also needs faction API access to be allowed in your faction's settings. Full: don't use it.
More detail

The key goes in a request header and is never put in web addresses. Help pings don't use your key. The table below lists every selection.

Can using TornHelper get my account in trouble?

TornHelper only reads, and never acts for you in Torn.

  • You do the click: it links to the attack page and you attack. It never clicks or acts for you, as Torn's scripting rules require.
  • Official API only, within its limits.
  • You are still responsible for your account, so use a key made just for TornHelper and follow Torn's rules.

War and faction

What is the War room, and how do Help pings and Discord work?

A shared page for your faction's ranked war. A leader or co-leader switches it on.

  • You get a live enemy board with claims, a hospital reserve list, who is here and Help pings.
  • Who joins: members with faction mode on. Leaders can bar people.
  • Where it reads: members' browsers read Torn in turns with their own keys. Our server never calls Torn for the board.
  • Help pings: ask your faction for help with an enemy on the board, or for hits when the chain timer gets low (the room sends that one by itself). No free text, only who sent it, for what and when. Kept 14 days.
  • Discord: if a leader or co-leader adds a Discord webhook, pings are also posted in that channel.
More detail

The switch is under Settings in Faction HQ. It stays off until a leader turns it on. The webhook link is stored encrypted and used only to post pings. Nobody can read it after it is saved. Messages go from our server to Discord, whose terms then apply.

Which key do I need?

TornHelper only reads data; it can't do anything in your Torn account. Create a key just for TornHelper in Torn's settings. Every request carries the comment "TornHelper", so you can see exactly what it asked for in your Torn API log, and you can delete the key whenever you like.

Recommended: a Custom key with the selections listed below. A Limited key works too if you'd rather not pick.

Key levelWhat it unlocksWhat TornHelper reads
PublicLive status checks, the bounty finder, your own lists, the chain timer and the enemy member list on Scout. No fair fight against your own stats.Players' basic info and profiles (status, level, last action), faction members, your faction's chain and war, open bounties.
LimitedEverything Public does, plus fair fight on chain targets and bounties, sharing your attacks to improve the stat estimates, who attacked you, signing in to an account, faction mode and faction lists, and lists on Torn pages in the userscript.Your own battle stats and attacks. The war activity feed also needs faction API access to be allowed in your faction's settings.
CustomThe same as Limited, but with only the selections TornHelper uses.User: basic, profile, battlestats, attacks. Faction: basic, members, chain, wars, and attacks for the war activity feed.
FullNot needed.Don't use a Full key: it gives access to far more of your account than TornHelper reads.

Your key is kept in this browser and used from here to call Torn. It is sent to TornHelper's server only if you share your attacks (on each visit, at most every 10 minutes, not stored), turn on faction mode or use shared lists (once, to read your profile and the key's access level, not stored), or turn on automatic sync (stored encrypted).

Create a key in Torn's settings

Privacy and data use

The short version first. Every detail is under Full details.

Stays in your browser

  • Your API key, unless you use automatic sync
  • Settings and theme (copied to your account, if you make one)
  • Recent lookups and request times
  • Userscript: its key, settings and side tab list stay in your script manager

On our server

  • Estimates, anonymous
  • Your lists
  • Faction mode: your name on shared attacks and claims
  • War room: on or off, Help pings, chat messages and mutes, the room log, the chain watch schedule, Discord webhook (encrypted)
  • Faction HQ: who asked to join or was let in (player ID, name, status, role, who decided and when)
  • Your key, only with automatic sync, encrypted
  • Usage log: a pseudonym, the day and the tool, for 90 days
  • Account, if you make one: your player ID and name, your devices (a hash of the sign-in token and a short device name) the roles your browser reported and your synced settings
  • Stock market page: public market prices only, no player data

Who can see it

  • Everyone: estimates, which do not name you
  • Your faction: faction data, the war room, Help pings, chat messages, the room log, who is online
  • Leaders, co-leaders and officers: who switched the war room on and the Faction HQ member lists. Leaders and co-leaders only: reports of chat messages
  • Only you: your lists, until you share them, and your account and devices

How long things are kept, and how to remove them

  • Claims and reservationsA claim lasts 3 minutes, or until 30 seconds after the ETA you gave (at most 5 minutes 30 seconds). A reservation lasts at most 20 minutes.Minutes
  • Help pings, chat messages and room logDeleted after 14 days. You can delete your own chat messages sooner; a mute is deleted when it runs out.14 days
  • War room boardServer memory only, for at most a day. Gone on restart.Memory only
  • Who is in the war roomServer memory only. Gone when you leave.Memory only
  • Shared player statusServer memory only, for at most 10 minutes, with a scrambled code per reporter that is not shown to anyone. Gone on restart.How to remove it: Turn off sharing in Settings to stop adding to it (the userscript's side tab has its own switch in the script's settings, off by default; with it off the tab neither adds to the cache nor gets from it). What was shared is gone from our server's memory within 10 minutes.Memory only
  • Your key on our serverOnly with automatic sync, encrypted. Deleted when you remove it.How to remove it: Deleted when you remove the key in Settings (if you used automatic sync).Until removed
  • Stat estimatesAnonymous, so they stay.Kept
  • Faction log entriesStay with your faction.Kept
  • Faction HQ and Company HQ members, requests and tool switchesStay until a leader, co-leader or officer (in Company HQ: the director or an officer) changes them. A tool switch (changed by leaders and co-leaders only) records who last changed it and when, and who may see members' shared battle stats. Left entries are deleted after 90 days.Until removed
  • Shared battle stats (Faction HQ, only if you turn sharing on)Your exact strength, defense, speed and dexterity, latest reading only, with the time. Shown to your faction's leaders, co-leaders and officers, or to every approved member if a leader or co-leader chose that. Deleted by itself 30 days after it was last refreshed. The numbers come from the member's own browser and are not verified by TornHelper.How to remove it: Turn sharing off on the Members page of Faction HQ and it is deleted at once. It is also deleted at once when a leader or co-leader switches the tool off, when you are removed, and when you ask to delete your account. If you leave the faction, it is deleted the next time TornHelper sees you in another faction (when you turn on faction mode there), and at the latest 30 days after it was last refreshed.Until removed
  • Company employees and their history (Company HQ, only if the director switches the tool on)The latest employee list the director shared and one row per employee and day: player ID, name, position, days in the company, last activity, working stats and effectiveness. Shown to the director and officers. History is deleted after 90 days.How to remove it: Deleted at once when the director switches the tool off, with the next list for an employee who has left the company, and your own rows when you delete your account.90 days
  • Company stock and daily sales (Company HQ, only if the director switches the tool on)The latest stock list the director shared (product, amount in stock and on order, price, amount sold today) and the amount sold per product and day. No player data. Shown to the director and officers. Daily sales are deleted after 90 days.How to remove it: Deleted at once when the director switches the tool off, and for a product that is no longer in the next list.90 days
  • Job applications (Company HQ, only if the director switches the tool on)The latest list of applications the director shared: for each applicant the player ID, name, level, working stats, when the application expires and its status. Only open applications are kept; the application's message is not stored. Only the latest list is kept, no history. Shown to the director and officers. Deleted by itself 30 days after it was shared.How to remove it: Deleted at once when the director switches the tool off, and your entry when you ask to delete your account.30 days
  • The director's note (Company HQ, only if the director switches the tool on)One short text note per company that the director writes, with the time and the director's player ID. Shown to the director and every approved member. Only the latest version is kept.How to remove it: Deleted at once when the director saves an empty note or switches the tool off, and when the director asks to delete their account or the account is deleted after 12 months of not being used.Until removed
  • Discord webhookEncrypted, until a leader or co-leader removes it.Until removed
  • Your listsUntil you delete them.How to remove it: You can delete them at any time.Until removed
  • Usage log (who used what)A pseudonym, the day and the tool. Deleted after 90 days.How to remove it: Switch it off in Settings to stop it. What was logged is deleted by itself after 90 days.90 days
  • Account and devicesA device is forgotten 7 days after it signs out or expires. An account is deleted 30 days after you ask, or after 12 months without use. A suspended account is kept until its suspension ends or is lifted. No email is kept.How to remove it: Delete it in Settings under Account. You are signed out everywhere at once and it is removed after 30 days, unless you sign in again before then. A suspended account is kept until its suspension ends or is lifted.Until removed
Full detailsThe complete and exact version, in short lists.

In your browser

  • Your API key, your settings, the players you recently looked at and when TornHelper last sent a request.
  • These stay on your device.
  • The userscript keeps its data in your script manager's storage on your device: your key, its settings and, if you use the target list side tab, a pass for your lists, the list you chose (player IDs, names and levels) and a short-lived copy of those players' public status (whether they can be attacked, and until when). The script sends none of this anywhere, except what the side tab's checks found if you turn on Share what my checks find in its settings (off by default).
  • The only exception is the key, which is sent to our server in the cases the table below describes.

On our server

Always

  • Anonymous stat estimates built from attacks you share.
  • The lists you create (players, notes, your name as owner, and each player's faction ID when it is known: you added a whole faction or a player from a table that shows it, or the userscript's side tab read it and you turned on sharing there).
  • The stock market page shows public market data (stock prices, share counts, item and point prices) that our server reads from Torn with the site's own key, on a timer. It uses no player data and no visitor's key, and nothing about the people who open it is read or stored. The values you type there stay in your browser.

In faction mode

  • Your name with your shared attacks, for your faction.
  • The player you claim or reserve, for a few minutes.
  • Whether your faction's war room is on and who switched it.
  • Your request to join Faction HQ and your membership there: your name, your status, your role, who decided and when. Left entries are deleted after 90 days.
  • Only if you have an account and turn sharing on in Faction HQ: your exact strength, defense, speed and dexterity, read by your own browser with your key (the key is not sent), the latest reading only, with its time. Your leaders, co-leaders and officers see it, and every approved member too if a leader or co-leader opened it. Turning sharing off, being removed, the tool being switched off or deleting your account removes it. If you leave the faction, it is removed the next time TornHelper sees you in another faction, and at the latest 30 days after the last refresh. The numbers come from your own browser and TornHelper does not verify them.

In Company HQ

  • Your request to join your company's Company HQ and your membership there: your player ID and name, your status, your role, who decided and when. Left entries are deleted after 90 days; the others stay until the director or an officer changes them.
  • Your company, and whether you are its director or an employee, is read from Torn once with your key (the key is not stored) and kept only in a signed cookie in your browser for one hour. Company HQ's tools store more only when the director switches them on.
  • Only if the director has an account and switches the employees tool on: the director's own browser reads the employee list from Torn with their key (the key is not sent) and the server stores, for each employee, the player ID, name, position, days in the company, last activity, working stats and effectiveness, the latest list plus one row per employee and day. Only the director and officers see it. History is deleted after 90 days, with the next list for someone who has left the company, at once when the director switches the tool off, and for your own rows when you delete your account. Wages and company value are not stored.
  • Only if the director has an account and switches the stock tool on: the director's own browser reads the company's stock from Torn with their Limited key (the key is not sent) and the server stores, for each product, its name, price, amount in stock and on order and amount sold today, the latest list plus the amount sold per product and day. There is no player data in it, not even who sent it. Only the director and officers see it. Daily sales are deleted after 90 days and everything at once when the director switches the tool off.
  • Only if the director has an account and switches the applications tool on: the director's own browser reads the job applications from Torn with their Limited key (the key is not sent) and the server stores, for each applicant, the player ID, name, level, working stats, when the application expires and its status, never the application's message. Only open applications are kept. Only the latest list is kept, with no history. Only the director and officers see it. It is deleted 30 days after it was shared, at once when the director switches the tool off, and your entry when you delete your account.
  • Only if the director has an account and switches the note tool on: the director writes one short text note (at most 2000 characters) that is stored with the time and the director's player ID. The director and every approved member of the Company HQ see it. Only the latest version is kept. It is deleted when the director saves an empty note, switches the tool off or deletes their account (or their account is deleted after 12 months of not being used).

Help pings and Discord

  • Help pings (who sent one, for a target or the chain, the target and when) are kept for 14 days. The room's own chain timer warning has no sender. The chain watch schedule (the hours you signed up for) is kept until 14 days after the hour.
  • The war room log (a call with the ETA you chose, a release, a done mark you set yourself, a ping, someone joining or leaving, someone signing up for or leaving a chain watch hour, the chain timer going low or breaking, with who did it, the enemy it was about and when) is kept for 14 days. It has no free text and nothing from your attacks.
  • War room chat messages (the text, the channel, the war it belongs to, the enemy it names if you picked one, your player ID and name, and when) are kept for 14 days. You can delete your own messages at any time; a leader or co-leader can delete any message in their faction. A mute a leader or co-leader sets on you (until when, and who set it) is kept until it runs out. Deleting your account deletes your messages too; an account that goes unused does not, and your messages then stay until the 14 days are over. A report of a message is a line in the war room log, without the text, and only leaders and co-leaders can see it. There is no moderation queue outside your faction.
  • A Discord webhook that a leader or co-leader adds is stored encrypted and used only to post Help pings.

Server memory only

  • In the war room, the board that members' browsers read from Torn (the enemy's public member status and the ranked war score and chain) is kept for at most a day.
  • It is lost when the server restarts.
  • The public status of players your browser checked (okay, in hospital, jail, travelling or abroad, and until when) is kept for at most 10 minutes and shown to other visitors who look at the same players, so they need fewer API calls. It is added only if you are signed in and turned it on in Settings, and who added it is not kept. The userscript's side tab takes part too, only if you turn on Share what my checks find in its settings (off by default) and your player ID has an account: it then tells our server which list is open and the statuses it holds with their age, only to get the plan back and not stored, and it adds the statuses it read. It sends its pass, which holds your player ID and name, never your key. With that switch off it sends our server nothing about your lists and gets no plan or shared statuses.

Usage statistics

  • Once a day for each tool you open (and once a day for the userscript), a row is added with a pseudonym of your player ID, the day, the tool and whether it came from the site or the userscript.
  • The pseudonym is a keyed hash. Without our secret it cannot be turned back into your ID, and it is a different value from the one used for shared attacks, so the two cannot be matched.
  • No name, no API key and no IP address are stored with it. Rows older than 90 days are deleted.
  • It is sent only while a key is connected, never while Offline mode is on, and you can switch it off in Settings. The player ID comes from your browser and cannot be checked, so limits on how often and for how many players one browser may report keep the totals honest.

Account (only if you make one)

  • Your player ID and name, when the account was made and when it was last used, and its status (if it was suspended: until when, with a fixed reason code).
  • For each device you are signed in on: a hash of its sign-in token (the token itself is only in your browser's cookie), a short device name such as "Chrome on Windows", and when it signed in, was last used, expires and was signed out.
  • The faction and company roles your browser last reported, read from Torn by your browser with your key. Our server does not check them.
  • Settings that follow you across devices: display and live-check preferences, goals, the chain alert threshold and sound, the live strip pin, tagged players, remembered filters and table setups, Open my last tool directly, the room Torn-reads switch and whether the tour is done. One small record per area (at most 16 KB). Never your key, offline mode, request times or Discord webhook.
  • Devices are forgotten 7 days after they sign out or expire. Deleting your account removes it after 30 days, and an account that has not been used for 12 months is deleted (a suspended account is kept until its suspension ends or is lifted). We have no email address for you, so we cannot send you notices.
  • You can download your account data as a file in Settings: the account, devices (without the token hash), synced settings, your lists, your Faction HQ memberships, your shared battle stats, the Company HQ employee history kept about you and the HQ tool switches you last changed, your contributor settings (without any key), your claims, your Help pings, your chat messages and the mutes against you. The anonymous usage log is not in it: it cannot be linked to you by design.
  • The people who run TornHelper have platform roles (admin or moderator) stored with their player ID, who gave the role and when. These roles only open the admin page; they give no access inside a Faction HQ or Company HQ. To confirm themselves there, they must use one registered API key, of which only a one-way hash is stored (never the key). Everything an admin or moderator does there (suspending or lifting a suspension, signing an account out everywhere, cancelling a deletion, giving or removing a role, registering the one key they confirm themselves with) is written to an audit log with their player ID, the account it concerned, a fixed action name, a few codes or counts (never a key or a token) and the time. Audit entries are deleted after 12 months. Admins cannot see your key, your sign-in tokens or what you do on the site, and cannot sign in as you.
  • TornHelper never asks for your key in Discord or in game. The only place to type a key is the API key section in Settings.

Your key

  • Stored only if you turn on automatic sync, and then encrypted.
  • If you use the userscript's target list side tab, the key is sent about once every 6 hours, in a single request that is not stored. Our server uses it for one read of your profile and one of the key's access level from Torn, to learn who you are and whether the key is Limited or better, and returns a pass for your lists that is valid for 6 hours and says whether you have an account. Apart from that and reading your lists, the side tab sends our server nothing unless you turn on Share what my checks find in its settings (off by default).

Who can see it

Everyone

  • Estimates are shown to everyone and don't identify you.
  • The usage log is never shown per player. It is only ever used as totals.

Your faction only

  • Faction data is shown to your faction only.
  • While you are connected to the war room, your name is shown to your faction's other connected members. It is kept in the server's memory only and forgotten when you disconnect.
  • What the war room shows from Torn (the board, whether your faction's members are online, your claims and reservations) is shown to your faction only.
  • Help pings are shown to your faction, and to its Discord channel if a leader or co-leader added a webhook (Discord's terms then apply there). Nobody can read the webhook URL after it is saved.
  • The room log and the chain watch schedule are shown to your faction only.
  • Chat messages are shown to your faction's connected members with your name. They are never posted to Discord. Only torn.com links in a message can be clicked; other addresses stay plain text.

Leaders and co-leaders

  • Who switched the war room on is shown to your faction's leaders and co-leaders. The Faction HQ member lists are shown to them and to the officers they appoint.
  • A report of a chat message (who reported it and whose message it was, not the text) is shown to your faction's leaders and co-leaders only, in the room log.
  • Your role comes from your faction's public information.

Lists

  • Lists are private unless you share them.

IP addresses and ads

Like any website, our server and its network provider see your IP address. We use it only to limit abuse, and we run no ads and no third-party analytics. The only usage log is the pseudonymous one described above, which holds no IP address.

The disclosure Torn's terms require:

How TornHelper uses your key

Required disclosure under the Torn API terms of service.
FieldTornHelper
Data storage
  • Persistent: anonymous stat estimates of players you attacked, if you share attacks.
  • Lists you make: the players on them with their names, levels, notes and, when it is known, their faction ID (saved when you add a whole faction or a player from a table that shows the faction, and when the userscript's side tab reads their faction and you turned on sharing there), and your name as owner, until you delete the list or it expires.
  • In faction mode, also your name with your shared attacks for your faction, and the player you claim or reserve in the war room for a few minutes (a reservation for at most 20 minutes).
  • For a faction's war room: whether it is on and who switched it.
  • For a faction's Faction HQ: its name, who set it up and whether members are approved one by one, and for each member who asked to join or was let in: player ID and name, the status (waiting, approved, declined, removed or left), the HQ role (member or officer), when they asked and who decided and when.
  • Left entries are deleted after 90 days; the others, declined ones included, stay until a leader, co-leader or officer changes them.
  • For a company's Company HQ: its name, the player ID of the director who registered it and whether employees are approved one by one, and for each employee who asked to join or was let in: player ID and name, the status (waiting, approved, declined, removed or left), the HQ role (member or officer), when they asked and who decided and when.
  • Left entries are deleted after 90 days; the others, declined ones included, stay until the director or an officer changes them.
  • Whether you are a company's director or an employee, and which company, is read from Torn once with your key (the key is not stored) and kept only in a signed cookie in your browser for one hour; it is not stored on our server.
  • Company employees, only if the company's director has an account, is in Company HQ and switches the tool on: the director's own browser reads the list of employees from Torn with the director's key (the key is not sent to us) and sends it, and we store, for each employee, their player ID, name, position, days in the company, when they were last active, their three working stats and their effectiveness (total, working stats and inactivity), with the time.
  • The latest list is kept, plus one row per employee and day with the working stats and effectiveness, so the HQ can show what changed.
  • History older than 90 days is deleted by the worker, an employee who is no longer in the list loses their history with the next one, and everything is deleted when the director switches the tool off.
  • If you are an employee and delete your account, your own rows are deleted from the list and the history at once, and the next lists leave you out while the account waits to be deleted (once it is gone, a list adds you again while you work there).
  • Wages and company value are not stored.
  • Company stock, only if the director has an account, is in Company HQ and switches the tool on: the director's own browser reads the company's stock from Torn with the director's Limited key (the key is not sent to us) and sends it, and we store, for each product, its name, price, amount in stock and on order and amount sold today, with the time, plus the amount sold per product and day; it contains no player data, the daily sales are deleted by the worker after 90 days and everything is deleted when the director switches the tool off.
  • Company job applications, only if the director has an account, is in Company HQ and switches the tool on: the director's own browser reads the applications from Torn with the director's Limited key (the key is not sent to us) and sends them, and we store, for each applicant, their player ID, name, level, their three working stats, when the application expires and its status (only open applications are kept, never the application's message), with the time.
  • Only the latest list is kept, with no history; it is deleted by the worker 30 days after it was sent and at once when the director switches the tool off, and an applicant who asks to delete their account is taken out of it at once (the next lists leave them out while the account waits to be deleted).
  • The Company HQ note, only if the director has an account, is in Company HQ and switches the tool on: one plain text note of at most 2000 characters that the director writes, with the time and the director's player ID, replaced each time it is saved; it is deleted when the director saves an empty note, switches the tool off or asks to delete their account (or their account is deleted after 12 months of not being used), and with the Company HQ.
  • Which HQ tools a leader or co-leader (in Company HQ: the director) switched on for the faction, who the leader or co-leader chose to show members' shared battle stats to (leaders, co-leaders and officers, or every approved member), with their player ID and when they last changed each switch, until they change it again; the player ID is erased from it when that account is deleted.
  • Shared battle stats, only if you have an account, are in Faction HQ and turn sharing on yourself in the HQ's Members page: your exact strength, defense, speed and dexterity (and so their total), read from Torn by your own browser with your key (the key is not sent to us), with the time it was sent.
  • Only the latest reading is kept, no history.
  • It is replaced with a fresh reading when you open the Members page of Faction HQ with sharing on and the last reading is more than an hour old.
  • It is deleted when you turn sharing off, when you are removed from the HQ, when a leader or co-leader switches the tool off, and when you ask to delete your account.
  • If you leave the faction, it is deleted the next time TornHelper sees you in another faction (when you turn on faction mode there).
  • Whatever happens, it is deleted by itself 30 days after it was last refreshed.
  • The numbers are read by your own browser, and TornHelper does not check that they are true.
  • Help pings in the war room: who sent it (player ID and name; none for the warning the room sends by itself when the faction's chain timer is low, which has the chain length and the seconds left instead), whether it is for a target or the chain, the target's ID and name, and when, for 14 days.
  • War room chat: the messages you write (the text, the channel, the ranked war it belongs to, the enemy from the board it names if you chose one, your player ID and name, and when), for 14 days, or until you or a leader or co-leader delete one, or you delete your account (an account that just goes unused does not take them with it); the mutes a leader or co-leader sets on you (your player ID, until when, who set it and when), until they run out; and the reports of a message, which are only a line in the war room log with no message text.
  • The chain watch schedule: the hours you sign up for, with your player ID and name, until 14 days after the hour; and the chain warning a leader or co-leader sets for the faction (how much time is left on the timer when the room is warned, and the least chain length it is warned for); and, for the chat's war channel, when the faction's last ranked war started and when the room saw it end (the war's public times, no player data), so the war channel stays open for 24 hours after a war.
  • The war room log: what happened in the room (a call, release, Help ping, someone joining or leaving, someone signing up for or leaving a chain watch hour, or the faction's chain timer going low or breaking), with the player ID and name of who did it, the ID and name of the enemy it was about, the chain length (or the hour of a chain watch block) and when, for 14 days; it has no free text and nothing from your attacks.
  • The log also notes when a leader or co-leader deletes someone's chat message or mutes someone, and when a member reports a message (the report is shown to leaders and co-leaders only), with the player ID and name of who did it and of the message's author, never the message text.
  • A leader or co-leader can add a Discord webhook for the faction: its URL is stored encrypted, with who added it and when, until it is removed, and used only to post Help pings.
  • Temporary, in the server's memory only and gone at the latest within a day: who is in the war room, and the board that members' browsers read from Torn (the enemy members' public name, level, hospital, jail or travel status and last action, our own members' status and last action (whether they are online, idle or offline, from Torn's public members list), the ranked war score and the faction chain).
  • Also temporary, in the server's memory only: the public status (okay, in hospital, jail, travelling or abroad, and until when) of players your browser checked, for at most 10 minutes, next to a scrambled code per reporter that cannot be turned back into your ID.
  • The server uses it only to tell reports from different players apart, and it is gone on restart.
  • Usage log: a pseudonym of your player ID (a keyed hash that cannot be turned back into your ID or matched to your shared attacks), the day, the tool you opened and whether it was the site or the userscript, once per tool per day, for 90 days, to count how many players use what; no name, key or IP address.
  • You can switch it off in Settings.
  • Your key, settings (an account also keeps most of them, see below), the players you tagged (at most five, only their IDs), the status of players you recently looked at and, for a minute, the answers to your Ready now searches and, for ten minutes, the times and the feature of your latest Torn requests (used to keep TornHelper within its limit of 75 requests a minute) stay in your browser, as does a short tag of the key the lists sign-in last ran for (not the key), so a changed key is signed in again once.
  • The target filters you apply, and how you set up each player table (the column it is sorted by, rows per page, the Targets mode, levelling source and Baldr list you chose, and the bounty and attacker settings), are remembered in cookies in your browser until you change or reset them; they are sent to our server only as part of the page request and never anywhere else unless you have an account (see below).
  • Accounts, if you create one: your player ID and name, when the account was made and when it was last used; its status and, if it was suspended, until when and a fixed reason code; for each device you are signed in on, a hash of its sign-in token (never the token itself), a short device name such as "Chrome on Windows" (never your browser's full identification), and when it signed in, was last used, expires and was signed out; and the faction and company roles your browser last reported (IDs, roles and when), read from Torn by your browser with your key, which our server does not check.
  • Synced settings, if you are signed in, so they follow you to your other devices: your display and live-check preferences (including the Look studio and table defaults), your goals, the chain alert threshold and sound, whether the live strip is pinned, the players you tagged, your remembered target filters and table setups, whether Open my last tool directly and the war room Torn-reads switch are on, and whether you finished the tour.
  • Each of these areas is stored as one small record (at most 16 KB) with a version number and the time it last changed, and goes when the account does.
  • Your key, offline mode, request times, status cache and Discord webhook are never synced.
  • Platform roles, for the people who run TornHelper: their player ID, the role (admin or moderator), who gave it and when, and a one-way hash (SHA-256) of the one API key they confirm themselves with on the admin page (never the key itself), kept until the role is removed or the account is deleted.
  • An audit log of what admins and moderators do in the admin page (suspending or lifting a suspension, signing an account out everywhere, cancelling a deletion, giving or removing a role, changing a feature flag, registering an admin key): their player ID, the account it concerned, a fixed action name, a few codes or counts (never a key or a token) and the time, kept for 12 months.
  • Feature flags, for trying a feature out with some people: which flag is on for whom, and an allowlist of player, faction and company IDs, with who changed it and when.
  • A suspended account is kept, with the end date and a fixed reason code, until the suspension ends or is lifted, even past the usual deletion times.
  • Re-checking a key for the admin page works like signing in: the key is sent once, used to read whose it is and what level it has, and not stored (for people with a platform role, only the hash above is kept, to tell whether it is the same key next time).
  • You can download everything stored on your account as one file in Settings (the anonymous usage log is not in it, because it cannot be linked to you).
  • The sign-in token itself is a random value kept in a cookie in your browser.
  • A device is forgotten 7 days after it signs out or expires.
  • Deleting your account signs you out everywhere at once and removes the account and what is stored on it after 30 days (signing in again within 30 days restores it), and an account that has not been used for 12 months is deleted.
  • We have no email address for you, so we cannot send you notices.
Data sharing
  • General public: stat estimates of other players are shown to everyone, and nothing identifies you.
  • The status of players your browser checks is shared with other visitors for a few minutes so they need fewer API calls, only if you are signed in and turned it on in Settings; nothing identifies you.
  • Faction: in faction mode, your shared attacks and claims are shown to members of your faction.
  • In your faction's war room, your faction's other members see your name while you are there, the targets you claim or reserve, the board your browser or theirs read from Torn (including whether you are online, idle or offline), the chat messages you write (with your name), the room log of what happened in the room, and the chain watch schedule you sign up for; none of that goes outside your faction, except that a Help ping (who sent it, for what and when, or the warning the room sends by itself when the chain timer is low) is also posted to your faction's Discord channel if a leader or co-leader added a webhook, and Discord's terms then apply there.
  • Chat messages are never posted to Discord.
  • A report of a message is shown only to your faction's leaders and co-leaders.
  • Lists are private unless you share one with your faction or with anyone who has its link; shared lists show your name.
  • Chain alerts go only to a Discord webhook you add, straight from your browser.
  • Whether your faction's war room is on is shown to your faction's members; who switched it on is shown to its leaders and co-leaders.
  • Faction HQ membership (who asked, who is in, who was removed and who decided) is shown to your faction's leaders, co-leaders and officers; you see only your own status.
  • Company HQ membership (who asked, who is in, who was removed and who decided) is shown to your company's director and officers; you see only your own status.
  • Company employees (if the director switched the tool on) are shown to the director and the officers of the Company HQ only, with each employee's name and their change since the last list; other employees see nothing.
  • Company stock and job applications (if the director switched those tools on) are shown to the director and the officers only; the applications show each applicant's name, level and working stats, and no other employee sees them.
  • The director's note (if the director switched the tool on) is shown to the director and every approved member of the Company HQ.
  • Which HQ tools are switched on is shown to approved members of the Faction HQ, and the player ID of whoever last changed a switch to leaders and co-leaders.
  • Your shared battle stats (if you turned sharing on) are shown with your name to your faction's leaders, co-leaders and officers, and to every approved member of the HQ if a leader or co-leader opened them to everyone (the HQ says which); you always see your own, and they are shown to others only while no older than 7 days.
  • In faction mode your role (leader, co-leader or member) is read from your faction's public information and kept only in a signed cookie in your browser.
  • The usage log is never shown per player: it is only ever used as totals.
  • Your account, its devices and the roles your browser reported are not shown to anyone else.
Purpose of usePublic community tools; faction tools in faction mode and shared lists; Company HQ for your company's director and employees, with an overview of the employees and their working stats over time, the company's stock and daily sales and its job applications for the director and officers, and a note from the director for the members; anonymous usage statistics; your own bars, cooldowns and status on the start page, read from your browser and not stored; signing in to your TornHelper account and, later, keeping your settings across devices; fewer API calls for everyone through a shared short-lived status cache
Key storage & sharing
  • Not stored, unless you turn on automatic sync: then stored encrypted and used only to read your attacks and battle stats.
  • Creating an account or signing in sends your key to our server once to check who you are and what access level it has; it is not stored.
  • Turning on Company HQ does the same and also reads your job and your company (its name and director) once; the key is not stored.
  • For the people who run TornHelper (admins and moderators), a one-way hash of the key they confirm themselves with on the admin page is kept, never the key.
Key access levelPublic for your own lists and lists shared by link; Limited or Custom (battlestats) for faction lists and for lists on Torn pages in the userscript; Limited or Custom (battlestats, attacks) to share attacks, see fair fight and see who attacked you; faction attacks with faction API access to see who is hitting whom; Limited or Custom for creating an account, signing in, faction mode, Company HQ mode and the admin page's key check (a Public key is refused there, because Public keys are shared with many other sites); Limited or Custom (company) for the director to read the company's stock and job applications for Company HQ; Public for the faction and role your browser reports to your account

Required disclosure under the Torn API terms of service.

Fair use

Torn allows 100 requests a minute per player, across all your tools. TornHelper keeps to 75 a minute in total from your browser, so there is room for the rest.
Torn's limit
100 per minute
Status checks
40 per minute
Ready now searches
10 per minute
List lookups
30 per minute
Chain reads
10 per minute
War room reads
30 per minute

TornHelper's own caps, per browser. All of them together stay under the total of 75 a minute.

  • Meter: the status pill in the header shows requests sent in the last minute. It counts only TornHelper in this browser, not the userscript, TornPDA or other tools.
  • Pause: open the status pill and choose Paused (or press P), or use the Offline mode switch in Settings. While paused, this browser sends nothing to Torn, pages keep their data and the meter drops to zero. Automatic sync on our server is not paused; turn that off in Settings to stop it too.
  • Careful: identical requests are cached, status checks pause for 30 seconds after Torn reports the limit, and a key Torn reports as disabled is dropped.

Use a key made for TornHelper, and don't share it. If you stop using TornHelper, delete the key in Torn's settings.

What's new

Changes players will notice, newest first.

v0.3.3Released 2026-11-01

New

  • Userscript: the target list tab on a profile or attack page has an "Add this player to a list" button. Pick one of your lists, or make a new one right there.

v0.3.2Released 2026-11-01

v0.3.1Released 2026-10-31

Improved

  • Userscript: the bar on a profile page appears at once with its space reserved, so the page no longer jumps when the lookup finishes.
Earlier releases

v0.3.0Released 2026-10-30

Improved

  • Targets: estimated stats now show on phone cards, and a missing estimate shows a dash in Bounties, Revenge and your lists.

v0.2.8Released 2026-10-30

New

  • Company HQ: a company director can open the company's own space, decide which employees get in, and share the employee list with trains, the stock and sales, the job applications and a note. Directors choose each tool and the key stays in the browser.

v0.2.7Released 2026-10-30

Fixed

  • Reading your attacks no longer skips attacks that happened in the same second at the edge of a page, and shared-status entries you have not saved yet survive when another tab writes.
  • Lists keep to their size limits even when several adds arrive at once, and deleting an account removes everything in one step.

v0.2.6Released 2026-10-30

Improved

  • Signing in, faction lists and the userscript's shared lists now need a Limited or Full key (or a Custom key with battle stats). Private lists still work with a Public key. Existing sessions keep working until they expire.

Fixed

  • A hiccup from Torn (a key that was too low, a key cooldown) no longer marks players as "Not found in Torn" for a day; only Torn's own "no such player" answer does.

v0.2.5Released 2026-10-29

Improved

  • Lists use fewer API calls: Auto-update lets in fewer extra rows and rests when most of them turn out to be in hospital, and a player in hospital for a long time is not checked again until the last five minutes.

v0.2.4Released 2026-10-29

New

  • War room Chain tab: the faction's chain timer, who can hit now, a sign-up schedule for chain watch hours, and a warning when the timer runs low (a leader picks when and for how many hits; it can also post to Discord).
  • War room chat: short messages for your faction, with a separate channel for the current war. Report a message to your leaders, or hide a player just for you. Messages are kept 14 days.
  • Userscript: the note you wrote on a player in a list now shows under the name in the side tab.

Improved

  • The FAQ is shorter: repeated answers are merged, one table covers how long things are kept and how to remove them, and the footer's version links to What's new.

v0.2.3Released 2026-10-28

New

  • With a TornHelper account and sharing switched on, the userscript's side tab and Torn PDA get fresher target lists with fewer API calls: the site tells the script which players to check next and shows statuses other players already found, shared for a few minutes. In return the tab shares what its own checks find. Sharing is the switch "Share what my checks find" in the script's settings, off by default. Off, or without an account, the side tab works exactly as before and sends the site nothing about your lists.

v0.2.2Released 2026-10-28

New

  • Signed-in players can share the statuses their checks find (Settings, off by default), so everyone needs fewer API calls on the same lists.

v0.2.1Released 2026-10-27

New

  • Signed in with an account, your look, goals, chain watch, tags and remembered filters now follow you between devices. If this device and your account differ the first time, you choose which to keep.
  • Download everything stored on your account as a file from Settings.

v0.2.0Released 2026-10-27

New

  • Optional TornHelper accounts: create one in Settings with the key you already connected (it is checked once and not stored), see the devices you are signed in on, sign them out, or delete the account with 30 days to change your mind.

Fixed

  • Settings no longer scrolls sideways on a phone.

v0.1.3Released 2026-10-27

New

  • Userscript: a side tab on Torn pages opens one of your TornHelper lists and shows who you can attack right now. Turn it on under Pages in the script's settings.
  • Levelling hides players whose estimated stats are far above your own (where fair fight already tops out), with a button to show them anyway.

Improved

  • The live strip never scrolls sideways: on a narrow window it drops the least important pieces first.
  • Scout and Lists now share the Targets layout: same title, toolbar and table.
  • Userscript: an Open TornHelper link under the TH button and in the settings header.

Fixed

  • The TornPDA install steps now match the app's real menu.

v0.1.2Released 2026-10-27

New

  • Settings is rebuilt as a control panel with search, and a Look studio shows your changes live.
  • Quick settings: the gear in the top bar (or the Menu on a phone) changes the look without leaving the page.

Improved

  • TornHelper keeps all its Torn calls under one shared limit, so it never eats your whole API budget.
  • Each row shows whether it is being checked, waiting its turn, not checked yet or couldn't be checked.

Fixed

  • Players Torn can't find are hidden instead of being checked again and again, and rechecked after a day.

v0.1.1Released 2026-10-27

New

  • With a key saved you land straight on Targets, with your energy, health and status in the live strip.
  • Fast mode and tags: the next players out of hospital and up to five tagged players are checked first.

Improved

  • Estimates are shown as total battle stats instead of a battle stat score.
  • Every Targets mode has the same toolbar: Filters, Refresh all, Auto-update and Fast.

Fixed

  • Players whose hospital time runs out move back into the table right away.

v0.1.0Released 2026-10-26

New

  • One Targets page with four modes: Chain, Levelling, Bounties and Revenge.
  • Fair fight and estimated stats on every player table.
  • War room: a shared enemy board, hit claims and Help pings for your faction.
  • A userscript that shows estimates and fair fight right on torn.com.
  • A welcome page, a goal-based start page and a quick tour for new players.
  • Keyboard shortcuts, Jump to (Ctrl K) and a compact dock view you can pop out.

Improved

  • Keep updated rechecks your targets for you, and your filters are remembered.
  • Choose accent colour, layout, a flat or glow style and whether things animate in Settings.

Fixed

  • Old links to Bounties, Revenge and the key page now land in the right place.

Disclaimer

  • Not official. TornHelper is a community tool made by a player. It is not affiliated with, endorsed by or sponsored by Torn City or Torn Ltd.
  • Estimates can be wrong. They come from fair fight values in attacks that players share, and can be out of date. Check a target and use your own judgement.
  • As is. There is no promise that it is correct or always available. You use it at your own risk.

Made by MrZixxel [3245851]

Found a bug or have an idea? Send MrZixxel a message in Torn.