X Engagement Insights

What time should you post on X?

No single hour of the day produces a measurable engagement advantage in this dataset. Posting hour is a far weaker lever than post format, and the full hourly table below shows why.

Key findings

  • Posts published in the 06:00 UTC hour earned 5.2% below the engagement of the same accounts' other posts (95% interval -6.2% to -4.0%), measured across 16,940 X accounts and 85,609 of their posts in the 30 days to 9 October 2026. The effect held for 9,106 of those 16,940 accounts individually.
  • 3 of the 24 hours of the day show no measurable engagement difference at all, measured across 31,125 X accounts and 2,918,544 of their posts in the 30 days to 9 October 2026, so posting hour is a much weaker lever than it is usually described as.
  • More posting hours measurably underperform (21) than measurably outperform (0), which makes avoiding the weak hours a more reliable tactic than chasing the strong ones.

Engagement by hour of the day, all 24 hours

The complete table, in clock order rather than ranked. Publishing only the top five hours would make the effect look far stronger and far more reliable than it is; the rows marked as having no measurable difference are the most important thing here.

Median engagement by hour of publication (UTC), 2,918,544 original X posts
Hour published (UTC)Effect (95% interval)Accounts comparedPosts
00:00 UTCNo measurable difference-2.4% to -0.0%, spans zero17,05988,974
01:00 UTC-2.0%-3.3% to -0.9%17,3318,877 agree89,757
02:00 UTC-3.2%-4.4% to -2.2%17,0248,873 agree87,746
03:00 UTC-3.6%-4.7% to -2.4%17,7489,282 agree94,204
04:00 UTC-5.2%-6.1% to -4.0%15,2928,188 agree75,662
05:00 UTC-4.1%-5.3% to -3.0%15,0917,998 agree74,863
06:00 UTC-5.2%-6.2% to -4.0%16,9409,106 agree85,609
07:00 UTC-4.8%-5.8% to -3.8%18,3189,861 agree93,035
08:00 UTC-3.5%-4.5% to -2.7%20,52710,830 agree108,010
09:00 UTC-3.5%-4.3% to -2.6%22,58811,912 agree124,304
10:00 UTC-2.9%-3.5% to -2.0%23,72812,402 agree129,073
11:00 UTC-2.7%-3.6% to -1.9%25,77813,415 agree140,826
12:00 UTC-2.5%-3.3% to -1.7%27,82214,427 agree153,702
13:00 UTC-2.9%-3.6% to -2.1%30,14715,729 agree166,699
14:00 UTC-3.8%-4.5% to -3.0%30,75516,252 agree172,845
15:00 UTC-2.1%-2.9% to -1.3%31,12516,033 agree176,291
16:00 UTC-3.1%-3.9% to -2.3%29,64015,481 agree170,811
17:00 UTC-3.2%-3.9% to -2.3%28,10214,663 agree158,650
18:00 UTC-1.9%-2.9% to -1.0%26,28713,467 agree148,930
19:00 UTC-2.3%-3.2% to -1.5%24,92612,895 agree141,044
20:00 UTC-1.2%-2.2% to -0.3%23,02511,705 agree131,352
21:00 UTCNo measurable difference-1.5% to +0.5%, spans zero21,159115,843
22:00 UTC-1.6%-2.7% to -0.4%19,1359,758 agree100,076
23:00 UTCNo measurable difference-2.4% to -0.0%, spans zero17,68190,238

A row is only reported as a finding when its 95% interval stays on one side of zero and at least 30 independent accounts contributed a comparison. Measured over the 30 days to 9 October 2026.

What are those hours in local time?

Only the hours that differ measurably are worth converting. Times are computed for today, so daylight saving is already applied.

Hours with a measurable effect, converted to local time
UTCEffectNew YorkLos AngelesLondonMumbaiTokyo
20:00 UTC-1.2%16:0013:0021:0001:30 (next day)05:00 (next day)
22:00 UTC-1.6%18:0015:0023:0003:30 (next day)07:00 (next day)
18:00 UTC-1.9%14:0011:0019:0023:3003:00 (next day)
01:00 UTC-2.0%21:00 (prev day)18:00 (prev day)02:0006:3010:00
15:00 UTC-2.1%11:0008:0016:0020:3000:00 (next day)
19:00 UTC-2.3%15:0012:0020:0000:30 (next day)04:00 (next day)
12:00 UTC-2.5%08:0005:0013:0017:3021:00
11:00 UTC-2.7%07:0004:0012:0016:3020:00
13:00 UTC-2.9%09:0006:0014:0018:3022:00
10:00 UTC-2.9%06:0003:0011:0015:3019:00
16:00 UTC-3.1%12:0009:0017:0021:3001:00 (next day)
17:00 UTC-3.2%13:0010:0018:0022:3002:00 (next day)
02:00 UTC-3.2%22:00 (prev day)19:00 (prev day)03:0007:3011:00
08:00 UTC-3.5%04:0001:0009:0013:3017:00
09:00 UTC-3.5%05:0002:0010:0014:3018:00
03:00 UTC-3.6%23:00 (prev day)20:00 (prev day)04:0008:3012:00
14:00 UTC-3.8%10:0007:0015:0019:3023:00
05:00 UTC-4.1%01:0022:00 (prev day)06:0010:3014:00
07:00 UTC-4.8%03:0000:0008:0012:3016:00
04:00 UTC-5.2%00:0021:00 (prev day)05:0009:3013:00
06:00 UTC-5.2%02:0023:00 (prev day)07:0011:3015:00

