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 97% 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 the other topics.
Growth
26 measurements spanning 91 days, net +464. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)
Subscribers
Change
5 Nov 2026, 03:27
8,799
+2
4 Nov 2026, 19:22
8,797
+8,794
4 Nov 2026, 07:05
3
-8,788
1 Nov 2026, 11:56
8,791
+5
29 Oct 2026, 07:55
8,786
-6
26 Oct 2026, 09:48
8,792
+3
23 Oct 2026, 16:27
8,789
+33
21 Oct 2026, 00:44
8,756
-3
18 Oct 2026, 05:10
8,759
-1
15 Oct 2026, 06:39
8,760
+16
12 Oct 2026, 02:20
8,744
+7
5 Oct 2026, 11:17
8,737
+17
27 Sept 2026, 04:20
8,720
+43
16 Sept 2026, 00:01
8,677
+27
12 Sept 2026, 03:42
8,650
+47
7 Sept 2026, 10:58
8,603
+142
2 Sept 2026, 09:34
8,461
-5
30 Aug 2026, 02:13
8,466
+9
27 Aug 2026, 11:44
8,457
+27
24 Aug 2026, 06:05
8,430
first reading
Engagement
71 posts held, back to 23 July 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 30 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
14.1%
avg views ÷ 8,799 subscribers
Avg views / post
1,240
21 posts measured
Reaction rate
0.157%
reactions ÷ views · ER floor
Posts in window
21
of 71 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 8 of 21 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 6 November 2026
Posts held
71 (23 July 2026 – 6 November 2026)
Views total
26,110
Reactions total
17
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Nov 2026, 11:54 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
Links
≈1,040
Lifetime counters from Telegram’s own channel header, read 8 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
42 reactions across 23 posts, in 3 distinct kinds. The most used accounts for 81.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
34
81.0%
👍
7
16.7%
🔥
1
2.38%
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 30 of the 71 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 42 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 71 most recent posts we hold, published 23 July 2026 to 6 November 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 21 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
📝 Binance Wallet Pre-TGE · 🕒 15:34:41
🇨🇳 特别感谢币安Alpha社区
币安Alpha目前正在进行系统升级。在此,我们衷心感谢社区成员的持续支持和参与。空投和交易竞赛即将回归,我们期待为您带来更多精彩活动!
🎁 专属回馈空投
为表达我们的谢意,截至2026年11月6日23:59:59 UTC,拥有200点或以上Alpha积分的用户将有机会分享总价值35万美元的空投奖励池。
🔸 不扣除Alpha积分
🔸 无需先到先得或领取
🔸 奖励将自动发放至符合条件用户的Alpha账户
有关奖励和发放时间的更多详情,我们将尽快公布。
感谢您的耐心等待和持续支持。我们期待很快为您带来更多精彩活动!
🇺🇸 A Special Thank You to Our Binance Alpha Community
Binance Alpha is currently undergoing a sy…
📢 Binance Wallet Pre-TGE | 🕒 2026-10-29 13:11:26
🔗 [Source]
🇨🇳 拥有 60 点或以上币安 Alpha 积分的币安钱包用户可通过 Alpha 活动页面参与本次 TGE Prime 预售活动。
参与本次 TGE 活动将扣除 15 点积分。
🇺🇸 Binance Wallet users with 60 or more Binance Alpha Points can join this Pre-TGE Prime Sale event via the Alpha event page.
Participation in this TGE event will deduct 15 points.
📢 Binance Wallet Pre-TGE | 🕒 2026-10-28 17:02:01
🔗 [Source]
🇨🇳 币安Alpha第二波Unitas (UP)空投奖励现已开启!
拥有至少244点币安Alpha积分的用户即可按先到先得的方式领取197枚UP代币的空投。如果奖励池未全部发放完毕,积分门槛将每5分钟自动降低5点。
请注意,领取空投将消耗15点币安Alpha积分。用户必须在24小时内于Alpha活动页面确认领取,否则将被视为放弃领取。
🇺🇸 Binance Alpha's second wave of Unitas (UP) airdrop rewards are here!
Users with at least 244 Binance Alpha Points can claim an airdrop of 197 UP tokens on a first-come, first-served ba…
📢 Binance Wallet Pre-TGE | 🕒 2026-10-28 13:43:02
🔗 [Source]
🇨🇳 请准备好领取币安 Alpha 空投,并于今日 09:00 (UTC) 开始交易。
拥有至少 244 点币安 Alpha 积分的用户即可按先到先得的方式领取代币,直至空投池全部发放完毕或空投活动结束。更多详情即将公布。
请密切关注币安官方渠道,了解具体的空投代币及最新动态。
🇺🇸 Please get ready to claim the Binance Alpha airdrop and trade today at 09:00 (UTC).
Users with at least 244 Binance Alpha Points can claim the token on a first-come, first-served basis until the airdrop pool is fu…
Showing the 12 most recent of 71 posts we hold for @eqn_alpha_aster. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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 5 November 2026 — this
entry's latest reading, not the date you are reading this.
“方程式-币安Alpha&Aster上新” (@eqn_alpha_aster), 8,799 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/eqn_alpha_aster.
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.