Crypto & trading — 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 83% 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.
Growth
15 measurements spanning 41 days, net -176. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 8,460–8,688 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
17 Sept 2026, 10:18
8,486
-13
13 Sept 2026, 13:15
8,499
-19
10 Sept 2026, 01:37
8,518
-23
4 Sept 2026, 18:20
8,541
-15
1 Sept 2026, 14:06
8,556
-15
29 Aug 2026, 12:18
8,571
-8
26 Aug 2026, 05:24
8,579
-12
23 Aug 2026, 04:49
8,591
-10
20 Aug 2026, 02:52
8,601
-8
16 Aug 2026, 21:45
8,609
-15
13 Aug 2026, 13:36
8,624
-22
10 Aug 2026, 19:22
8,646
-15
7 Aug 2026, 16:17
8,661
-1
7 Aug 2026, 02:15
8,662
no change
7 Aug 2026, 02:04
8,662
first reading
Engagement
20 posts held, back to 29 April 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 27 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 31 October 2022. An engagement rate over an empty window would be a number about nothing.
Reaction mix
172 reactions across 15 posts, in 8 distinct kinds. The most used accounts for 50.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
87
50.6%
🔥
48
27.9%
🤔
10
5.81%
🤯
8
4.65%
😁
6
3.49%
❤
5
2.91%
😱
5
2.91%
🥰
3
1.74%
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 15 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 172 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 April 2022 to 31 October 2022, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
It's been a while since our last announcement. A lot has happened during this time, both with us and in the world, both in the real world and in the crypto world.
As you all know, the crypto community faces many problems. Much is still very uncertain and difficult to interpret or even understand. During this time we tried with all our might to strengthen the project behind the scenes as much as possible. At first we …
Hey Fam,
As you know, the market crashed and we fall down from our good way. The token price dropped from around 0.034 back to 0.02. You all remember how the price got up and it will once again happen. The biggest problem we have right now is, that people are leaving the crypto space after what happened with Luna and UST. Luna 2.0 is a new approach to get everything stable again. We are watching the market before we…
Hey everyone
It’s cold in the crypto world, but don’t worry, ELVN will have a good comeback, as always. This time, we come to stay!
In the meantime, take part in the Liquidity Program. The best paying program in the whole space!
Everyone that already took part did earn huge amounts!
BTC is falling, hard times for crypto, time to earn stable!
Take part in our Liquidity Program and earn BUSD for providing Liquidity!
💰11Minutes Liquidity Program💰
Another day passed, this is one of the best paying reward pools out there!
The early Contributors did already earn more than 15% of their contributions as rewards. Be part of this, those are the current rates.
If you contribute 1000 BUSD to the Liquidit…
Hey Fam,
BitMart delayed the listing for a few days for technical reasons! Trade will start on the 9th of May!!
A special BitMart game with rewards is coming 👀
https://support.bmx.fund/hc/en-us/articles/5727833854619--Important-Notice-Delay-of-11-Minutes-ELVN-Listing
💰11Minutes Liquidity Program💰
Another day passed, this is one of the best paying reward pools out there!
The early Contributors did already earn more than 15% of their contributions as rewards. Be part of this, those are the current rates.
If you contribute 1000 BUSD to the Liquidity program, the estimated daily rewards you will get will be:
Lock Duration 3 Month: $2.91 - In Total: $262.39 (APY 104%)
Lock Duration …
Showing the 12 most recent of 20 posts we hold for @Minutes11Ann. 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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
1
we ourselves saw one of these resolve, at some point
Never seen alive
0
vacant every time we have ever looked
@Minutes11Ann named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@bitmartexchange named in 7 posts, 8 August 2026 – 21 August 2026 · confirmed gone 24 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 17 September 2026 — this
entry's latest reading, not the date you are reading this.
“11Minutes Announcement” (@Minutes11Ann), 8,486 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Minutes11Ann.
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.