AI.PIBBLE official pinned «To the PIBBLE Community, PIBBLE, which has operated under a global structure since 2018, has completed its consolidation into a single entity, PIBBLE Korea. All legal and tax compliance reviews within South Korea have been finalized, and official notification…»

Channel
AI.PIBBLE official
@pibble_official
On this record: Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry
10,270subscribers
-531 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001215772482 |
|---|---|
| Type | Channel |
| Username | @pibble_official |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/pibble_official |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 03:57 | 10,270 | -29 |
| 5 Sept 2026, 18:17 | 10,299 | -22 |
| 3 Sept 2026, 21:01 | 10,321 | -7 |
| 2 Sept 2026, 09:18 | 10,328 | -9 |
| 1 Sept 2026, 11:53 | 10,337 | -15 |
| 31 Aug 2026, 14:23 | 10,352 | -42 |
| 30 Aug 2026, 17:43 | 10,394 | -10 |
| 29 Aug 2026, 16:07 | 10,404 | -6 |
| 28 Aug 2026, 19:34 | 10,410 | -4 |
| 27 Aug 2026, 21:25 | 10,414 | -4 |
| 26 Aug 2026, 21:02 | 10,418 | -9 |
| 25 Aug 2026, 18:23 | 10,427 | -16 |
| 24 Aug 2026, 19:37 | 10,443 | -11 |
| 23 Aug 2026, 07:47 | 10,454 | -15 |
| 21 Aug 2026, 16:37 | 10,469 | -7 |
| 20 Aug 2026, 13:37 | 10,476 | -8 |
| 19 Aug 2026, 13:32 | 10,484 | -23 |
| 18 Aug 2026, 10:03 | 10,507 | -42 |
| 17 Aug 2026, 11:45 | 10,549 | -53 |
| 16 Aug 2026, 01:43 | 10,602 | first reading |
Engagement
20 posts held, back to 4 August 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 36 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 28 April 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
2,205 reactions across 13 posts, in 12 distinct kinds. The most used accounts for 12.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🥰 | 273 | 12.4% | |
| 💯 | 268 | 12.2% | |
| ❤ | 250 | 11.3% | |
| ❤🔥 | 248 | 11.2% | |
| 🤩 | 245 | 11.1% | |
| 😍 | 244 | 11.1% | |
| 🎉 | 239 | 10.8% | |
| 🔥 | 238 | 10.8% | |
| 👍 | 190 | 8.62% | |
| 💩 | 4 | 0.181% | |
| 😱 | 4 | 0.181% | |
| 👏 | 2 | 0.091% |
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 13 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 2,205 reactions 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 4 August 2025 to 28 April 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
To the PIBBLE Community, PIBBLE, which has operated under a global structure since 2018, has completed its consolidation into a single entity, PIBBLE Korea. All legal and tax compliance reviews within South Korea have been finalized, and official notification has been submitted to major South Korean exchanges. Leadership, team composition, PIB token issuance structure and policy, and community operations remain unc…
👏2💩1
📢 PIBBLE (PIB) | 2026 Roadmap Official Release PIBBLE has officially published its 2026 roadmap. The roadmap is structured around a participation-reward-utility-burn cycle, with the objective of transitioning PIB into a utility asset whose value is generated through ecosystem participation. Q1 | Staking service pilot launch and blockchain UX service open Q2 | Full staking service launch and community expansion Q3 | …
💩3❤1😱1
AI.PIBBLE official pinned «We're pleased to announce that Coinone is running a PIB trading volume event. 👉 View Coinone announcement: https://coinone.co.kr/info/notice/4988 We appreciate your interest and participation. Thank you.»
We're pleased to announce that Coinone is running a PIB trading volume event. 👉 View Coinone announcement: https://coinone.co.kr/info/notice/4988 We appreciate your interest and participation. Thank you.
😱2👍1
📢 [공지] 2025년 로드맵 달성 현황 보고 PIBBLE 커뮤니티 여러분, 2025년 한 해를 마무리하며, PIBBLE 프로젝트의 주요 성과를 공유드립니다. 피블팀은 AI 기반 서비스 고도화, 멀티체인 인프라 완성, 무역금융 AI 시장 진출을 중심으로 대부분의 로드맵을 성공적으로 달성했습니다. ✨ 2025년 핵심 성과 - AI PIBBLE 누적 75만 유저 달성 - 멀티체인 생태계 완성 (ERC20+Kaia+Solana) - AION 엔진 정식 출시 - UAE 중동 파트너십 체결 - 제10차 PIB 토큰 소각 완료 (4,800만 PIB) POSCO, Amazon, 두바이 금융권의 검증을 받은 PIBBLE의 기술력을 바탕으로, 2026년에는 AI와 블록체인이 실물경제로 확장되는 새로운 생태계를 구축해 나가겠습니다. 여러분…
❤1😱1
AI.PIBBLE official pinned «🔥PIBBLE 10th PIB Token Burn Completed Hello PIBBLE Community! We've successfully completed our Q3 2025 revenue-based token burn. ━━━━━━━━━━━━━━━━━━━━ 📊 Burn Details - Burned Amount: 48,000,000 PIB - Burn Date: November 25, 2025 - Funding Source: PIBBLE…»
🔥PIBBLE 10th PIB Token Burn Completed Hello PIBBLE Community! We've successfully completed our Q3 2025 revenue-based token burn. ━━━━━━━━━━━━━━━━━━━━ 📊 Burn Details - Burned Amount: 48,000,000 PIB - Burn Date: November 25, 2025 - Funding Source: PIBBLE App Revenue (P.Pay transactions, AICREDIT sales, etc.) - Burn Wallet: 0x1cA108eD22ac0125Cf202B721cC01bBDb9bBA97D - TX Hash: 0x52a83877c28005277ca923bd7297ea374c8307d…
🛫 PIBBLE × Dreamstone Partners Strategic MOU AI blockchain platform PIBBLE has executed a Memorandum of Understanding with global aviation finance specialist Dreamstone Partners to develop an innovative blockchain-based investment model leveraging aircraft real-world assets. 🔑 Key Highlights: Digital transformation and tokenization of aircraft leasing assets Integration of real economy with Web3 ecosystem infrastru…
🔥67🥰64❤61❤🔥56💯56🤩54🎉48😍47
AI.PIBBLE official pinned «🚀[AION Launch] *AION L/C Review Engine Now Live* 🎯 PIBBLE #Pibble(#PIB) Enters Trade AI Market Hello PIBBLE Community! 🙌 Caramelbay is expanding into the B2B trade market, leveraging AI expertise built through PIBBLE! Annual trade disputes from Letter of…»
AI.PIBBLE official pinned «🚀[AION Launch] *AION L/C Review Engine Now Live* 🎯 PIBBLE #Pibble(#PIB) Enters Trade AI Market Hello PIBBLE Community! 🙌 Caramelbay is expanding into the B2B trade market, leveraging AI expertise built through PIBBLE! Annual trade disputes from Letter of…»
🚀[AION Launch] *AION L/C Review Engine Now Live* 🎯 PIBBLE #Pibble(#PIB) Enters Trade AI Market Hello PIBBLE Community! 🙌 Caramelbay is expanding into the B2B trade market, leveraging AI expertise built through PIBBLE! Annual trade disputes from Letter of Credit (L/C) issues reach $15B+ in Korea alone. Document defects and toxic clauses cause frequent payment rejections. ✨ *AION Core Features* - LLM trained on 5,00…
💯50❤🔥48❤41🎉40🔥40🥰40😍35🤩22
Showing the 12 most recent of 20 posts we hold for @pibble_official. 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.
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
@pibble_official 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.
named in 9 posts, 8 August 2026 – 13 August 2026
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“AI.PIBBLE official” (@pibble_official), 10,270 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/pibble_official.
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.