Kelly Sommers engagement report
@kellabyte - 53K followers on X
Measured over 30 original posts from a 30-day window, last computed on October 15, 2026.
Engagement
A typical post picks up 194 interactions against 53K followers, an engagement rate of 0.366%. Measured over 30 original posts, its engagement rate beats 69% of 20,445 tracked accounts of a similar size, which puts it in the middle of its size range rather than at either end. Posts are seen about 12K times each, and 1.60% of those impressions turn into an interaction. That is about 22.8% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 2.4 posts a day over the last 30 days, with activity on roughly 60% of days. Most posts go out around 17:00 UTC, and Wednesday is the busiest day of the week. Of the 30 posts sampled, 30% carry an image or video, 7% are part of a thread and 7% link out. The account's strongest tracked post pulled 3.7K interactions, about 19x its own typical post.
Measured over 30 original posts from a 30-day window, last computed on October 15, 2026. Recurring tag: #re2026capcom.
Compared with accounts its own size
Kelly Sommers's engagement rate beats 69% of the tracked X accounts closest to it in follower count (20,445 accounts, accounts of similar size (decile 5 of 10)). A percentile is spread evenly by construction, so 50 really is the middle of that group and 90 really is its top tenth.
On engagement per impression rather than per follower it beats 51% of the same group. When those two numbers disagree, the gap is about how far its posts travel rather than how people react to them.
Where this sits in the catalog
At 0.366%, Kelly Sommers sits above the 50th percentile of the 205,374 accounts in this comparison. That places it in the above the median band, which runs 0.143% to 0.678%.
Show the percentile table
| Percentile | Engagement rate |
|---|---|
| 10th percentile | 0.004% |
| 25th percentile | 0.024% |
| 50th percentile | 0.143% |
| 75th percentile | 0.678% |
| 90th percentile | 2.55% |
| 99th percentile | 82.4% |
This ruler is the whole measured catalog, not a size-matched group: it shows where the raw rate falls across every account we can measure, all of which are large. For a like-for-like comparison, read the size-band percentile above instead. See how the bands are built
Posting timing
This account posts most often around 17:00 UTC, and Wednesday is its busiest day of the week. The bars below are the catalog-wide pattern, with this account's own busiest slot marked. They do not show how this account performs at each hour: we keep one aggregate per account, not one per hour, so that measurement does not exist in our data.
Show engagement by hour posted, utc as a table
| Hour (UTC) | Vs author median | Posts |
|---|---|---|
| 00:00 UTC | -1% | 89K |
| 01:00 UTC | -2% | 90K |
| 02:00 UTC | -3% | 88K |
| 03:00 UTC | -4% | 94K |
| 04:00 UTC | -5% | 76K |
| 05:00 UTC | -4% | 75K |
| 06:00 UTC | -5% | 86K |
| 07:00 UTC | -5% | 93K |
| 08:00 UTC | -4% | 108K |
| 09:00 UTC | -4% | 124K |
| 10:00 UTC | -3% | 129K |
| 11:00 UTC | -3% | 141K |
| 12:00 UTC | -3% | 154K |
| 13:00 UTC | -3% | 167K |
| 14:00 UTC | -4% | 173K |
| 15:00 UTC | -2% | 176K |
| 16:00 UTC | -3% | 171K |
| 17:00 UTC | -3% | 159K |
| 18:00 UTC | -2% | 149K |
| 19:00 UTC | -2% | 141K |
| 20:00 UTC | -1% | 131K |
| 21:00 UTC | 0% | 116K |
| 22:00 UTC | -2% | 100K |
| 23:00 UTC | -1% | 90K |
Show engagement by day of week as a table
| Day | Vs author median | Posts |
|---|---|---|
| Sunday | +5% | 393K |
| Monday | +1% | 483K |
| Tuesday | -2% | 520K |
| Wednesday | -3% | 472K |
| Thursday | -2% | 430K |
| Friday | -3% | 447K |
| Saturday | +2% | 393K |
Formats this account uses
Its own posting mix on the left, and what each of those formats does across every account we track on the right. Only formats where the effect clears our publish test appear here, so an empty row is a format we could not measure rather than one that does nothing.
| Format | This account | Catalog effect | 95% interval | Accounts behind it |
|---|---|---|---|---|
| Image or video | 30% of posts | +111% | +108% to +115% | 34K |
| Outbound link | 7% of posts | -41% | -42% to -40% | 32K |
| Typical length | - | -3% | -3% to -2% | 54K |
- 30% of this account's sampled posts carry an image or video. Across the catalog, posts with an image or video run 111% above the same accounts' other posts.
- 7% of its posts carry a link off X. Across the catalog, posts with an outbound link run 41% below the same accounts' other posts.
- Its average post runs 170 characters, which falls in the 80 - 180 characters band. Across the catalog, posts of 80 to 180 characters run 3% below the same accounts' other posts.
These are catalog-wide differences applied to this account's own posting mix, not a measurement of how each format performs for this account specifically. We keep one median per account, not one per format per account, so the second thing is not something this data can tell you.
Best tweets
- Sep 29, 202619x their median
You hate dhh because of his agentic coding takes of 2026. I dismiss dhhās technical opinions since ~2007 when he said a SQL database is just a big hashtable. We are not the same.
- Oct 5, 202611x their median
I am not touching the operating system built from someone who cares so little and is proving to be the worst programmer Iāve ever seen.
- Oct 7, 20265.1x their median
Rails founders code has perf issues š I halved median response time in 5mins AI Go & Rust ports fix slow code written by Rails founders Rails uses Redis over TCP Go/Rust ports use in proc cache Iāve spent more time in the code than them. I give up. Code & benchmarks are trash
- Oct 6, 20264.3x their median
āI didnāt do it, AI didā is the biggest cope and laziest excuse of all time.
- Oct 6, 20264.0x their median
Guess what? His benchmark client code is dog shit too. You canāt trust the ports or the benchmark clients. What a shit show š Remember folks: It has to be real ā It has be competent ā It has to be responsible ā All he did was 2025 like naive one shots+making YOU fix it https://t.co/5e3CMhOb2S
- Sep 29, 20263.0x their median
Itās NOT a hot take that we will be reviewing less code soon But today you shouldnāt follow loud voices who have been full sending some of the worst code weāve ever seen Stick with Ruby or any language for that matter if your team is executing Use AI to elevate your weaknesses
- Sep 26, 20263.0x their median
Why donāt OSS projects post specs and prompts for work they want done? I have 3 token resets that expire in 5 days. Thatās a lot of compute I could donate.
- Sep 30, 20262.1x their median
Iāve been critical of the most embarrassing users of AI today & how careless they are being & just making other humans deal with it Soon I will blog about how I operate with current AI tools & how I stay on top of important things while accelerating. You donāt have to be shit!
- Oct 7, 20262.0x their median
The main reason he got bamboozled by AI is because his prompt was so bad and he takes a strict stance of not reading code or asking AI basic questions. Iāve seen people use AI for one shots way more difficult than this. Heās about a year behind on how to talk to AI.
- Oct 5, 20261.8x their median
Maybe donāt follow lead of loud voices putting all reads behind a single global lock publishing benchmarks Thatās how bad their code is They arenāt even trying to make code that works well or they donāt care or they are this bad at programming Either way, listen to smarter ppl
Ranked by total interactions across everything we have tracked for this account, which is a longer history than the 30-day window the rates above use. The multiple compares each post to this account's own median.
Recurring topics
The most frequent hashtags in the sampled posts. They describe what this account writes about; they are not a performance signal, and the catalog-wide breakdown on the hub shows how little hashtag count moves.
Buy or sell Twitter (X) accounts - escrow-protected
PlayerSells is an escrow marketplace for Twitter (X) accounts. Every deal is protected, with no middleman risk.
Reading these numbers
A typical post picks up 194 interactions against 53K followers, an engagement rate of 0.366%. Measured over 30 original posts, its engagement rate beats 69% of 20,445 tracked accounts of a similar size, which puts it in the middle of its size range rather than at either end. Posts are seen about 12K times each, and 1.60% of those impressions turn into an interaction. That is about 22.8% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 2.4 posts a day over the last 30 days, with activity on roughly 60% of days. Most posts go out around 17:00 UTC, and Wednesday is the busiest day of the week. Of the 30 posts sampled, 30% carry an image or video, 7% are part of a thread and 7% link out. The account's strongest tracked post pulled 3.7K interactions, about 19x its own typical post.
- What is Kelly Sommers's engagement rate on X?
- Kelly Sommers (@kellabyte) has an engagement rate of 0.366%, based on the median interactions across 30 original posts from the last 30 days against 53,035 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
- Is that a good engagement rate?
- At 0.366%, Kelly Sommers sits above the 50th percentile of the 205,374 accounts in this comparison. Those comparison accounts are all large ones, because our scanning cadence is weighted towards big accounts, so this is a ranking among peers of similar scale rather than a ranking across X.
- Does @kellabyte have real engagement?
- Its engagement rate beats 69% of the tracked X accounts closest to it in follower count (20,445 accounts), which puts it in the middle of its size range group. Ranking inside a size band matters because engagement rate falls as accounts grow, so a raw rate would mostly re-measure the follower count. It is a starting point for a look at follower quality, not a verdict on it.
- When does @kellabyte post?
- Most posts go out around 17:00 UTC, and Wednesday is its busiest day, at roughly 2.43 posts per day across the measured window.