Back to @traversymedia's profile

Brad Traversy engagement report

@traversymedia - 361K followers on X

Measured over 15 original posts from a 30-day window, last computed on October 5, 2026.

Engagement

Middle of its size range
Per follower
0.064%
of 361K followers
Per impression
1.77%
13K views on a typical post
Reach
3.59%
of its followers see a post
Typical post
229
interactions (median)
Saved
0.147%
19 bookmarks on a typical post
Posting rate
0.53/day
active 43% of days
Peak time
11:00 UTC
Thursday

A typical post picks up 229 interactions against 361K followers, an engagement rate of 0.064%. Measured over 15 original posts, its engagement rate beats 63% of 21,185 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 13K times each, and 1.77% of those impressions turn into an interaction. That is about 3.59% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.53 post a day over the last 30 days, though only 43% of days saw any activity at all. Most posts go out around 11:00 UTC, and Thursday is the busiest day of the week. Of the 15 posts sampled, 47% carry an image or video, 7% are part of a thread and 33% link out. The account's strongest tracked post pulled 1.5K interactions, about 6.4x its own typical post.

Measured over 15 original posts from a 30-day window, last computed on October 5, 2026.

Compared with accounts its own size

Brad Traversy's engagement rate beats 63% of the tracked X accounts closest to it in follower count (21,185 accounts, accounts of similar size (decile 10 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 63% 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.064%, Brad Traversy sits above the 25th percentile of the 212,349 accounts in this comparison. That places it in the below the median band, which runs 0.025% to 0.146%.

p100.004%
p250.025%
p50 (median)0.146%
p750.696%
p902.61%
p9983.1%
Engagement rate as a share of followers, across the 212,349 accounts we have scanned enough to measure. The axis is logarithmic, because the top and bottom of this population are about 22,452 times apart and a linear axis would flatten everything below the median into a single point.
Show the percentile table
Engagement rate percentiles
PercentileEngagement rate
10th percentile0.004%
25th percentile0.025%
50th percentile0.146%
75th percentile0.696%
90th percentile2.61%
99th percentile83.1%

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 11:00 UTC, and Thursday 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.

Engagement by hour posted, UTCTwenty-four bars, one per UTC hour. Each bar shows how posts published in that hour compare with their own authors' median engagement. Bars above the centre line ran higher than the median, bars below ran lower. A marker flags Busiest hour: 11:00 UTC.
0003060912151821
Above the authors' own mediansBelowScale: plus or minus 111%Busiest hour: 11:00 UTC
Show engagement by hour posted, utc as a table
Engagement by hour posted, UTC
Hour (UTC)Vs author medianPosts
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 UTC0%116K
22:00 UTC-2%100K
23:00 UTC-1%90K
Engagement by day of weekSeven bars, one per weekday, Sunday first. Each bar shows how posts published on that day compare with their own authors' median engagement. Bars above the centre line ran higher than the median, bars below ran lower. A marker flags Busiest day: Thursday.
SunMonTueWedThuFriSat
Above the authors' own mediansBelowScale: plus or minus 111%Busiest day: Thursday
Show engagement by day of week as a table
Engagement by day of week
DayVs author medianPosts
Sunday+5%393K
Monday+1%483K
Tuesday-2%520K
Wednesday-3%472K
Thursday-2%430K
Friday-3%447K
Saturday+2%393K
See what moves engagement across the whole catalogWhat counts as a good engagement rate at this size

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.

