Twitter ID 2024288437327843509 = December 15, 2024

Last updated March 22, 2026

About Twitter ID 2024288437327843509

This Twitter snowflake ID 2024288437327843509 was created on December 15, 2024 at 08:45:30 UTC. This could be a tweet ID, user ID, direct message, or any other Twitter object created at this exact moment.

How to Decode Twitter Snowflake ID 2024288437327843509

Twitter snowflake IDs encode the creation timestamp in the first 42 bits. To decode this ID: (2024288437327843509 >> 22) + 1288834974657 = 1734252330657 (Unix timestamp in milliseconds).

Common Searches for This ID

• decode twitter snowflake id 2024288437327843509
• twitter id 2024288437327843509 date
• 2024288437327843509 creation date
• what date is twitter id 2024288437327843509

Decoding the Timestamp

// JavaScript (BigInt required for 64-bit precision)
const id = 2024288437327843509n;
const twitterEpoch = 1288834974657n;

const timestampMs = (id >> 22n) + twitterEpoch;
const date = new Date(Number(timestampMs));

console.log("Date (UTC):", date.toUTCString());
console.log("ISO 8601:", date.toISOString());
console.log("Unix (ms):", timestampMs.toString());
console.log("Unix (s):", Math.floor(Number(timestampMs) / 1000));

# Python
id_val = 2024288437327843509
twitter_epoch_ms = 1288834974657

timestamp_ms = (id_val >> 22) + twitter_epoch_ms
timestamp_s = timestamp_ms / 1000

from datetime import datetime, timezone
dt = datetime.fromtimestamp(timestamp_s, tz=timezone.utc)
print(f"Date: {dt.strftime('%Y-%m-%d %H:%M:%S UTC')}")
print(f"ISO 8601: {dt.isoformat()}")
print(f"Unix (s): {timestamp_s:.3f}")

Snowflake Component Breakdown

// Extract all four Snowflake components
const id = 2024288437327843509n;
const twitterEpoch = 1288834974657n;

const timestamp  = (id >> 22n) + twitterEpoch;
const datacenter = (id >> 17n) & 0x1Fn;
const worker     = (id >> 12n) & 0x1Fn;
const sequence   = id & 0xFFFn;

console.log({
  date: new Date(Number(timestamp)).toISOString(),
  datacenterId: Number(datacenter),
  workerId: Number(worker),
  sequence: Number(sequence)
});

• 41-bit timestamp: milliseconds since Twitter's epoch (Nov 4, 2010)
• 5-bit datacenter ID: which data center generated this ID
• 5-bit worker ID: which server within the datacenter
• 12-bit sequence: up to 4096 IDs per millisecond per worker

Why BigInt Is Required in JavaScript

Twitter IDs exceed JavaScript's safe integer limit (2^53 - 1 = 9007199254740991). Using regular numbers causes precision loss:

// WRONG — precision loss
const id = 2024288437327843509; // JavaScript rounds this
console.log(id); // prints a different number

// CORRECT — use BigInt
const id = 2024288437327843509n;
console.log(id.toString()); // "2024288437327843509"

// When parsing from JSON, Twitter returns id_str for this reason
const tweet = JSON.parse('{"id_str": "2024288437327843509"}');
const safeid = BigInt(tweet.id_str);

Sequence Number Significance

The 12-bit sequence number in this ID indicates how many IDs were generated in the same millisecond by the same worker before this one. A sequence of 0 means this was the first ID generated in that millisecond. High sequence numbers indicate periods of very high activity on a specific server.

// Check if two IDs were generated in the same millisecond
function sameMillisecond(id1Str, id2Str) {
  const twitterEpoch = 1288834974657n;
  const id1 = BigInt(id1Str);
  const id2 = BigInt(id2Str);
  
  const ts1 = (id1 >> 22n) + twitterEpoch;
  const ts2 = (id2 >> 22n) + twitterEpoch;
  
  return ts1 === ts2;
}

// Check if two IDs were generated by the same worker
function sameWorker(id1Str, id2Str) {
  const id1 = BigInt(id1Str);
  const id2 = BigInt(id2Str);
  
  const worker1 = (id1 >> 12n) & 0x3FFn; // datacenter + worker
  const worker2 = (id2 >> 12n) & 0x3FFn;
  
  return worker1 === worker2;
}

Using This ID as an API Boundary

# Fetch tweets after this specific ID
import requests

headers = {"Authorization": "Bearer YOUR_BEARER_TOKEN"}
params = {
    "query": "your search terms",
    "since_id": "2024288437327843509",
    "max_results": 100,
    "tweet.fields": "created_at,author_id,text"
}

response = requests.get(
    "https://api.twitter.com/2/tweets/search/recent",
    headers=headers,
    params=params
)
data = response.json()
print(f"Found {len(data.get('data', []))} tweets")

Verifying the Decode

The Snowflake decode is deterministic — the same ID always produces the same timestamp. You can verify by:

• Running the JavaScript or Python examples above
• Using TechConverter.me's interactive Snowflake decoder
• Looking up the tweet or account with this ID on Twitter to confirm the creation date matches
• Comparing with adjacent IDs to confirm the timestamp progression is consistent

This specific ID, like all Twitter Snowflake IDs, encodes a precise millisecond timestamp that can be reliably extracted using the standard Snowflake decoding algorithm. The decoded date provides an objective, verifiable record of when this Twitter object was created.