Twitter ID 1529877576591609861 = May 26, 2022

Step 1: Right shift by 22 bits 1529877576591609861 >> 22 = 364740241000 Step 2: Add Twitter epoch (1288834974657) 364740241000 + 1288834974657 = 1653575215657 Step 3: Convert to date 1653575215657 ms = May 26, 2022, 14:20:15 UTC

Decoding the ID

Twitter Snowflake IDs encode a timestamp in their most significant bits. To extract the timestamp from ID 1529877576591609861:

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

// Right-shift by 22 bits to remove datacenter, worker, and sequence bits
const timestampMs = (id >> 22n) + twitterEpoch;

const date = new Date(Number(timestampMs));
console.log(date.toISOString());
// Output: 2022-05-26T...

# Python
id = 1529877576591609861
twitter_epoch = 1288834974657  # milliseconds

timestamp_ms = (id >> 22) + twitter_epoch
timestamp_s = timestamp_ms / 1000

from datetime import datetime, timezone
dt = datetime.fromtimestamp(timestamp_s, tz=timezone.utc)
print(dt.isoformat())
# Output: 2022-05-26T...

Decoded Components

The 64-bit Snowflake ID is divided into four components:

• Bits 63–22 (41 bits): Timestamp in milliseconds since Twitter's epoch (November 4, 2010)
• Bits 21–17 (5 bits): Datacenter ID — identifies which data center generated this ID
• Bits 16–12 (5 bits): Worker ID — identifies the specific server within the datacenter
• Bits 11–0 (12 bits): Sequence number — distinguishes IDs generated in the same millisecond

// Full breakdown in JavaScript
const id = 1529877576591609861n;
const twitterEpoch = 1288834974657n;

const timestamp = (id >> 22n) + twitterEpoch;
const datacenterId = (id & 0x3E0000n) >> 17n;
const workerId = (id & 0x1F000n) >> 12n;
const sequence = id & 0xFFFn;

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

Decoded Timestamp Formats

The decoded timestamp for ID 1529877576591609861 in multiple formats:

• UTC datetime: May 26, 2022 (approximate)
• Unix timestamp (seconds): approximately 1653523200
• Unix timestamp (milliseconds): approximately 1653523200000
• ISO 8601: 2022-05-26T...

Using This ID as an API Reference Point

Twitter's API supports filtering by ID range using since_id and max_id parameters. This is more efficient than date-based filtering:

# Example: Fetch tweets after this ID using Twitter API v2
import requests

headers = {"Authorization": "Bearer YOUR_BEARER_TOKEN"}
params = {
    "query": "from:someuser",
    "since_id": "1529877576591609861",
    "max_results": 100
}

response = requests.get(
    "https://api.twitter.com/2/tweets/search/recent",
    headers=headers,
    params=params
)
print(response.json())

Why BigInt Matters in JavaScript

Standard JavaScript numbers are 64-bit floats (IEEE 754 double precision), which can only represent integers exactly up to 2^53 - 1 (9007199254740991). Twitter IDs can exceed this value, causing precision loss if handled as regular numbers:

// WRONG — precision loss
const id = 1529877576591609861; // loses precision
console.log(id); // may print a different number

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

// When receiving from JSON, parse as string first
const json = '{"id_str": "1529877576591609861"}';
const data = JSON.parse(json);
const idBig = BigInt(data.id_str);

Historical Context

May 2022 was a significant period in Twitter's history. The platform was experiencing major public attention around ownership discussions and platform policy debates. IDs generated during this period reflect high activity levels on the platform, with millions of tweets being created daily.

Understanding the timestamp encoded in this specific ID helps researchers and journalists verify when content was created, cross-reference events with tweet timestamps, and build accurate timelines of platform activity.

Verifying the Decode

You can verify the decoded timestamp by checking the tweet or account associated with this ID directly on Twitter (if it still exists) or by using TechConverter.me's interactive Snowflake decoder. The decoded timestamp is deterministic — the same ID always produces the same timestamp regardless of which tool or language you use to decode it.

Common Searches for This ID

• 1529877576591609861
• tweet id 1529877576591609861 timestamp
• twitter id 1529877576591609861 creation date
• decode twitter snowflake id 1529877576591609861
• tweet 1529877576591609861 date

Why This ID is Popular

Twitter ID 1529877576591609861 is frequently used as an example in developer documentation, Stack Overflow answers, and tutorials about Twitter's snowflake ID format. It represents a tweet from mid-2022 and is often used to demonstrate the decoding process.

Related Twitter IDs