Back to @CEOGuy's profile

Ilan Rakhmanov engagement report

@CEOGuy - 222K followers on X

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

Engagement

Per follower
0.034%
of 222K followers
Per impression
0.278%
27K views on a typical post
Reach
12.2%
of its followers see a post
Typical post
76
interactions (median)
Saved
0.007%
2 bookmarks on a typical post
Posting rate
0.37/day
active 23% of days
Peak time
13:00 UTC
Wednesday

Early reading. We have captured 3 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 76 interactions against 222K followers, an engagement rate of 0.034%. Posts are seen about 27K times each, and 0.278% of those impressions turn into an interaction. That is about 12.3% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.37 posts a day over the last 30 days, though only 23% of days saw any activity at all. Most posts go out around 13:00 UTC, and Wednesday is the busiest day of the week. Of the 3 posts sampled, 100% carry an image or video and 67% are part of a thread. The account's strongest tracked post pulled 111K interactions, about 1458x its own typical post. Only 3 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 3 original posts from a 30-day window, last computed on October 2, 2026.

Where this sits in the catalog

At 0.034%, Ilan Rakhmanov sits above the 25th percentile of the 204,798 accounts in this comparison. That places it in the below the median band, which runs 0.024% to 0.143%.

p100.004%
p250.024%
p50 (median)0.143%
p750.678%
p902.55%
p9982.4%
Engagement rate as a share of followers, across the 204,798 accounts we have scanned enough to measure. The axis is logarithmic, because the top and bottom of this population are about 22,879 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.024%
50th percentile0.143%
75th percentile0.678%
90th percentile2.55%
99th percentile82.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 13: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.

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: 13:00 UTC.
0003060912151821
Above the authors' own mediansBelowScale: plus or minus 111%Busiest hour: 13: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: Wednesday.
SunMonTueWedThuFriSat
Above the authors' own mediansBelowScale: plus or minus 111%Busiest day: Wednesday
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 video100% of posts+111%+108% to +115%34K
Outbound link0% of posts-41%-42% to -40%32K
Typical length-+15%+14% to +16%32K
  • 100% 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.
  • 0% 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 471 characters, which falls in the over 280 characters band. Across the catalog, posts over 280 characters run 15% above 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

  • Jul 1, 20261458x their median

    Fable 5 is back. https://t.co/9RTGUCcPHy

    90K11K4.3K5.0K17M viewsView on X
  • Jun 2, 2026308x their median

    Building apps has never been easier. With Sites, Codex can turn your work, ideas, and plans into an interactive website or app your team can explore, use, and share with a URL. Rolling out to Business and Enterprise plans, before expanding more broadly. https://t.co/fF17Y2EzCP

    19K1.8K9641.3K9.7M viewsView on X
  • Jul 8, 20261.9x their median

    We built a full course on running Claude Code and AI agents the way that actually ships product, not toy demos. Always-on agents, a local brain that never forgets, and the prompting discipline that lets one person out-ship a team. It's what our engineering, marketing and ops teams actually run on day to day. Built it just for us. Should we open it to everyone?

    768591319K viewsView on X
  • Jul 23, 2026

    We just solved a problem every company has with AI and their employees. We’re giving early access to select few. If you believe your company can use a central Brain that syncs teams, AI agents, and company data, then join the waitlist below. https://t.co/TCVRghsfuq

    64733165K viewsView on X
  • Jul 16, 2026

    Teams that use AI Agents a lot, and are tired of their agents being out of sync with other team members, hit me up. We built a solution that works really well, and we’re looking for 10 companies to give free access to in exchange of constructive feedback. Get your team a brain.

    69431145K viewsView on X
  • Jun 1, 2026

    A self-custodial AI agent I built is up ~30% trading live on Hyperliquid this week. Small sample, means nothing yet, but here's what's under it. We already had AI at @Chain_GPT that flags bullish/bearish signals on tokens and one that price-predicts bluechips like $BTC with ML. The problem I kept seeing was that people have the data and still don't know how to turn it into actual trades. So I wired our API into Claude Opus 4.8 and let it trade those signals. I hold the keys the whole time, it just decides and executes. Up about 30% in a few days. Could reverse tomorrow, not advice. Worth open sourcing so anyone can run their own?

    7313921.5M viewsView on X
  • Jun 26, 2026

    I gave Claude Code one prompt and didn't touch the keyboard again until the whole thing was built and QA'd. It's a loop. You describe the goal once, it plans the phases, builds item by item, audits its own work, runs QA, and only comes back when it's actually done. No back-and-forth, no babysitting. This is the sauce a solo founder uses to out-ship a whole team. Bookmark it. Setup: - Agent: Claude Code (Opus 4.8) - Install: Obsidian + Obsidian Skills, Playwright MCP, Davia, Graphify, Claude in Chrome, Claude Preview, Figma, Notion, Vercel, superpowers, frontend-design, mempalace, taste-skill, skill, ai-seo, impeccable The prompt: ``` /goal /loop /effort ultracode /workflow {DESCRIBE IN FULL THE GOAL YOU WANT TO ACHIEVE} That's the high level of what I'm trying to build. Analyze it, understand it, and research it further so you can help me build a strong plan that's data and value driven. Document everything in our local brain/wiki and on Notion. Here's the master page to write in, create sub-pages as needed: {NOTION URL}. Then do the following. 1. List every phase and every item needed to complete this goal in full, phase by phase, item by item. Audit the list, make improvements, repeat until the audit is clean and the list is finalized. 2. For each item, build a careful, strategic plan. Research and brainstorm hard first, be data and value driven. Write one plan at a time, not all at once. After each plan, audit it, improve it, repeat until the audit is clean. 3. Sort all phases and items by priority and the best order to reach the goal. If at any point you hit a question or a decision: brainstorm hard, lay out the best options, and pick the recommended one. You're fully authorized to decide on auto mode without asking me. For anything that needs a PRD (feature, product, UI/UX, flow, architecture): first list all the PRDs needed, then write them one by one. After each PRD, audit and improve, and loop until the audit is clean before the next one. Then write the rest of the documentation (architecture, roadmap, UI/UX). For each piece, assign an AI agent that's an expert in that field (senior UI/UX designer, senior engineering architect, etc). When the docs are complete, audit everything and improve until the audit is clean. Once the plan is fully documented, perfected, and passing every audit, prepare for execution. Re-check the priority order from first to last. Then execute item by item: study the plan, brainstorm to improve it, audit and fix until clean, then build the item. After building, audit your work and fix until clean. Then test and run QA (if applicable) and fix until clean. Move to the next item and repeat, through every phase, until all items are built, tested, and passing QA and audits. When everything is done, run a full E2E QA sweep. Test every page, button, tab, function, and flow, leave nothing behind. If anything breaks: stop, plan the fix, fix it, and restart the E2E from the top, repeating until QA passes in full. Only then notify me it's good to go, with a link to the docs, a URL to test (if applicable), a summary of what was achieved, and any open items, engineering gaps, or next steps, itemized by priority. Then tell me what you were able to build. ``` Point it at a real goal and tell me what it builds. I'll help you tune it so it actually finishes.

    634132775K viewsView on X
  • Sep 16, 2026

    Long term staking continues to grow, with @Chain_GPT’s latest @BNBCHAIN contract holding 54.8M CGPT across 11 pools. 34.1M CGPT, or 62%, is locked for at least one year, showing strong commitment to longer term staking. Here’s the onchain breakdown 🧵👇 https://t.co/S1zkgJi87z

    58134327K viewsView on X
  • Jul 1, 2026

    Before I execute any plan, I have a swarm of AI agents rip it apart first. Startup idea, product architecture, a marketing plan, a fundraising strategy, whatever it is. I stopped trusting my own plans until a room of brutally honest experts has torn into them and I've seen what's left standing. The prompt spins up a council with different backgrounds and roles, hands them the whole plan, lets them debate and research on their own, then makes them argue until they land on a v2 that's actually ready. Then it writes the full A-Z of how to execute it. This is the exact prompt I run in Claude Code with Opus 4.8: {Attach your file with the entire plan documented} /goal This is the plan. Before we execute, I want a brutally honest expert council with different backgrounds, roles, knowledge and traits relevant to this plan, like a real team would have. Deploy a swarm of agents with those characteristics, give them the full context of the plan, and have them debate it, brainstorm, and be brutally honest and data driven. They can research independently, and each comes back with their own conclusions. Once all the reports are in, study everything, consolidate it, and generate a v2 plan that's actually ready to execute. Then repeat this in a /loop until the majority of the council agrees the plan is good as is. Once it's finalized, build a detailed, professional, step by step A-Z execution plan covering everything we need to do to pull it off. Steal it. Tell me what it catches on your plan.

    64950492K viewsView on X
  • Sep 23, 2026

    Introducing Brain, the shared intelligence layer for a world increasingly run by humans and agents together. 🧠 We’ve spent a lot of time thinking about what happens when AI stops being a tool you open and starts becoming part of how a company actually operates. That world needs persistent memory, shared context, reusable skills, governed access and a way for agents to coordinate with people and with each other. That’s what Brain is built for. A human can add knowledge once and every permitted agent can use it. An agent can create context another agent picks up later. Teams can work across different models and interfaces without rebuilding their intelligence from scratch every time. Over time, the Brain becomes a living layer of shared intelligence across the company. This is the foundation we see for multiplayer AI. If you’re a solo builder, a small team or a large enterprise and want to get your own Brain running, DM me.

    60781220K 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 76 interactions against 222K followers, an engagement rate of 0.034%. Posts are seen about 27K times each, and 0.278% of those impressions turn into an interaction. That is about 12.3% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.37 posts a day over the last 30 days, though only 23% of days saw any activity at all. Most posts go out around 13:00 UTC, and Wednesday is the busiest day of the week. Of the 3 posts sampled, 100% carry an image or video and 67% are part of a thread. The account's strongest tracked post pulled 111K interactions, about 1458x its own typical post. Only 3 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 Ilan Rakhmanov's engagement rate on X?
Ilan Rakhmanov (@CEOGuy) has an engagement rate of 0.034%, based on the median interactions across 3 original posts from the last 30 days against 222,016 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
Is that a good engagement rate?
At 0.034%, Ilan Rakhmanov sits above the 25th percentile of the 204,798 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 @CEOGuy have real engagement?
There is not yet enough sample to rank this account against others of its size.
When does @CEOGuy post?
Most posts go out around 13:00 UTC, and Wednesday is its busiest day, at roughly 0.37 posts per day across the measured window.

Keep going