X (Twitter) Β· Free Β· No sign-up
X (Twitter) Account Age Checker
Paste any X / Twitter numeric user ID and we decode the exact account creation date from the ID itself. Pure math β no API, no login, nothing leaves your browser.
Paste the numeric X / Twitter user ID. @handles cannot be decoded offline.
π Never enter passwords, tokens, emails or any private information. This tool only uses public usernames or IDs.
How it works
- 1 Β· Find the numeric user IDX handles like @jack don't contain a date. You need the numeric user ID, which you can grab from tweeterid.com, the X API, or by inspecting the page source. Old accounts (pre-Nov 2010) have legacy IDs that don't encode a timestamp.
- 2 Β· Paste it hereDrop the long number into the box above. The checker accepts up to 20 digits and rejects anything that doesn't decode to a realistic date.
- 3 Β· See the creation dateThe timestamp is decoded from the upper 41 bits of the snowflake using Twitter's epoch of 2010-11-04 01:42:54.657 UTC. Works for deleted, suspended, or renamed accounts.
Why check an X (Twitter) account's age?
Account age is the single best low-cost signal for spotting throwaway accounts, mass-registered bot farms, and impersonators on X. Researchers use it to date when a viral account was actually created (rather than trusting the visible 'Joined' label, which X has occasionally lagged). Brands use it to vet engagement quality before paying for promoted tweets. Moderators use it to spot evasion accounts. Because the date is encoded in the ID itself, the result is verifiable and doesn't depend on X's paid API.
How does the X snowflake ID reveal the creation date?
Starting November 4, 2010, Twitter switched to 64-bit 'snowflake' IDs. The top 41 bits store the number of milliseconds since Twitter's custom epoch (1288834974657 in Unix milliseconds). This checker right-shifts the ID by 22 bits, adds the epoch, and converts to a normal Date. Accuracy is to the millisecond. The same math works for tweet IDs, list IDs, and direct message IDs.
Limitations and honesty about this tool
Snowflake decoding works perfectly for any account created from November 2010 onward. Accounts older than that have legacy sequential IDs and we cannot decode a creation date from those β we'll tell you instead of guessing. We also require the numeric user ID rather than the @handle, because X's public web no longer exposes a handle-to-ID lookup without authentication. Most other 'X age checker' tools that accept handles are either calling the paid X API behind the scenes (and may break when their key runs out) or fabricating dates from cached data.
Frequently asked questions
Can I check an X account age by @handle?
Not directly with this tool. X removed the public unauthenticated user lookup endpoint in 2023, so any handle-to-date lookup now requires a paid X API key. We accept the numeric user ID instead, which you can grab from a free third-party converter like tweeterid.com.
Is this safe to use? Does it touch the X API?
Yes, it's safe and it does NOT touch the X API. The decode happens entirely in your browser using public, well-documented math on the user ID. Nothing is sent to a server and nothing is stored.
Does it work for deleted, suspended, or banned X accounts?
Yes. Because the creation date is encoded in the user ID itself, the date is decodable even if the account is gone β as long as you still have the numeric ID from before deletion.
Why doesn't it work for very old Twitter accounts?
Twitter only switched to snowflake IDs on November 4, 2010. Accounts created before that date have small sequential IDs (usually under 250 million) that don't contain a timestamp. We refuse to guess and will return an error instead.
Does the same trick work for tweet IDs?
Yes. All snowflake IDs on X β tweets, users, lists, DMs β use the same format. Paste any modern tweet ID and you'll get the timestamp of when that tweet was posted.
How accurate is the decoded date?
Exact to the millisecond. The timestamp comes straight from the ID that X assigned at creation time. The only edge case is the ~5 millisecond drift between an account being registered and the ID being minted, which is negligible for any human use case.