X (Twitter) Account Country & Location Scraper

Get the country an X account is based in: the exact "Account based in" field X shows in its About panel. Plus signup source (App Store country vs Web), verified badge type, affiliate organization, join date, and how many times the handle has been renamed.

🌍 What you get

X's internal "About this account" data, per handle:

• Account based in: country name X shows on the profile's About panel, plus a clean ISO 3166-1 alpha-2 code (United States → US).
• Connected via: device / store the account was most recently active on. Web, <Country> App Store, or <Country> Android App. Useful for identifying which country / platform the account operates from.
• Verified status: Blue, Business, Government badges + the reason X shows + since date.
• Affiliate: parent organization the account is affiliated with (e.g. employees → their employer).
• Rename count: join date + number of times the handle has been renamed + date of the most recent rename (previous handle strings not exposed by X).

Not a self-typed profile string. X's own determination.

📋 How to use it

Step 1: Add targets

Drop in any mix of:

• Handles: nike, elonmusk, @openai. One per line.
• Numeric user IDs: 44196397, 1339835893. Survives handle changes. Resolved to the current handle before lookup.
• Full profile URLs: https://x.com/nike. Bare profile URLs only.

Mix all three in one run. Duplicates across fields are deduped for free.

Step 2: Run and export

Click Start. Rows stream into the Output tab as they scrape. Export from the Output tab as JSON, CSV, or Excel, or pull the dataset over the Apify API.

Optional: turn off any fields you don't need in the 📤 Output fields section to keep rows lean. Off means the field is omitted entirely (not null).

Every row carries a status field. Success = country resolved. no_location = About panel returned but has no country (usually gov / political accounts, not billed). not_found = handle does not exist. error = temporary lookup failure. Retry the run.

💰 Pricing

Pay per row. Filtered, missing, and failed rows are always free.

Event	Per 1,000
Account located	$2.00

💡 Good to know

• Two location fields. account_based_in = X's determined country. connected_via = the country / platform of the most recent device the account connected from. They can differ, e.g. a Danish account whose owner recently used the US App Store returns Denmark + United States App Store.
• Regional buckets. X sometimes returns a multi-country region (Europe, East Asia, North America, West Asia) instead of a country. account_based_in_is_region is true on those rows and account_based_in_iso is null (no single ISO for a region).
• Web signups have no country. connected_via = Web means browser signup, no country signal. connected_via_iso stays null.
• Field toggles. Every output field has its own on/off switch to keep rows lean.
• Cross-input dedup. The same account arriving via handle + user ID + URL in the same run is charged once.

❓ FAQ

How is account_based_in different from a user's self-typed profile location?

X computes account_based_in internally from signup metadata + activity signals. It's on the "About this account" panel, not on the profile header. The free-text self-typed location field is not returned by this actor.

Why is account_based_in_iso null on some rows?

Two reasons. Either X returned a regional bucket (Europe, East Asia, ...), in which case those rows have account_based_in_is_region: true. Or the country name is not yet in the ISO mapping table (a bug candidate to flag).

Why is status: no_location on some rows?

X hides the About panel country for some high-profile government, political, or diplomatic accounts. The row still returns identity data (verified status, affiliate, date joined) but not country. These rows are not billed.

Can I get the free-text location field a user typed?

No. This actor targets the X-determined country only. For self-typed location, use X Profile Scraper.

Do I need X cookies or an API key?

No. This actor works without any authentication.

Can I scrape a private / protected / suspended account?

No. If X hides it, no scraper can see it. The row will come back as not_found.

How do I export to Google Sheets / Excel / a CRM?

From the run's Output tab, hit Export → CSV, Excel, JSON, or HTML. Or pull via the Apify API.

How long are results kept?

Rows live in your Apify account. Retention depends on your Apify plan.

🔗 Other tools you might like

• X.com (Twitter) Profile Scraper: tweets from any X profile with filters.
• X.com (Twitter) Follower Scraper: followers, following, verified followers, plus optional email extraction.
• X.com (Twitter) Tweet Scraper: any tweet by URL, ID, or search query.
• X.com (Twitter) Tweet Replies Scraper: full reply tree from any tweet URL.

⚖️ Legal disclaimer & terms of use

Purpose. Intended for research, journalism, OSINT, market analysis, and educational use. The tool extracts data X itself publishes in its own "About this account" panel. The developer does not host, store, or possess any data you extract with this tool.

Personal data. Country / location information about identifiable individual accounts is Personally Identifiable Information under GDPR, CCPA, and similar frameworks. By running this Actor you become the Data Controller for anything you collect. If you process data belonging to EU / UK / California / other regulated data subjects, you are responsible for the notification, purpose-limitation, retention, and opt-out obligations those laws impose (e.g. GDPR Article 14 notice within 30 days).

User liability. You assume 100% responsibility for compliance with X's Terms of Service and every applicable law in your jurisdiction and the jurisdiction of the accounts you target. The developer assumes zero liability for platform blocks, account bans, regulatory fines, or legal actions resulting from your use of this software.

No warranty. Software provided "as-is" without warranties of any kind. Country / verification / affiliate data reflects what X displayed at scrape time and can change without notice. You agree to hold the developer harmless from any damages or losses incurred.

Keywords: x location scraper, twitter location scraper, account based in, twitter country lookup, x profile country, twitter geolocation, account country api, twitter user country, x connected via, twitter verified badge, twitter affiliate lookup