Converted with the current daylight-saving rules for each city, so these labels shift by an hour twice a year while the UTC column never moves.

Is the day of the week a stronger signal than the hour?

On this dataset, yes, and by some distance. The largest hourly effect is smaller than the largest daily one, and the day-of-week table has a single clear loser rather than a spread of near-flat rows. That comparison is set out in full on the best day to post. If you are choosing where to spend effort, format decisions still beat both: outbound links move engagement further than any hour of the day measured here.

Frequently asked questions

What is the best time to post on X (Twitter)?
In this dataset no single hour of the day produces a measurable engagement advantage. Posting hour is a much weaker lever than post format.
What is the worst time to post on X?
Posts published in the 06:00 UTC hour earned 5.2% below the engagement of the same accounts' other posts (95% interval -6.2% to -4.0%), measured across 16,940 X accounts and 85,609 of their posts in the 30 days to 9 October 2026. The effect held for 9,106 of those 16,940 accounts individually. Avoiding the weakest hours is a more dependable tactic than targeting the strongest, because the negative effects in this dataset are larger than the positive ones.
Are these times in my local time zone?
No. Every hour on this page is UTC, because that is the only time zone the underlying post timestamps share. A conversion table for five major cities is included above, computed for today so daylight saving is already accounted for.
Does posting time matter as much as people say?
Not on this evidence. Across 31,125 X accounts and 2,918,544 of their posts in the 30 days to 9 October 2026, 3 of the 24 hourly buckets have a 95% interval that spans zero, meaning no difference can be stated for them at all. Format decisions measured on the same posts move engagement several times further than the hour of publication does.
Why compare each account only against itself?
A raw comparison of interaction counts by hour would mostly show which hours large accounts prefer. Comparing each account's posts in one hour against that same account's posts in every other hour, over the same 30-day window, removes account size from the comparison and leaves the timing effect on its own. It also makes the account the unit of evidence, which is what allows a confidence interval to be computed at all.

How this was measured

Method
Public posts are collected per account and replies and reposts are discarded. Within each account, the median engagement of the posts in a bucket is compared against the median engagement of that same account's posts outside it, producing one ratio per account. The reported effect is the median of those per-account ratios, with a distribution-free 95% interval around it. Account size therefore cancels out instead of being re-measured, and the unit of evidence is the account rather than the post, because posts inside one account are not independent observations of how the platform behaves.
What an effect percentage means
An effect of +10% means the typical measured account earned 10% more engagement on posts in that bucket than on its own posts outside it. The interval beside it is a 95% confidence interval on that figure; where the interval spans zero the page reports no measurable difference rather than a small effect. It is not a click-through rate and not a guarantee for any individual account.
Sample and window
262,513 X accounts carry an engagement aggregate, built from 11,798,994 collected posts. Every aggregate covers a trailing 30-day window, last recomputed on 9 October 2026. Interaction counts are read at collection time and reflect that moment, not a live figure.
How uncertainty is handled
Every effect carries a distribution-free 95% confidence interval and the number of independent accounts behind it. A result is only stated as a finding when that interval stays entirely on one side of zero; where it spans zero the page says no measurable difference rather than printing a small number that would get quoted without its caveat. Accounts are the unit of evidence, not posts: several thousand posts from one account are one observation of how the platform behaves, not several thousand.
What we do not claim
These are observational differences, not a controlled experiment. A format that correlates with higher engagement here has not been shown to cause it: posts that carry a link, or an image, or a hashtag also differ in what they are about, and this data cannot separate the format from the content. A flat result means the interval spans zero, not that the true effect is exactly nothing.
How the hour is assigned
Each post is bucketed by the UTC hour of its publication timestamp as reported by the platform. No local-time inference is attempted, because the audience location of a post is not observable from public data and guessing it would push a made-up variable into a real measurement.

Cite this page

The aggregate findings on this page are published under CC BY 4.0. You may reuse them anywhere, including in AI-generated answers, provided the source is named. The licence covers the derived statistics only, not the underlying post text, which is not redistributed.

PlayerSells. "What time should you post on X?." PlayerSells X Engagement Insights. Data measured 9 October 2026. https://playersells.com/insights/best-time-to-post

Machine-readable findings (JSON)Methodology

The full dataset index lives at https://playersells.com/insights.