NVK engagement report
@nvk - 162K followers on X
Measured over 6 original posts from a 30-day window, last computed on October 25, 2026.
Engagement
Early reading. We have captured 6 original posts for this account, below the 8 we require before treating a median as settled. The numbers above describe what we have seen so far, not a finished profile of the account.
A typical post picks up 138 interactions against 162K followers, an engagement rate of 0.086%. Posts are seen about 29K times each, and 0.485% of those impressions turn into an interaction. That is about 17.7% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 1.5 posts a day over the last 30 days, though only 17% of days saw any activity at all. Most posts go out around 21:00 UTC, and Friday is the busiest day of the week. Of the 6 posts sampled, 17% carry an image or video and 50% link out. The account's strongest tracked post pulled 8.1K interactions, about 59x its own typical post. Only 6 original posts have been captured so far, fewer than the 8 posts we want behind a median before treating it as settled. Read the figures above as an early measurement of this account, not as a finished profile of it.
Measured over 6 original posts from a 30-day window, last computed on October 25, 2026.
Where this sits in the catalog
At 0.086%, NVK 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%.
Show the percentile table
| Percentile | Engagement rate |
|---|---|
| 10th percentile | 0.004% |
| 25th percentile | 0.025% |
| 50th percentile | 0.146% |
| 75th percentile | 0.696% |
| 90th percentile | 2.61% |
| 99th percentile | 83.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 21:00 UTC, and Friday 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 | 17% of posts | +111% | +108% to +115% | 34K |
| Outbound link | 50% of posts | -41% | -42% to -40% | 32K |
| Typical length | - | no effect | -2% to -1% | 42K |
- 17% 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.
- 50% of its posts carry a link off X. Across the catalog, posts with an outbound link run 41% below the same accounts' other posts, so a large share of this account's output sits in the weakest bucket we measure.
- Its average post runs 184 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
- Oct 23, 202659x their median
I bet a lot of people are having the same idea I'm having... https://t.co/1FutXeBlR6
- May 21, 20268.7x their median
Sparrow v2.5.0 released with: Silent Payments (SP) wallets SP-capable Frigate public server @2140_dev https://t.co/C7r0pfBGD5 fee rates source https://t.co/HOEwliSIRd https://t.co/5hyNDWn5Ka
- Oct 16, 20265.5x their median
Yahoo is still blocking emails from our newly assigned IPv4 space (206.220.120.0/22). It's likely they're behind on updating their database of allocated IP space. It was already published via https://t.co/qmpaXCrt47 and other providers have been accepting it for 2 weeks already.
- Aug 11, 2026
Some lessons we learned from the Coldcard incident that might be useful to other Bitcoin services: 1/ The importance of not reusing addresses Reusing addresses has always been discouraged for privacy, but this incident showed it’s also a first line of defense during a security breach, particularly for multisig. As long as even one key in your quorum remains uncracked, an attacker can’t locate your unspent addresses from on-chain data alone, because that key’s public keys never appear on-chain until you spend. 2/ Multisig wallets need an end-to-end key replacement/rotation flow When users have to migrate under pressure, the dangerous parts are manual: hand-entering destination addresses, deciding which keys to keep, preserving coin segregation, choosing how to broadcast. A good rotation flow handles all of this for them, so a stressful, error-prone process becomes something an ordinary user can complete safely without losing privacy or making a costly mistake. This turned out to matter enormously during the incident. 3/ Reliable communication in a crisis The sooner users learn of a security issue, the more time they have to act before it becomes a loss. Bitcoin services should have a built-in, redundant alert system ready before an emergency. The hard part is doing it without sacrificing privacy: you need a way to reach users reliably without collecting the kind of personal data that becomes a liability of its own. This matters especially for a long-term savings solution like ours. Many users keep their cold storage genuinely cold, logging in only occasionally, and a lot of them aren’t on social media or following Bitcoin news day to day. For them, a reliable alert reaching them directly can be the difference between acting in time and never hearing about the problem at all.
- Oct 23, 2026
IMHO, the Brotli bug (think zlib 20 years ago) is a bigger deal than PHP2Shell and all the "oooh, AI found it! AI found it!" hype. Node2Shell is a terrible name. I’m calling it Broccoli. 🥦
- Sep 14, 2026
If you're running Core Lightning (CLN) with the experimental dual-funding feature, you probably want to disable it for now: https://t.co/z2YCG37WXl
- Oct 23, 2026
How exploitable is the recent Broccoli 🥦 vulnerability (CVE-2026-111497)? We went beyond reproducing memory corruption and demonstrated a control-flow hijack. Not a realistic RCE exploit, but definitely not just a crash. Here's what we found. 🧵
- Oct 25, 2026
https://t.co/PbEtWWE9H0
- Nov 21, 2023
BBQr 🤭
- Oct 23, 2026
We’ve opened Pandora’s box. AI is making attacks faster, while defense still depends on people reviewing changes and shipping fixes. AI is the only way to keep up. But how long can that human bottleneck hold? AI Can Find the Bugs. Who Fixes the Internet? https://t.co/I7wMd90P5v
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 138 interactions against 162K followers, an engagement rate of 0.086%. Posts are seen about 29K times each, and 0.485% of those impressions turn into an interaction. That is about 17.7% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 1.5 posts a day over the last 30 days, though only 17% of days saw any activity at all. Most posts go out around 21:00 UTC, and Friday is the busiest day of the week. Of the 6 posts sampled, 17% carry an image or video and 50% link out. The account's strongest tracked post pulled 8.1K interactions, about 59x its own typical post. Only 6 original posts have been captured so far, fewer than the 8 posts we want behind a median before treating it as settled. Read the figures above as an early measurement of this account, not as a finished profile of it.
- What is NVK's engagement rate on X?
- NVK (@nvk) has an engagement rate of 0.086%, based on the median interactions across 6 original posts from the last 30 days against 161,859 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
- Is that a good engagement rate?
- At 0.086%, NVK 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 @nvk have real engagement?
- There is not yet enough sample to rank this account against others of its size.
- When does @nvk post?
- Most posts go out around 21:00 UTC, and Friday is its busiest day, at roughly 1.5 posts per day across the measured window.