28 Sept 2026, 22:15 UTC156 viewsread 29 September 2026
https://x.com/modusbuilders/status/2104691356857684274?s=20
Channel
Modus
@modusbuilders
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
26subscribers
+3 since we began measuring on 29 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004243880100 |
|---|---|
| Type | Channel |
| Username | @modusbuilders |
| Created | Between 1 May 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 September 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/modusbuilders |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Oct 2026, 20:18 | 26 | -1 |
| 5 Oct 2026, 06:57 | 27 | +4 |
| 29 Sept 2026, 07:22 | 23 | no change |
| 29 Sept 2026, 06:47 | 23 | first reading |
Engagement
16 posts held, back to 18 September 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 612.3%
- avg views ÷ 26 subscribers
- Avg views / post
- 159
- 16 posts measured
- Reaction rate
- 0%
- reactions ÷ views · ER floor
- Posts in window
- 16
- of 16 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 16 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 28 September 2026 |
|---|---|
| Posts held | 16 (18 September 2026 – 28 September 2026) |
| Views total | 2,547 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Sept 2026, 07:22 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Video runtime
- 8m 21s
- Average length
- 1m 24s
Measured directly from 6 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
28 Sept 2026, 22:15 UTC157 viewsread 29 September 2026
https://x.com/modusbuilders/status/2104687263217033447?s=20
28 Sept 2026, 19:06 UTC174 viewsread 29 September 2026
Claude Sonnet 5.5 is now live in Modus. It runs over 30% faster, gets more done in fewer steps, and has a sharp eye for design, so your idea becomes a polished, deployed onchain product with less back and forth along the way. Go build something. https://x.com/modusbuilders/status/2104648754691510635?s=46&t=qGtNRZaNNi2hEJ4GoINGEg
25 Sept 2026, 06:48 UTC168 viewsread 29 September 2026
Photo
Create stunning pitch decks, investor updates and launch presentations with agents that already know your product and your brand. They know what you're building because they built it with you. Context flows through every chapter in Modus, from your PRD to your design to your code, so by the time you reach your deck, your agents already know your story, your users and exactly what you do and don't want. Choose from …
25 Sept 2026, 05:23 UTC145 viewsread 29 September 2026
Video
Your product is live. Now it's time to hire the team that runs it. Agent Employees work around the clock and get better the longer they're with you. Most of that happens in Owner Chat, where you talk to them like you would a new hire, give them direction, and shape what they remember and what they're good at. Only those conversations with you go straight into their memory. Whatever they pick up on their own, from sc…
23 Sept 2026, 12:05 UTC127 viewsread 29 September 2026
Opus 5.5, GPT-6 Sol and GPT-6 Luna are live on Modus. Opus 5.5: Fable-level performance, 40% cheaper than Opus 5 GPT-6 Sol: sharper coding and agent work at half the price GPT-6 Luna: fast and cheap for high-volume tasks Try them now at modus.builders https://x.com/modusbuilders/status/2102730874446024977?s=20
22 Sept 2026, 08:19 UTC124 viewsread 29 September 2026
Photo
Photo, posted without a caption
22 Sept 2026, 08:19 UTC119 viewsread 29 September 2026
Jev from TypeSafe AI is now running inside Modus. We've been testing it since launch, and the results blew past what we expected, so it's rolling out across the platform, on Robinhood Chain, Solana, and every EVM chain we support. First place it landed: tool routing. Every agent turn decides which tools to load and which prompt template to use, and an LLM used to make that call, slowly and often wrong. Jev now makes…
21 Sept 2026, 13:47 UTC108 viewsread 29 September 2026
https://x.com/modusbuilders/status/2102030905845977582?s=20
21 Sept 2026, 08:50 UTC106 viewsread 29 September 2026
Video
Modus Code takes your approved PRD and designs and builds the whole product, live, in front of you. Agents write and test your contract, set up the database and API, and turn every screen into a working page. You watch each step land, and when the contract is ready, you deploy it from chat with a single wallet signature. Everything onchain runs on Modus Gateway. RPC, indexing, and market data come through one key th…
19 Sept 2026, 11:52 UTC135 viewsread 29 September 2026
Video
Build your product inside Modus, from brand design to onchain deployment. Design your app screens, website, and launch kit, including banners, videos, slides, and your investor deck, with agents keeping everything on brand. Then take it onchain. Write EVM smart contracts or Solana programs, have agents review them, and deploy to the chain you choose. Agents work with you at every step, and you can switch to full ma…
19 Sept 2026, 03:29 UTC166 viewsread 29 September 2026
Video
You don't need a design team anymore. You need taste. Modus has a full design studio, with agents working beside you. Websites, app screens, slides, decks, banners, videos. One canvas, everything in your brand. https://x.com/modusbuilders/status/2101151227761295472?s=20
Showing the 12 most recent of 16 posts we hold for @modusbuilders. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Mentions
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 13 October 2026 — this entry's latest reading, not the date you are reading this.
“Modus” (@modusbuilders), 26 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/modusbuilders.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.