16 measurements spanning 15 days, net +828. 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 11,246–12,492 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
22 Aug 2026, 17:24
12,257
+20
21 Aug 2026, 06:34
12,237
+3
20 Aug 2026, 08:33
12,234
-12
19 Aug 2026, 07:05
12,246
-19
18 Aug 2026, 10:03
12,265
-4
17 Aug 2026, 12:23
12,269
-13
16 Aug 2026, 01:45
12,282
-16
14 Aug 2026, 08:39
12,298
-22
13 Aug 2026, 03:34
12,320
-28
12 Aug 2026, 01:33
12,348
+958
11 Aug 2026, 05:03
11,390
-14
10 Aug 2026, 06:01
11,404
-11
9 Aug 2026, 02:51
11,415
-3
8 Aug 2026, 03:12
11,418
-11
7 Aug 2026, 13:01
11,429
no change
7 Aug 2026, 12:53
11,429
first reading
Engagement
24 posts held, back to 5 March 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 27 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
9.37%
avg views ÷ 12,257 subscribers
Avg views / post
1,150
6 posts measured
Reaction rate
1.60%
reactions ÷ views · ER floor
Posts in window
6
of 24 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 20 August 2026
Posts held
24 (5 March 2026 – 20 August 2026)
Views total
6,893
Reactions total
110
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
23 Aug 2026, 03:49 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
114
Videos
28
Links
174
Lifetime counters from Telegram’s own channel header, read 23 August 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.
Video runtime
17s
Average length
9s
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
1,089 reactions across 24 posts, in 11 distinct kinds. The most used accounts for 40.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
444
40.8%
👏
222
20.4%
🔥
174
16.0%
👍
161
14.8%
🎉
62
5.69%
🤗
13
1.19%
🍾
5
0.459%
👀
3
0.275%
⚡
2
0.184%
💯
2
0.184%
🤓
1
0.092%
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 24 of the 24 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 1,089reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 24 most recent posts we hold, published 5 March 2026 to 20 August 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.
🎉EURC is now live on Pheasant Super App!
The multi-stablecoin era is coming. €🇪🇺
Bring the EURO into an AI-powered onchain experience built for both users and AI agents.
One interface. More currencies. More possibilities.
📣https://x.com/PheasantNetwork/status/2090444396210553175
📗https://home.pheasant.network/library/superapp-eurc
Our strategic round calls for an onchain celebration!
✅ Bridge and Swap on all network
🪂 +300 Pheasant Points
🗓️ Aug 18 - Sep 8
🏟️ https://x.com/PheasantNetwork/status/2089654876552786101
Join us as we kick off the next phase together.
📣Strategic Round #2
We're excited to announce strategic funding from Enflux, supporting our next phase of growth as we scale the $PNT ecosystem and prepare for TGE.
With the Super App now live, we're accelerating toward what's next.
More to come⏩
https://x.com/PheasantNetwork/status/2087846174547972332
Pheasant Bird's-Eye Recap: July 2026 7️⃣
🗓️ Monthly Overview
📍 Key Focus
🛠️ Development Updates
💡 Product Metrics
⛓️ Network Share
💬 CEO’s Comment
Take a look back at the month in Pheasant Bird's-Eye!🐦👓
https://x.com/PheasantNetwork/status/2087504195318399009
Pheasant Super App is now live on Arbitrum!🎊
Interact with Arbitrum through a single AI-powered interface. Simply describe what you want to do, and Pheasant takes care of the onchain execution.
This is the first step toward making every onchain action as simple as having a conversation.
Try it now👉 https://pheasant.network/superapp
X post: https://x.com/PheasantNetwork/status/2085381558010261946
🎉Pheasant Super App is live!🪽
Today marks the beginning of a new way to interact with crypto.
Just tell Pheasant what you want to do, and AI takes care of the rest.
📍No protocol selection.
📍No unnecessary complexity.
We're just getting started👉https://pheasant.network/superapp
X announcement: https://x.com/PheasantNetwork/status/2084525668298367326
Blog: https://home.pheasant.network/library/super-app
$PNT distribution is taking shape:wing:
We’ve selected Sablier as our token distribution partner, bringing transparent and seamless onchain distribution to $PNT.
Almost there!
- X: https://x.com/PheasantNetwork/status/2076877829153882565
- Blog: https://home.pheasant.network/library/sablier
Excited to join an upcoming AMA!🗣️
Our CEO, Tomo, will answer any questions and share more about the Pheasant Super App, our vision, and what’s ahead as we approach TGE. We'll see you there soon!
🗓️ Thursday, July 9
🕛 12:00 PM UTC
📌 https://x.com/i/spaces/1DGleeNOnMkJL?s=20
The next chapter of Pheasant Network is almost here🪽
One interface.
Every action.
Powered by AI.
Meet the Super App. Coming soon...
https://x.com/PheasantNetwork/status/2072492210239726036
🤖 Pheasant Network now supports ERC-8004 🧠
AI Agents can discover Pheasant Network, retrieve quotes, build ERC-7683 orders, and track cross-chain transfers through a standardized interface.
Another step toward agent-native interoperability🪽
Read more 👇
https://x.com/PheasantNetwork/status/2069454922047693238
Building with SPECA🛠️
We recently incorporated SPECA's AI-powered analysis into our development workflow to help surface potential issues before deployment.
Excited to see AI becoming a practical tool for building more secure blockchain infrastructure.
https://x.com/PheasantNetwork/status/2067400202802082097
Pheasant Network now fully supports ERC-7683⛺️
By aligning with the emerging standard for cross-chain intents, we're strengthening the foundation for a more interoperable and scalable ecosystem.
Read more👇
https://x.com/PheasantNetwork/status/2067145798878396755
❤60👍17🎉12👏4
Signed Pheasant BD
Showing the 12 most recent of 24 posts we hold for @pheasant_network. 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.
Citation-graph rank
Citation-graph rank — 973,343 of 1,584,420entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
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.
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 22 August 2026 — this
entry's latest reading, not the date you are reading this.
“Pheasant Network🪽” (@pheasant_network), 12,257 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/pheasant_network.
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.