Twitter ID 1800000000000000000 = July 10, 2024

Last updated March 22, 2026

About Twitter ID 1800000000000000000

This Twitter snowflake ID 1800000000000000000 was created on July 10, 2024 at 12:00:00 UTC. This is a commonly searched Twitter ID, often used as an example or reference point.

How to Decode Twitter ID 1800000000000000000

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

Common Searches for This ID

• twitter snowflake id 1800000000000000000 date
• twitter id 1800000000000000000
• tweet id 1800000000000000000 date
• what date is twitter id 1800000000000000000

Decoding the Timestamp

// JavaScript (BigInt required for 64-bit precision)
const id = 1800000000000000000n;
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):", (timestampMs / 1000n).toString());

# Python
id_val = 1800000000000000000
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"UTC: {dt.strftime('%Y-%m-%d %H:%M:%S UTC')}")
print(f"ISO 8601: {dt.isoformat()}")
print(f"Unix timestamp (s): {timestamp_s:.3f}")
print(f"Unix timestamp (ms): {timestamp_ms}")

Snowflake Component Breakdown

The 64-bit ID 1800000000000000000 breaks down into these Snowflake components:

• Bits 63–22 (41 bits): Milliseconds since Twitter's epoch (Nov 4, 2010 00:00:00 UTC)
• Bits 21–17 (5 bits): Datacenter ID (0–31)
• Bits 16–12 (5 bits): Worker ID (0–31)
• Bits 11–0 (12 bits): Sequence number (0–4095)

// Extract all components
const id = 1800000000000000000n;
const twitterEpoch = 1288834974657n;

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

console.log("Timestamp:", new Date(Number(timestamp)).toISOString());
console.log("Datacenter ID:", Number(datacenter));
console.log("Worker ID:", Number(worker));
console.log("Sequence:", Number(sequence));

Capacity of the Snowflake System

The Snowflake structure allows Twitter to generate IDs at massive scale:

• 41-bit timestamp: supports IDs until approximately year 2082
• 10-bit machine ID (datacenter + worker): up to 1024 simultaneous ID generators
• 12-bit sequence: up to 4096 IDs per millisecond per worker
• Total capacity: over 4 million unique IDs per millisecond across all workers

Using This ID for API Queries

Use ID 1800000000000000000 as a boundary for Twitter API queries to retrieve content from around this time period:

# Twitter API v2 — search tweets before this ID
import requests

headers = {"Authorization": "Bearer YOUR_BEARER_TOKEN"}

params = {
    "query": "your search query",
    "max_id": "1800000000000000000",
    "since_id": "1700000000000000000",
    "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()
for tweet in data.get("data", []):
    print(tweet["created_at"], tweet["text"][:80])

Building a Timeline of ID Milestones

Comparing multiple round-number IDs reveals the rate of Twitter activity over time:

// Build a timeline of ID milestones
const milestones = [
  { id: "1000000000000000000", label: "1 quintillion" },
  { id: "1500000000000000000", label: "1.5 quintillion" },
  { id: "1700000000000000000", label: "1.7 quintillion" },
  { id: "1800000000000000000", label: "1.8 quintillion" },
  { id: "1900000000000000000", label: "1.9 quintillion" },
  { id: "2000000000000000000", label: "2 quintillion" },
];

const twitterEpoch = 1288834974657n;

milestones.forEach(({ id, label }) => {
  const bigId = BigInt(id);
  const tsMs = (bigId >> 22n) + twitterEpoch;
  const date = new Date(Number(tsMs));
  console.log(`${label}: ${date.toDateString()}`);
});

Data Archiving Use Case

When archiving Twitter data, ID milestones serve as convenient partition boundaries:

# Partition tweets into time-based buckets using ID ranges
def partition_tweets_by_id(tweets):
    """
    Partition a list of tweet dicts into time buckets
    based on known ID milestones.
    """
    buckets = {
        "before_1700000000000000000": [],
        "1700000000000000000_to_1800000000000000000": [],
        "1800000000000000000_to_1900000000000000000": [],
        "after_1900000000000000000": [],
    }
    
    for tweet in tweets:
        tweet_id = int(tweet["id"])
        if tweet_id < 1700000000000000000:
            buckets["before_1700000000000000000"].append(tweet)
        elif tweet_id < 1800000000000000000:
            buckets["1700000000000000000_to_1800000000000000000"].append(tweet)
        elif tweet_id < 1900000000000000000:
            buckets["1800000000000000000_to_1900000000000000000"].append(tweet)
        else:
            buckets["after_1900000000000000000"].append(tweet)
    
    return buckets

Verifying the Decode

The Snowflake decode is fully deterministic. To verify:

• Run the JavaScript or Python examples above — they will always produce the same result
• Use TechConverter.me's interactive Snowflake decoder to confirm
• Cross-reference with tweets or accounts known to have been created around the decoded date

ID 1800000000000000000 is one of several round-number milestones that serve as useful anchors for Twitter data analysis. Knowing the corresponding date allows efficient API queries, dataset partitioning, and historical analysis of Twitter activity.