This account's posting mix compared with catalog-wide effects
FormatThis accountCatalog effect95% intervalAccounts behind it
Image or video47% of posts+111%+108% to +115%34K
Outbound link33% of posts-41%-42% to -40%32K
Typical length-no effect-2% to -1%42K
  • 47% 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.
  • 33% 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 224 characters, which falls in the 180 - 280 characters band. Across the catalog, posts of 180 to 280 characters match the same accounts' other posts almost exactly.

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 10, 20266.4x their median

    My daughter used AI to make me a really cool present for my birthday ❤️ https://t.co/AI1AAVZRKk

    1.4K3063536K viewsView on X
  • Sep 3, 20265.5x their median

    There are a lot of issues with AI code, but we have to stop pretending that everyone's code was beautiful before. As a freelancer/consultant, some of you wouldn't believe the crap I had to fix. Stuff that AI would NEVER do 😄 I would have much rather those "devs" use AI

    1.1K93921449K viewsView on X
  • Mar 27, 20262.9x their median

    I know some people are sick of all the AI content everywhere. Tutorials are not dead at TM. Working hard on a 2026 React Native crash course for youtube. Start recording Monday 😀 Quick Screengrab/Preview: https://t.co/XCFcJ8KRl6

    1.0K6153729K viewsView on X
  • Jan 16, 20263.8x their median

    AI generated code is causing some serious problems. Stats show that AI usage has come with a 1.7x increase in bugs. 32% of senior devs have shipped AI generated code, and research shows 45% of it contains security flaws. The problem isn’t AI. It’s over trusting it and shipping oversized PRs with less oversight. Check out the latest video on this topic where @dennisivy11 shares how you can still use AI and secure your code 👇

    79086861358K viewsView on X
  • Jun 23, 20264.0x their median

    Finally finished my homelab server rack 😊 video coming soon Inside: - Sysracks enclosed cabinet - TP-Link Omada 2.5G / 10G core switch - 2U Intel Core Ultra 9 Docker/staging server - GMKTec EVO-X2 AI/automation box (Hermes box) - Dell PowerEdge lab server (Proxmox) - QNAP 8-bay rack NAS with 8x8TB RAID 6 - Synology NAS during migration - Dual APC UPS units - AC Infinity rack cooling - Sonos + smart-home gear tucked in cleanly This runs my internal dev/staging services, local DNS, reverse proxy, storage, backups, automation, and AI agent stack. Proxmox & virtualization learning server. Completely unnecessary. Extremely satisfying. #homelab #serverrack #selfhosted #homeserver #networking

    7975248944K viewsView on X
  • Aug 28, 20263.9x their median

    When using AI to code, be careful about constantly switching between projects. It may not feel exhausting in the moment, but it can burn you out fast. The goal shouldn't be to create as much as possible. It should be to build useful things and actually finish them.

    75971551325K viewsView on X
  • Sep 29, 20263.9x their median

    Today’s seniors are yesterday’s juniors. Where are tomorrow’s seniors coming from?

    7635761536K viewsView on X
  • Aug 13, 20263.6x their median

    I seriously cannot stand these people anymore. I don't know what happened to a good chunk of the tech community. I used to connect with these people because they loved technology like I do. They wanted to learn, build, experiment, and talk about what was possible. Over the past couple of years, though, I've watched a huge portion of that curiosity turn into pure skepticism, pessimism, and hostility. There are two ridiculous extremes in the AI debate. On one end, you have people claiming that non-developers can vibe code anything and that anyone can instantly become a developer. On the other, you have people who treat AI like politics and completely lose their minds over anything associated with it. Lately, I see far more of the latter, and honestly, they are even more irrational and insufferable than the vibe coders. I also know that many of them use AI themselves. They don't actually care about having an honest discussion. AI is just their latest excuse to shit on everyone and everything while pretending they are taking some principled stand. I used to follow politics, but the audiences around political content, on both the left and the right, became so toxic and irrational that I eventually stopped caring about any of it. I appreciate level-headed people who can discuss complicated topics without turning everything into a tribal war. That is what I once believed the tech community was. It does not feel that way anymore, and it is incredibly demotivating and depressing. I am not saying this describes most people, but it describes a large and increasingly loud group. If you find yourself making stupid comments like this, take a step back and ask what you are actually contributing. Criticism is healthy. Skepticism is necessary. Blind hostility, personal attacks, and performative outrage are not. You do not have to love AI. You do not have to use it. You can question the hype, the ethics, the business models, and the effect it may have on our industry. But if you cannot discuss any of that without attacking people, assuming the worst, or turning every conversation into a moral crusade, then you are not protecting the tech community. You are helping destroy the very curiosity and openness that made it worth being part of in the first place. Sorry for the long post

    6924880854K viewsView on X
  • Apr 21, 20261.9x their median

    I’m creating a lot of cool shit lately, but it feels like I’m becoming more of a project manager than a developer 😐

    66918461064K viewsView on X
  • May 3, 20261.7x their median

    My take has changed from “vibe coding will never work” to “vibe coding may work with future models.” But only if you understand software development and architecture. That if will never change for me.

    5403261830K viewsView on X

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.

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 229 interactions against 361K followers, an engagement rate of 0.064%. Measured over 15 original posts, its engagement rate beats 63% of 21,185 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 13K times each, and 1.77% of those impressions turn into an interaction. That is about 3.59% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.53 post a day over the last 30 days, though only 43% of days saw any activity at all. Most posts go out around 11:00 UTC, and Thursday is the busiest day of the week. Of the 15 posts sampled, 47% carry an image or video, 7% are part of a thread and 33% link out. The account's strongest tracked post pulled 1.5K interactions, about 6.4x its own typical post.

What is Brad Traversy's engagement rate on X?
Brad Traversy (@traversymedia) has an engagement rate of 0.064%, based on the median interactions across 15 original posts from the last 30 days against 360,532 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
Is that a good engagement rate?
At 0.064%, Brad Traversy sits above the 25th percentile of the 212,349 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 @traversymedia have real engagement?
Its engagement rate beats 63% of the tracked X accounts closest to it in follower count (21,185 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 @traversymedia post?
Most posts go out around 11:00 UTC, and Thursday is its busiest day, at roughly 0.53 posts per day across the measured window.

Keep going