Channel
@zorotechnology
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
12,790subscribers
-486 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002172886407 |
|---|---|
| Type | Channel |
| Username | @zorotechnology |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/zorotechnology |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 46% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 23:00 | 12,790 | -19 |
| 16 Sept 2026, 14:18 | 12,809 | -16 |
| 14 Sept 2026, 21:20 | 12,825 | -21 |
| 13 Sept 2026, 06:58 | 12,846 | -12 |
| 11 Sept 2026, 08:41 | 12,858 | -25 |
| 8 Sept 2026, 14:38 | 12,883 | -42 |
| 5 Sept 2026, 07:16 | 12,925 | -27 |
| 3 Sept 2026, 09:18 | 12,952 | -10 |
| 2 Sept 2026, 03:25 | 12,962 | -12 |
| 1 Sept 2026, 05:27 | 12,974 | -14 |
| 31 Aug 2026, 03:14 | 12,988 | -11 |
| 30 Aug 2026, 02:45 | 12,999 | -16 |
| 29 Aug 2026, 02:34 | 13,015 | -15 |
| 28 Aug 2026, 03:45 | 13,030 | -14 |
| 27 Aug 2026, 03:32 | 13,044 | -8 |
| 26 Aug 2026, 01:16 | 13,052 | -15 |
| 25 Aug 2026, 02:12 | 13,067 | -14 |
| 23 Aug 2026, 14:03 | 13,081 | -15 |
| 21 Aug 2026, 20:56 | 13,096 | -16 |
| 20 Aug 2026, 19:24 | 13,112 | first reading |
20 posts held, back to 29 January 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 49 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 14 April 2026. An engagement rate over an empty window would be a number about nothing.
129 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 45.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 58 | 45.0% | |
| 👍 | 42 | 32.6% | |
| 👏 | 12 | 9.30% | |
| 🥰 | 6 | 4.65% | |
| 💯 | 4 | 3.10% | |
| 😍 | 3 | 2.33% | |
| ⚡ | 2 | 1.55% | |
| 🙉 | 2 | 1.55% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 129 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 29 January 2026 to 14 April 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Telegram still dominates crypto communities for one reason, it just works. With 900M+ users and most projects running their main groups there, it’s where real conversations and coordination happen, not just discovery. That’s why it stays on top. https://www.zoro.org/
❤5
The real cost of AI training isn’t just the tech, it’s the price tag. When it costs millions to train a model, only a few companies can afford to play. That means less competition, less experimentation, and slower innovation. That’s the real problem. https://www.zoro.org/
👍2
The biggest mistake in AI startups? Focusing on the model, not the system around it. A strong model without data pipelines, feedback loops, distribution, and real use cases doesn’t hold up. It’s like building a perfect top on a weak foundation, it won’t last. Build the system, not just the core. https://www.zoro.org/
👍2
Funny enough, the simplest AI products often win. Around 76% of users prefer tools that are easy to use over feature-heavy ones. Simple tools get adopted faster and actually get used. Clarity beats complexity always :) See more: https://www.zoro.org/
👍1
Web2 wasn’t built for autonomous AI economies, as it relies on centralized platforms, approvals, and restricted payments that slow agents down. Over 80% of global payments still depend on intermediaries, making machine-to-machine transactions inefficient. https://zoro.org
👏1
Is Claude disrupting the market? It’s gaining ground, with Anthropic taking about 70% of new enterprise AI spend, especially among developers and teams, while ChatGPT still has 100M+ users. This isn’t one winner, models are carving out different roles. https://www.zoro.org/
❤3👍1😍1
AI agents are starting to handle tasks on their own, but full independence is still limited. McKinsey & Company estimates up to 30% of work hours could be automated by AI. Some agents already use crypto wallets for payments. https://www.zoro.org/
❤3👍1😍1
AI has grown fast on centralized platforms, but the trade-offs are becoming clear. Around 60% of companies already worry about vendor lock-in. That’s why decentralization is starting to matter. https://www.zoro.org/
👍4❤1💯1
AI agents are moving beyond simple tools, and Gartner estimates that by 2028 about 33% of enterprise software will include autonomous agents handling decisions and workflows. The next unicorns may rely less on employees and more on networks of agents. https://www.zoro.org/
👍2
Around 84% of developers already use or plan to use AI tools, but tools and infrastructure are not the same. AI tools help with tasks like writing or coding. AI infrastructure lets teams deploy models, manage data, and run real systems. How it works - https://www.zoro.org/
👍6❤3💯2
Most AI in Web3 does not need blockchain. Web2 works for API models. On-chain AI is up around 86% over the past two years, with millions of wallets. Blockchain is needed when agents manage assets, send payments, or require verifiable logic. https://www.zoro.org/
👍4❤2👏2
Who adopts AI faster, enterprises or users? Users move fast, enterprises move bigger. Real impact happens when both align. https://www.zoro.org/
👍5👏3⚡2❤2
Showing the 12 most recent of 20 posts we hold for @zorotechnology. 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.
Named by 1 registered channel — 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Zoro Announcements” (@zorotechnology), 12,790 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/zorotechnology.
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.