Twitter Snowflake Decoder - Find Exact Tweet Timestamp

Last updated March 22, 2026

Tweet Timestamp Finder Examples

The Tweet Timestamp Finder decodes the exact creation date and time from any tweet ID. Below are examples of timestamp extractions and their applications.

Single Tweet Timestamp

Tweet ID: 1529877576591609861

Results:
  UTC time:       May 26, 2022 at 18:45:32.000 UTC
  Your timezone:  May 26, 2022 at 2:45:32 PM EDT (UTC-4)
  Unix timestamp: 1653590732000 (milliseconds)
  ISO 8601:       2022-05-26T18:45:32.000Z
  Relative:       About 3 years ago

Twitter epoch used: November 4, 2010 at 01:42:54 UTC (1288834974657 ms)

Multiple Tweet IDs — Timeline Reconstruction

Analyzing a Twitter thread:

Tweet 1: 1700000000000000000 → Sep 9, 2023 12:34:56 UTC
Tweet 2: 1700000100000000000 → Sep 9, 2023 12:35:02 UTC  (+6 seconds)
Tweet 3: 1700000200000000000 → Sep 9, 2023 12:35:08 UTC  (+6 seconds)
Tweet 4: 1700000300000000000 → Sep 9, 2023 12:35:14 UTC  (+6 seconds)

Observation: Tweets posted every 6 seconds — possible automated posting

Fact-Checking Timeline

Claim: "This tweet was posted before the event happened"

Event time:  March 15, 2024 at 10:00 UTC
Tweet ID:    1800000000000000000

Decoded tweet time: March 15, 2024 at 08:22 UTC

Conclusion: Tweet was posted 1 hour 38 minutes BEFORE the event.
            The claim is VERIFIED.

Decoding Process (Transparent)

Tweet ID: 1529877576591609861

Binary representation:
  0001010100111001001001001001001001001001001001001001001001001001

Timestamp bits (first 41):
  10101001110010010010010010010010010010010

Decimal value: 364755757343 milliseconds

Add Twitter epoch (1288834974657 ms):
  364755757343 + 1288834974657 = 1653590732000 ms

Convert to date:
  1653590732000 ms ÷ 1000 = 1653590732 seconds
  = May 26, 2022 18:45:32 UTC ✓

Pre-Snowflake vs Snowflake IDs

Pre-Snowflake (before 2010):
  Tweet ID: 12345678
  Note: Sequential ID — no embedded timestamp
  Estimated date: Based on known ID-to-date mappings from Twitter's early era

Snowflake (2010 onwards):
  Tweet ID: 1382350606417817604
  Decoded: April 14, 2021 16:30:00.123 UTC ✓ (millisecond precision)

Research Application — Viral Event Analysis

Analyzing tweet IDs from a viral hashtag:

First tweet:  1700000000000000000 → Sep 9, 2023 12:34 UTC
Peak activity: Sep 9, 2023 14:00–16:00 UTC (highest ID density)
Last tweet:   1700500000000000000 → Sep 9, 2023 18:22 UTC

Total duration: ~5 hours 48 minutes
Peak spread:    2-hour window in the afternoon

Common Use Cases

• Finding the exact time a tweet was posted
• Verifying tweet timestamps for journalistic investigations
• Reconstructing event timelines from tweet IDs
• Detecting automated posting patterns (regular intervals)
• Academic research on information spread timing
• Checking if a tweet predates or postdates a specific event
• Processing Twitter data archives without additional API calls

Enter any tweet ID or paste a tweet URL to instantly decode the creation timestamp in UTC, your local timezone, Unix format, and ISO 8601.

const TWITTER_EPOCH = 1288834974657;
const tweetId = 1382350606417817604n;
const timestamp = (tweetId >> 22n) + BigInt(TWITTER_EPOCH);
const date = new Date(Number(timestamp));

console.log(date.toISOString()); // 2021-04-14T15:30:06.657Z

Where 1288834974657 is Twitter's epoch in Unix milliseconds. The >> operator right-shifts the ID by 22 bits to extract the timestamp portion.

Why Twitter Uses Snowflake IDs

Twitter developed snowflake IDs in 2010 to solve the challenge of generating unique identifiers at massive scale. Benefits include:

• Time-Ordered: Tweets are naturally sorted by post time
• Globally Unique: No two tweets will ever have the same ID
• Distributed Generation: Multiple servers can generate IDs without coordination
• Compact: 64-bit IDs are efficient for storage and URLs
• Embedded Metadata: Timestamp is built into the ID itself

Historical Context

Before November 4, 2010, Twitter used sequential integer IDs. These older tweets don't have embedded timestamps and can't be decoded with this tool. The switch to snowflake IDs was necessary as Twitter scaled to handle billions of tweets.

Frequently Asked Questions

Can I find timestamps for deleted tweets?

Yes, if you have the tweet ID or URL saved. The timestamp is encoded in the ID itself, so even if the tweet is deleted, you can still decode when it was originally posted.

Do retweets have different timestamps?

Yes! Retweets get their own unique ID with a timestamp of when the retweet happened, not when the original tweet was posted.

Are tweet timestamps accurate?

Yes, timestamps are accurate to the millisecond. They represent the exact moment Twitter's servers created the tweet ID.

Can I decode timestamps from private accounts?

Yes, as long as you have access to see the tweet and can copy its URL or ID. The timestamp is part of the ID structure itself.

What's the oldest tweet I can decode?

You can decode any tweet posted after November 4, 2010, when Twitter launched snowflake IDs. Tweets before this date use sequential IDs without embedded timestamps.