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 the other topics.
Observations
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Content that also appears on other registered channels
Posts published here appear in near-verbatim form on 3 other registered channels. This entry also sits inside a group of 5 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
Matching posts — open both and compare (6 of the pairs behind the counts below)
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 331 comparable posts for this entry, running 29 April 2021 to 7 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Of the group of 5 channels, the one whose matching posts we hold earliest is @PiAnnouncements — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Channels linked by matching posts
This channel is in a group of 5 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.
65 measurements spanning 95 days, net -184,351. 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,312,145–2,551,802 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)
Subscribers
Change
10 Nov 2026, 04:06
2,339,798
-2,366
8 Nov 2026, 16:19
2,342,164
-3,114
7 Nov 2026, 08:05
2,345,278
-1,839
6 Nov 2026, 10:16
2,347,117
-1,865
5 Nov 2026, 11:39
2,348,982
-1,997
4 Nov 2026, 10:50
2,350,979
-2,052
3 Nov 2026, 09:09
2,353,031
-1,845
2 Nov 2026, 08:27
2,354,876
-1,827
1 Nov 2026, 04:58
2,356,703
-2,265
31 Oct 2026, 06:08
2,358,968
-2,157
30 Oct 2026, 09:01
2,361,125
-1,929
29 Oct 2026, 09:19
2,363,054
-2,274
28 Oct 2026, 06:27
2,365,328
-1,964
27 Oct 2026, 07:05
2,367,292
-1,806
26 Oct 2026, 09:55
2,369,098
-1,170
25 Oct 2026, 08:58
2,370,268
-1,249
24 Oct 2026, 12:16
2,371,517
-2,351
23 Oct 2026, 12:27
2,373,868
-2,355
22 Oct 2026, 09:51
2,376,223
-2,806
21 Oct 2026, 04:18
2,379,029
first reading
Engagement
348 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 2,083 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
9.96%
avg views ÷ 2,339,798 subscribers
Avg views / post
233,000
7 posts measured
Reaction rate
6.15%
reactions ÷ views · ER floor
Posts in window
7
of 348 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 7 November 2026
Posts held
348 (6 April 2021 – 7 November 2026)
Views total
1,632,000
Reactions total
100,362
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 14:11 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
136
Videos
13
Links
216
Lifetime counters from Telegram’s own channel header, read 11 November 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 7 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 28 hours of being posted; a typical post has already reached 14.5% of its 24-hour view count within the first hour, and 51.5% within the first six; the median 24-hour reach across those posts is 65,300 views — 2.79% of this channel’s own subscriber count (90th percentile 75,160).
8 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
225,772 reactions across 39 posts, in 52 distinct kinds. The most used accounts for 39.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
90,001
39.9%
👍
28,691
12.7%
🖕
28,211
12.5%
👏
21,831
9.67%
💩
18,455
8.17%
👎
14,725
6.52%
🔥
8,840
3.92%
🥴
3,661
1.62%
🙉
3,210
1.42%
🥰
860
0.381%
🥱
826
0.366%
😁
750
0.332%
🙏
732
0.324%
🤬
656
0.291%
⚡
349
0.155%
❤🔥
309
0.137%
🤔
263
0.116%
🤮
222
0.098%
🤣
198
0.088%
🫡
186
0.082%
32 further kinds
2,796
1.24%
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 346 of the 348 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 643,598 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 348 most recent posts we hold, published 6 April 2021 to 7 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 7 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).
Pi's first Ecosystem Summit streams on YouTube: technical demos, new feature announcements, developer conversations and Pi Network founders Chengdiao Fan and Nicolas Kokkalis.
Nov 17 and 18: 8:00 AM PST / 4:00 PM UTC
Nov 19: new 200,000 USDT hackathon kickoff
Check out your Pi App home screen announcement for more details!
Several technical updates have been released to support developers!
- An improved Developer Portal simplifies app configuration and management
- Pi BlockExplorer now tracks historical prices for Launchpad Testnet tokens
- A new SoloHost skill enables AI assistants to prepare app packages for Pi Desktop
- PiVerify has expanded identity verification capabilities for third-party businesses
These improvements reduce ba…
Pi Desktop version 0.6.4 has been released!
The update makes remote access to SoloHost apps much easier by eliminating the need to configure home routers. Pi Desktop now handles the connection setup, making it simpler for Pioneers to access SoloHost apps, such as local AI agents, running on their computers through Pi Browser on their phones.
The release also provides more protection measures for SoloHost users, che…
Pi Ecosystem Summit, coming November 17-19, aims to encourage more builders to develop on Pi, while giving Pioneers an opportunity to discover more applications and utilities across the ecosystem.
The summit will include:
- Platform releases and developer updates
- Developer demos
- App showcases from companies and community developers
- Developer conversations with the Pi Core Team
- All-new hackathon
Learn more…
Pi Network is introducing the first-ever Pi Ecosystem Summit, a three-day online event on November 17–19, 2026!
While Pi Day and Pi2Day celebrate progress across the broader Pioneer community and network, the Pi Ecosystem Summit will focus on developers, the Pi platform, and the apps and utilities they build to serve Pioneers and expand Pi's utility.
The Summit will feature new platform announcements, developer t…
Pi is the native cryptocurrency of the Pi Network ecosystem, supporting ecosystem participation and utility across the network. Stablecoins are cryptocurrencies designed to maintain a relatively stable value, typically by being pegged to an asset such as the U.S. dollar, and they may serve an important but narrower purpose where stable prices are particularly useful.
Learn more about how stablecoins can expand the …
Stablecoins can play an important role in expanding certain utility across the Pi ecosystem, particularly in use cases where predictable price stability is important.
The introduction of stablecoins requires a deliberate, unique approach, and must be aligned with Pi Network’s ecosystem and principles.
- Simply adding a stablecoin does not guarantee that it will naturally complement Pi.
- How the two function alongsi…
Pi Network is exploring how stablecoins can support additional utility across the Pi ecosystem while maintaining a distinct, complementary role to Pi.
Read the new blog in the Pi mining app to learn about:
- Pi’s approach to stablecoins
- How stablecoins may help expand participation within the ecosystem
- Why their implementation requires careful design
And how the OUSD partnership can fit into Pi’s broader stable…
Pi Network is partnering with Open Standard, the company powering Open USD (OUSD), a partner-governed stablecoin designed as open infrastructure! Open Standard brings together more than 200+ partners across payments, finance, technology, and crypto, including Visa, Google, and Stripe.
OUSD is designed with an incentive model focused on supporting ecosystem growth, and Pi will explore rewards programs for Pioneers an…
Following the successful completion of the Protocol 27 upgrade on Pi Mainnet, Pi Testnet has upgraded to Protocol 28.
Protocol 28 improves how the network handles delays in transaction data and enables developers to upgrade groups of smart contracts at once and change stored data more safely as their applications develop.
All Node operators must upgrade their Nodes to Protocol 28 by October 13, 2026, in preparation…
Pi has released several technical updates to KYC and Mainnet migration processes that address specific KYC application corner cases, improve verification processes, and help eligible Pioneers who were previously unable to progress.
KYC and Mainnet migration involve many different checks designed to allow genuine Pioneers to progress while preventing bad actors, bots and those with policy violations.
While most Pion…
Pi KYC and Mainnet migration received several technical updates that address corner cases and help unblock more Pioneers in these processes!
Go to the Pi app to learn more!
❤3,220👍1,160💩410👎193🔥153🖕106😡106🤬75
Showing the 12 most recent of 348 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 · 160,037 Telegram ranks this channel #4 of 86 here — alongside 85 others — read 28 August 2026
Meme Rich Club @meme_investerment_community · 124,771 Telegram ranks this channel #6 of 72 here — alongside 71 others — read 28 August 2026
DePIN - AI @defi_million1 · 126,272 Telegram ranks this channel #9 of 70 here — alongside 69 others — read 28 August 2026
Airdrop Hunters @airdrophuntersrsv · 152,961 Telegram ranks this channel #10 of 85 here — alongside 84 others — read 28 August 2026
Vibe_views @CryptoSpherewive · 19,244 Telegram ranks this channel #17 of 78 here — alongside 77 others — read 28 September 2026
Prep 2 | Science | Mr.Ahmed ElBasha @mrahmedelbashaa · 30,999 Telegram ranks this channel #19 of 36 here — alongside 35 others — read 5 September 2026
Coinverse @X365globalteam · 30,463 Telegram ranks this channel #23 of 78 here — alongside 77 others — read 5 September 2026
Alpha Network Official @alphanetworkofficial · 50,312 Telegram ranks this channel #29 of 71 here — alongside 70 others — read 26 August 2026
Pump Arena Channel @pumparenachannel · 28,433 Telegram ranks this channel #35 of 81 here — alongside 80 others — read 7 September 2026
Star Network Official Channel @starnetwork_official · 45,229 Telegram ranks this channel #44 of 74 here — alongside 73 others — read 26 August 2026
🌎 Atlantis Exchange - Official Channel 🌎🔥🚀 @AtlantisCEX · 21,943 Telegram ranks this channel #54 of 75 here — alongside 74 others — read 21 September 2026
Eagle Network Announcement @EagleNetworkChannel · 27,375 Telegram ranks this channel #67 of 80 here — alongside 79 others — read 9 September 2026
World @worldnetworkofficial · 72,222 Telegram ranks this channel #70 of 77 here — alongside 76 others — read 6 September 2026
Meta Whale @metawhale · 44,595 Telegram ranks this channel #71 of 84 here — alongside 83 others — read 27 August 2026
TTcoin | Cryptocurrency @ttcoinofficial · 84,209 Telegram ranks this channel #75 of 88 here — alongside 87 others — read 26 August 2026
This channel appears in 15 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 10 November 2026 — this
entry's latest reading, not the date you are reading this.
“Pi Network” (@PiAnnouncements), 2,339,798 subscribers as measured 10 November 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.