Visual Studio Code engagement report

Compared with accounts its own size

Visual Studio Code's engagement rate beats 58% of the tracked X accounts closest to it in follower count (4,067 accounts, accounts of similar size (decile 9 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.045%, Visual Studio Code sits above the 25th percentile of the 39,368 accounts in this comparison. That places it in the below the median band, which runs 0.013% to 0.082%.

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 14: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.

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.

Reading these numbers

A typical post picks up 365 interactions against 813K followers, an engagement rate of 0.045%. Measured over 31 original posts, its engagement rate beats 58% of 4,067 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 36K times each, and 1.01% of those impressions turn into an interaction. That is about 4.42% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 1.8 posts a day over the last 30 days, with activity on roughly 60% of days. Most posts go out around 14:00 UTC, and Wednesday is the busiest day of the week. Of the 31 posts sampled, 81% carry an image or video and 42% link out. The account's strongest tracked post pulled 3.8K interactions, about 10x its own typical post. Recurring topics include #vscode, #code, #coding.

What is Visual Studio Code's engagement rate on X?

Visual Studio Code (@code) has an engagement rate of 0.045%, based on the median interactions across 31 original posts from the last 30 days against 813,060 followers. Replies, reposts and quote-posts of other people are excluded from that sample.

Is that a good engagement rate?

At 0.045%, Visual Studio Code sits above the 25th percentile of the 39,368 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 @code have real engagement?

Its engagement rate beats 58% of the tracked X accounts closest to it in follower count (4,067 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 @code post?

Most posts go out around 14:00 UTC, and Wednesday is its busiest day, at roughly 1.83 posts per day across the measured window.