marcus engagement report
@marcusyul - 536K followers on X
Measured over 15 original posts from a 30-day window, last computed on August 27, 2026.
Engagement
A typical post picks up 226 interactions against 536K followers, an engagement rate of 0.042%. Measured over 15 original posts, its engagement rate beats 53% of 3,792 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 39K times each, and 0.584% of those impressions turn into an interaction. That is about 7.21% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 2.2 posts a day over the last 30 days, though only 30% of days saw any activity at all. Most posts go out around 15:00 UTC, and Thursday is the busiest day of the week. Of the 15 posts sampled, 87% carry an image or video, 20% are part of a thread and 40% link out. The account's strongest tracked post pulled 33K interactions, about 148x its own typical post. Recurring topics include #capcut, #capcutai, #capcutdidthat.
Measured over 15 original posts from a 30-day window, last computed on August 27, 2026. Recurring tags: #capcut, #capcutai, #capcutdidthat.
Compared with accounts its own size
marcus's engagement rate beats 53% of the tracked X accounts closest to it in follower count (3,792 accounts, accounts of similar size (decile 7 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 37% 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.042%, marcus sits above the 25th percentile of the 36,759 accounts in this comparison. That places it in the below the median band, which runs 0.012% to 0.08%.
Show the percentile table
| Percentile | Engagement rate |
|---|---|
| 10th percentile | 0.002% |
| 25th percentile | 0.012% |
| 50th percentile | 0.08% |
| 75th percentile | 0.434% |
| 90th percentile | 2.10% |
| 99th percentile | 160.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 15: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.
Show engagement by hour posted, utc as a table
| Hour (UTC) | Vs author median | Posts |
|---|---|---|
| 00:00 UTC | -1% | 51K |
| 01:00 UTC | -2% | 52K |
| 02:00 UTC | -3% | 50K |
| 03:00 UTC | -4% | 54K |
| 04:00 UTC | -6% | 43K |
| 05:00 UTC | -4% | 42K |
| 06:00 UTC | -4% | 48K |
| 07:00 UTC | -5% | 52K |
| 08:00 UTC | -4% | 61K |
| 09:00 UTC | -3% | 70K |
| 10:00 UTC | -2% | 72K |
| 11:00 UTC | -3% | 79K |
| 12:00 UTC | -2% | 87K |
| 13:00 UTC | -3% | 95K |
| 14:00 UTC | -4% | 98K |
| 15:00 UTC | -2% | 101K |
| 16:00 UTC | -4% | 99K |
| 17:00 UTC | -2% | 91K |
| 18:00 UTC | -1% | 85K |
| 19:00 UTC | -1% | 80K |
| 20:00 UTC | -1% | 75K |
| 21:00 UTC | -1% | 66K |
| 22:00 UTC | -2% | 58K |
| 23:00 UTC | -2% | 52K |
Show engagement by day of week as a table
| Day | Vs author median | Posts |
|---|---|---|
| Sunday | +4% | 232K |
| Monday | 0% | 290K |
| Tuesday | -2% | 281K |
| Wednesday | -1% | 252K |
| Thursday | -2% | 245K |
| Friday | -3% | 254K |
| Saturday | +3% | 228K |
Best tweets
- Aug 25, 2026148x their median
HAN CREADO UN CAPCUT GRATIS Y SIN MARCAS DE AGUA, Y YA TIENE 62K STARS EN GITHUB CapCut te mete marca de agua, te bloquea funciones y encima te cobra suscripción. Un grupo de devs se cansó y construyó la alternativa open source y gratuita. Se llama OpenCut. Te explico todo: Un editor de vídeo open source que están construyendo desde cero, con arquitectura basada en plugins. La idea: una alternativa real a CapCut, pero abierta. Sin marcas de agua, sin paywalls, sin suscripciones. Lo que crearon: → Editor completo con línea de tiempo y multipista → Plugins nativos para expandir lo que puede hacer → Una sola app para web, escritorio y móvil (núcleo en Rust) → MCP Server, automatizaciones y soporte para agentes de IA → Licencia MIT: puedes hacer lo que quieras con él Cómo instalarlo: → Clona el repo desde GitHub → Instala las dependencias → Ejecuta la versión clásica (disponible ya) → Sigue la nueva versión en https://t.co/wa5VTQYLn1 Es exactamente lo que CapCut debería haber sido desde el principio. Enlace abajo👇
- Aug 24, 20268.2x their median
I ran the same task on Claude Code and DeepSeek's new agent harness. One cost $150. The other cost $2. Today we're launching https://t.co/twx6etZb3X (@agentsky_dev), the "OpenRouter for Agents" — one API → Claude Code, Codex, DeepSeek, Kimi, OpenCode, and every major agent in the cloud. And Agent Playground on top: race them on your own task, with your real tools (GitHub, Gmail, more), side by side in a browser: time, cost, tokens burnt. Guess which one was $2.
- Aug 20, 20263.0x their median
Este creador explica cómo factura 30,000$ al mes con un canal de YouTube sin rostro y sin tocar el editor de vídeo. Claude estudia a la competencia, reescribe el guión, genera los visuales y crea los vídeos. 🔖 Menos de 20 minutos para empezar a generar tus primeros ingresos. https://t.co/faNs05Oi7o
- Aug 19, 20262.5x their median
https://t.co/2396fF6YlN
- Aug 26, 20262.1x their median
TUTORIAL COMPLETO DE YOUTUBE SHORTS EN 42 MINUTOS Cómo un chico en sus 20 pasó a ganar $100k al mes publicando shorts simples Encuentra el nicho. Publica sin mostrar la cara. Escala hasta los 6 dígitos al mes. 🔖 Guárdalo, te será muy útil https://t.co/Jk9CHrhbWi
- Aug 26, 2026
We thought a regular progress update would be boring, so we figured we’d show you instead. https://t.co/618njJYIZc
- Aug 25, 2026
A PE-backed healthcare company asked us to modernize their prior authorization automation on a ten-year platform with regulated patient data. The product roadmap called for a full platform rebuild with a new architecture, new data model, and new automation engine. They were skeptical of another automation overhaul. We proposed a proof of concept: one live payer portal, prove it works before building the product. We shipped a production browser extension in two months. Coordinators stopped bypassing the system. The bots ran headless browsers from a data center. Payers detected the IP and flagged it. When a bot hit MFA or a clinical question it couldn't answer, the session died. The coordinator filed a support ticket, waited for engineering to patch that specific workflow branch, and started the submission from scratch. Payer portals branch depending on procedure codes, clinical context, and plan requirements. The old system learned those paths one failure at a time. A coordinator would submit, the bot would break on a new branch, engineering would patch, and the next case would hit another branch nobody had mapped. The portal backlog never closed. We moved the automation into the coordinator's own browser. Same authenticated session they'd use for a manual submission. Payers see a normal login from a normal IP. When the automation needs help, the coordinator steps in and the run continues where it left off. Concept to production in two months with six engineers, HIPAA-hardened, PHI remediation across stored values and logs. Then we built Observe Mode. When a coordinator works a portal that doesn't have a script, the extension captures what they do. Those recordings become the foundation for the next automation. Coverage that builds from real workflows instead of breaking first and patching after. Ten years of payer workflow knowledge baked into the scripts. We migrated it into the new engine while the legacy platform kept running underneath. Build beside it, prove it works, and let the old system go when it's ready. That's how we modernize platforms that can't go down.
- Aug 24, 2026
TENGO CLAUDE CODE, CODEX Y CURSOR CORRIENDO A LA VEZ, Y CADA UNO CON SUS PROPIAS REGLAS si usas varios coding agents ya sabes el lío: reglas, skills, hooks y correcciones repartidas entre todos, sin sincronizar nunca. cada agente termina siendo su propio grafo de dependencias, y nadie lo está vigilando. encontré @blumedotcodes, una app local que ve y mantiene ese grafo entero. → detecta cuando corriges a tu agente → convierte esa corrección en skill o regla → vigila varios agentes a la vez, no solo uno → todo corre en local, nada sale de tu máquina no reemplaza a tus agentes, corre al lado de ellos y mantiene el orden. gratis para descargar.
- Aug 20, 2026
PERDISTE UN SÁBADO ENTERO POR UN "DÓNDE ESTÁ MI PEDIDO" Pasa en cualquier tienda de shopify. Preguntas repetidas, tickets que se acumulan, y tú contestando fuera de horario. Resolvas se conecta a tu soporte y resuelve solo: → Reembolsos y cambios dentro de tus límites → Respuesta en menos de 15 segundos → "Dónde está mi pedido" resuelto al momento → Tú decides los casos que se escapan Setup de 5 minutos, sin tocar nada de tu tienda. Enlace abajo a su waitlist :)
- Aug 20, 2026
Announcing the Lindy Chrome extension. Bring Lindy straight into your inbox to highlight your most important emails, draft replies backed by all your memories, and teach it how to label your email. Live now: https://t.co/av9senk60g https://t.co/Kfudarwt6b
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 X accounts - escrow-protected
PlayerSells is an escrow marketplace for X accounts. Every deal is protected, with no middleman risk.
Reading these numbers
A typical post picks up 226 interactions against 536K followers, an engagement rate of 0.042%. Measured over 15 original posts, its engagement rate beats 53% of 3,792 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 39K times each, and 0.584% of those impressions turn into an interaction. That is about 7.21% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 2.2 posts a day over the last 30 days, though only 30% of days saw any activity at all. Most posts go out around 15:00 UTC, and Thursday is the busiest day of the week. Of the 15 posts sampled, 87% carry an image or video, 20% are part of a thread and 40% link out. The account's strongest tracked post pulled 33K interactions, about 148x its own typical post. Recurring topics include #capcut, #capcutai, #capcutdidthat.
- What is marcus's engagement rate on X?
- marcus (@marcusyul) has an engagement rate of 0.042%, based on the median interactions across 15 original posts from the last 30 days against 536,219 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
- Is that a good engagement rate?
- At 0.042%, marcus sits above the 25th percentile of the 36,759 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 @marcusyul have real engagement?
- Its engagement rate beats 53% of the tracked X accounts closest to it in follower count (3,792 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 @marcusyul post?
- Most posts go out around 15:00 UTC, and Thursday is its busiest day, at roughly 2.2 posts per day across the measured window.