Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 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 why it has no browse page of its own yet.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
28 measurements spanning 31 days, net -57,563. 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 2,457,952–2,532,783 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)
Subscribers
Change
6 Sept 2026, 14:00
2,466,586
-4,496
4 Sept 2026, 03:55
2,471,082
-2,567
2 Sept 2026, 15:48
2,473,649
-2,650
1 Sept 2026, 13:24
2,476,299
-1,995
31 Aug 2026, 15:57
2,478,294
-2,224
30 Aug 2026, 15:25
2,480,518
-1,903
29 Aug 2026, 17:23
2,482,421
-2,045
28 Aug 2026, 16:19
2,484,466
-1,525
27 Aug 2026, 18:57
2,485,991
-1,216
26 Aug 2026, 17:25
2,487,207
-1,512
25 Aug 2026, 19:04
2,488,719
-1,623
24 Aug 2026, 20:58
2,490,342
-3,696
23 Aug 2026, 03:36
2,494,038
-3,173
21 Aug 2026, 16:16
2,497,211
-2,118
20 Aug 2026, 11:33
2,499,329
-1,596
19 Aug 2026, 12:36
2,500,925
-1,990
18 Aug 2026, 12:43
2,502,915
-2,409
17 Aug 2026, 10:03
2,505,324
-3,228
15 Aug 2026, 18:17
2,508,552
-2,978
14 Aug 2026, 04:56
2,511,530
first reading
Engagement
335 posts held, back to 6 April 2021 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 1,958 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
9.64%
avg views ÷ 2,466,586 subscribers
Avg views / post
238,000
7 posts measured
Reaction rate
1.47%
reactions ÷ views · ER floor
Posts in window
7
of 335 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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 8 September 2026
Posts held
335 (6 April 2021 – 8 September 2026)
Views total
1,663,800
Reactions total
24,517
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
9 Sept 2026, 17:12 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
Photos
127
Videos
13
Links
212
Lifetime counters from Telegram’s own channel header, read 9 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
View velocity
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 7 of this channel’s own posts over the last 30 days: across 6 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 39 hours of being posted; a typical post has already reached 24.7% of its 24-hour view count within the first hour, and 53.8% within the first six; the median 24-hour reach across those posts is 70,950 views — 2.88% of this channel’s own subscriber count (90th percentile 73,100).
7 most recently posted, with a view-velocity reading
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
Reaction mix
92,957 reactions across 26 posts, in 44 distinct kinds. The most used accounts for 59.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
55,091
59.3%
👍
18,444
19.8%
💩
6,729
7.24%
🔥
5,182
5.57%
👎
1,048
1.13%
🖕
788
0.848%
🥱
607
0.653%
👏
539
0.58%
🥰
500
0.538%
😁
490
0.527%
🤬
476
0.512%
🙏
342
0.368%
⚡
295
0.317%
🤣
197
0.212%
😭
168
0.181%
🕊
144
0.155%
❤🔥
139
0.15%
🫡
137
0.147%
🤔
132
0.142%
🆒
122
0.131%
24 further kinds
1,387
1.49%
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 333 of the 335 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 510,783 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 335 most recent posts we hold, published 6 April 2021 to 8 September 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.
Supporting developers is essential to expanding utility at the application level.
Developers create products, services, and experiences that give Pioneers more ways to participate in the Pi ecosystem. Improving the underlying development environment helps turn Pi’s technical capabilities and ecosystem resources into applications that Pioneers can use.
Learn more about Pi's newly released developer capabilities and …
SoloHost gives Pioneers more ways to use their computers for local AI and easier access to other self-hosted applications, further extending the utility of Pi Desktop and Nodes beyond blockchain infrastructure.
OpenClaw and the Atlassian MCP Server show how SoloHost can support different types of self-hosted software for different user needs, from local AI agents to more specialized developer utilities.
Through Sol…
OpenClaw and the Atlassian MCP Server are now featured in SoloHost on Pi Desktop, expanding the range of self-hosted tools users can run locally.
OpenClaw offers a more contained local AI setup with streamlined installation, while the Atlassian MCP Server supports AI-integrated Jira workflows for professionals through a locally run connection.
Go to the Pi mining app to learn more about both apps and how SoloHost e…
Following the successful completion of the Protocol 26 upgrade on Pi Mainnet, Pi Testnet is upgrading to Protocol 27!
Protocol 27 introduces more flexible and secure smart contract authentication capabilities, enabling more advanced ways for accounts and applications to authorize transactions. The upgrade continues Pi’s broader work to incorporate newer protocol features and expand the network’s smart contract capab…
Along with the new Node 0.6.2 release, Pi has completed an initial distributed computing functionality test through SoloHost with five volunteer Node runners.
The devices operated by all five participants successfully completed the computing tasks sent to them automatically through a SoloHost app.
The test validated the end-to-end flow of tasks across real devices, including connecting to a Pi coordinator, receivin…
The Pi Node version 0.6.2 has been released!
This introduces improvements to SoloHost, Node connectivity, and the Pi Desktop user experience.
In parallel, Pi has successfully completed a distributed computing test through a SoloHost app, further advancing the utility of Pi Nodes beyond supporting the Pi blockchain.
Together, these updates make it easier to run and manage applications on Pi Nodes and SoloHost, whil…
The Pi2Day 2026 Ecosystem Quest saw incredible participation with over 2.56 million Pioneer participants, and over 1.78 million of them completing every step to claim this year’s special-edition badge.
Congratulations to everyone who celebrated Pi2Day by exploring the Pi ecosystem and the new Pi2Day releases: SoloHost, Pi-Sign-in, and PiVerify.
Learn more in the Pi app.
Reminder: the Pi Mainnet is upgrading to Protocol v26. All Mainnet node operators must complete the upgrade by August 11 to remain connected to the network.
Protocol v26 is a major milestone that improves contract safety, state management, interoperability, and cryptographic capabilities ahead of the final planned upgrade, Protocol v27.
Details here minepi.com/pi-node
The Pi Mainnet is upgrading to Protocol 26. Deadline: Aug. 11.
All Mainnet node operators must complete the upgrade before the deadline to remain connected to the network. Details here: https://minepi.com/pi-node
Protocol 26 is a major milestone ahead of the final planned upgrade, Protocol 27. With 8 successful upgrades completed over the past few months, these final two upgrades will bring the network up to date w…
In the Pi Launchpad model, projects issue tokens as tools to acquire users for their applications and integrate those tokens directly into product functionality, such as access, payments, rewards, and governance.
Instead of being taken by the issuing project, the proceeds of Pi from their token launch go to a liquidity pool with the ecosystem token, which bootstraps a healthy liquidity foundation from the start.
Fo…
Pi Launchpad has completed the distribution of its second Testnet token, SLICE!
Explore the post-launch experience and see how liquidity pools work through the new price tracking feature!
The Launchpad app in Pi Browser shows individual allocation details, the launch and effective token prices, access to the SLICE liquidity pool, and a chart tracking changes in the SLICE price relative to Test-Pi.
Go to the Pi min…
❤2,560👍779💩313🔥208🖕76🤬74🤣52👏50
Showing the 12 most recent of 335 posts we hold for @PiAnnouncements. 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
Named by 5 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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@PiAnnouncements 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@learnpi_ named in 1 post, 8 August 2026 – 8 August 2026
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 21 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Next Big Coin @freenewcoinlisting · 177,787 Telegram ranks this channel #4 of 86 here — alongside 85 others — read 28 August 2026
Meme Rich Club @meme_investerment_community · 139,088 Telegram ranks this channel #6 of 72 here — alongside 71 others — read 28 August 2026
DePIN - AI @defi_million1 · 140,582 Telegram ranks this channel #9 of 70 here — alongside 69 others — read 28 August 2026
Airdrop Hunters @airdrophuntersrsv · 170,663 Telegram ranks this channel #10 of 85 here — alongside 84 others — read 28 August 2026
Prep 2 | Science | Mr.Ahmed ElBasha @mrahmedelbashaa · 31,636 Telegram ranks this channel #19 of 36 here — alongside 35 others — read 5 September 2026
Coinverse @X365globalteam · 32,243 Telegram ranks this channel #23 of 78 here — alongside 77 others — read 5 September 2026
Alpha Network Official @alphanetworkofficial · 52,302 Telegram ranks this channel #29 of 71 here — alongside 70 others — read 26 August 2026
Pump Arena Channel @pumparenachannel · 30,486 Telegram ranks this channel #35 of 81 here — alongside 80 others — read 7 September 2026
Star Network Official Channel @starnetwork_official · 47,409 Telegram ranks this channel #44 of 74 here — alongside 73 others — read 26 August 2026
Eagle Network Announcement @EagleNetworkChannel · 28,898 Telegram ranks this channel #67 of 80 here — alongside 79 others — read 9 September 2026
World @worldnetworkofficial · 75,859 Telegram ranks this channel #70 of 77 here — alongside 76 others — read 6 September 2026
Meta Whale @metawhale · 46,414 Telegram ranks this channel #71 of 84 here — alongside 83 others — read 27 August 2026
TTcoin | Cryptocurrency @ttcoinofficial · 113,132 Telegram ranks this channel #75 of 88 here — alongside 87 others — read 26 August 2026
This channel appears in 13 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Domains linked from posts
10 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 6 September 2026 — this
entry's latest reading, not the date you are reading this.
“Pi Network” (@PiAnnouncements), 2,466,586 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/PiAnnouncements.
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.