Telegram RegisterThe public register of Telegram

Channel

Pieverse News

@pieversenews

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

870subscribers

-53 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002893593596
TypeChannel
Username@pieversenews
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/pieversenews

Growth

870923896.57 August 2026 — 923 subscribers8 August 2026 — 923 subscribers8 August 2026 — 911 subscribers15 August 2026 — 870 subscribers7 August 202615 August 2026
4 measurements spanning 8 days, net -53. 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 862–931 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 16:44870-41
8 Aug 2026, 14:40911-12
8 Aug 2026, 01:00923no change
7 Aug 2026, 19:22923first reading

Engagement

20 posts held, back to 16 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
109.0%
avg views ÷ 870 subscribers
Avg views / post
948
1 post measured
Reaction rate
0.949%
reactions ÷ views · ER floor
Posts in window
1
of 20 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
WindowRolling 30 days · latest post in window 24 July 2026
Posts held20 (16 February 202624 July 2026)
Views total948
Reactions total9
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 01:00 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

Video runtime
47s
Average length
47s

Measured directly from 1 video 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

88 reactions across 16 posts, in 6 distinct kinds. The most used accounts for 31.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2831.8%
2528.4%
🔥1921.6%
🥰1011.4%
🖕55.68%
😢11.14%

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 16 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 88reactions 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 16 February 2026 to 24 July 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

24 Jul 2026, 07:59 UTC948 views9 reactionsread 8 August 2026
Photo

🎁 Claim Your Free $PIEVERSE KuGift — Live Now! A total of 4,000 $PIEVERSE is being distributed through 1,000 KuGifts, with 4 $PIEVERSE in each gift. ⏰ First come, first served — once they’re gone, they’re gone. How to Claim - Download the KuCoin App and create a KuCoin Web3 Wallet. - Complete your wallet setup. - Follow the claiming guide if needed: https://www.kucoin.com/web3/support/48142946141641 - Claim your

9

13 Jul 2026, 14:13 UTC913 views3 reactionsread 8 August 2026
Photo

BNB Chain Campaign Reward Distribution Update The BNB Chain Agent Survival Quest rewards in $U have now been distributed. 🎉 Thank you to everyone who joined the event and helped make it a success!

🔥2😢1

26 Jun 2026, 06:15 UTC≈1,060 views3 reactionsread 8 August 2026
Photo

Pieverse Weekly Roundup 🐾 BNB Agent Survival Quest highlights, Bitget Wallet payments, new messaging updates, and more from across the Pieverse ecosystem!

3

14 Jun 2026, 13:53 UTC≈1,420 views11 reactionsread 8 August 2026
Photo

🧧 Red Packet Race rewards for the Pieverse x @okx APP Campaign with @wallet are now live! Eligible participants can now claim their PIEVERSE rewards directly from the Red Packet Race page. How to claim: 1. Log in to the Red Packet Race page 2. Check your Purr-Fect Claw score 3. Click “Claim Reward” 4. Confirm the onchain transaction to receive your reward Claim now: https://pieverse.io/campaigns/redpacket-race P

5🖕5🔥1

4 Jun 2026, 15:31 UTC≈1,130 views12 reactionsread 8 August 2026
Photo

Thanks to everyone who joined the Pieverse x OKXAPP Campaign with OKX WALLET. The campaign reached $58M in total A2A red packet volume—a look at what happens when agent payments move from concept into real user activity. 🐾 You voted and we listened. Rewards will follow an activity-weighted draw, where higher red packet activity gives you a stronger chance at larger rewards. Final allocations will be shared next we

12

27 May 2026, 16:21 UTC≈1,340 views7 reactionsread 8 August 2026
Photo

100,000+ users have joined the Pieverse x @okx APP Campaign with @wallet and claimed their first .pie AI agent 🐾 A2A red packet transaction volume has now crossed $5M What started as a cute agent card has become a real payment loop at scale: claim a .pie identity, activate Purr-Fect Claw, send and claim red packets, and move value through messaging-native A2A flows This is what we wanted the campaign to prove—that

7

25 May 2026, 05:02 UTC≈1,230 views9 reactionsread 8 August 2026
Photo

Forbes featured Pieverse as one of the companies leading innovation in agentic payments. The next phase of AI will not just be agents that reason, but agents that can pay, settle, and participate in real commerce. 👉 Read the full story on @Forbes

🔥9

21 May 2026, 14:51 UTC≈1,620 views11 reactionsread 8 August 2026

Ready to join the Pieverse x OKX Red Packet Race? Follow this guide to claim your Purr-Fect Claw, generate your OKX x Pieverse Agent Card, share it on X, send red packets, and start climbing the leaderboard! Full Guide 👈

🥰101

21 May 2026, 08:12 UTC≈1,260 views3 reactionsread 8 August 2026
Photo

🚨 Pieverse x OKX Agent Payments Protocol Campaign! A massive 500,000 $PIEVERSE reward campaign powered by OKX APP is here — featuring Red Packet Race, Treasure Code, AI agents, on-chain rewards, and more on X Layer Read the full details on X and get ready to participate!

🔥3

12 May 2026, 15:39 UTC≈1,270 views3 reactionsread 8 August 2026
Photo

Back in the DappBay Featured Activities days, we promised $30K in Pieverse tokens to everyone who joined the "Own Your Time" campaign with @BNBCHAIN. Today, the 6-month cliff period is up — and all $30k worth of $PIEVERSE have been distributed to qualifying participants, right on schedule. Since then, Pieverse has gone all-in on agents and A2A commerce — shipping agent runtimes across multiple messaging platforms,

21

6 May 2026, 07:03 UTC≈1,130 views2 reactionsread 8 August 2026

📣 Pieverse x Mocaverse Campaign Support 🚨 We’ve noticed that some users are experiencing issues participating in the Pieverse x Mocaverse campaign and are currently unable to complete the required verification or join the campaign properly. Our team is actively working together with Mocaverse to resolve these issues as quickly as possible. To help us review and resolve eligible cases efficiently, we’ve opened a de

2

2 May 2026, 05:55 UTC811 views2 reactionsread 8 August 2026
Photo

As promised: more ways to be early, more ways to be rewarded. 🐾 Pieverse is coming to @okx Boost with another Token $PIEVERSE airdrop for the community. • Register by May 4 at 10AM UTC. • Claims open May 5 at 2PM UTC. See you on Boost. Official Tweet

🔥2

Showing the 12 most recent of 20 posts we hold for @pieversenews. 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.

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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“Pieverse News” (@pieversenews), 870 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/pieversenews.

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.