Channel
@piggycell_announcement
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
42,514subscribers
-2,045 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002157476176 |
|---|---|
| Type | Channel |
| Username | @piggycell_announcement |
| Description | Combining hub-based charging devices and blockchain for a digital twin strategy and proposing an app-tech social game platform. - Official group chat: @piggycell_chat - Web: https://www.piggycell.io/ - X: https://x.com/piggycell |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/piggycell_announcement |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 75% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 14:42 | 42,514 | -88 |
| 16 Sept 2026, 10:39 | 42,602 | -53 |
| 14 Sept 2026, 15:37 | 42,655 | -35 |
| 12 Sept 2026, 23:17 | 42,690 | -165 |
| 11 Sept 2026, 00:39 | 42,855 | -114 |
| 8 Sept 2026, 04:20 | 42,969 | -220 |
| 5 Sept 2026, 01:58 | 43,189 | -129 |
| 3 Sept 2026, 08:33 | 43,318 | -87 |
| 1 Sept 2026, 23:09 | 43,405 | -100 |
| 31 Aug 2026, 20:56 | 43,505 | -56 |
| 30 Aug 2026, 19:25 | 43,561 | -34 |
| 29 Aug 2026, 17:23 | 43,595 | -25 |
| 28 Aug 2026, 20:03 | 43,620 | -32 |
| 27 Aug 2026, 16:27 | 43,652 | -31 |
| 26 Aug 2026, 16:13 | 43,683 | -24 |
| 25 Aug 2026, 19:22 | 43,707 | -101 |
| 24 Aug 2026, 17:35 | 43,808 | -56 |
| 23 Aug 2026, 00:59 | 43,864 | -87 |
| 21 Aug 2026, 15:16 | 43,951 | -93 |
| 20 Aug 2026, 16:12 | 44,044 | first reading |
20 posts held, back to 4 December 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 86 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 30 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 22 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.
407 reactions across 20 posts, in 18 distinct kinds. The most used accounts for 22.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👎 | 92 | 22.6% | |
| ❤ | 83 | 20.4% | |
| 💩 | 65 | 16.0% | |
| 👍 | 36 | 8.85% | |
| 🤮 | 31 | 7.62% | |
| 🤣 | 22 | 5.41% | |
| 🔥 | 18 | 4.42% | |
| 🤡 | 15 | 3.69% | |
| 👏 | 14 | 3.44% | |
| 😭 | 12 | 2.95% | |
| 😁 | 4 | 0.983% | |
| 😢 | 4 | 0.983% | |
| 😡 | 3 | 0.737% | |
| 🤔 | 3 | 0.737% | |
| 🌚 | 2 | 0.491% | |
| 😴 | 1 | 0.246% | |
| 🤷 | 1 | 0.246% | |
| 🫡 | 1 | 0.246% |
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 20 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 407 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 December 2025 to 30 June 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.
Hello, this is the Piggycell Team. It is with deep sadness that we share some difficult news. Our CEO, Jongsik Lee, who led both 충전돼지(Web2) and Piggycell(Web3), unexpectedly passed away last week following a sudden cardiac arrest while driving. This tragic loss came without warning, and our entire team is deeply saddened. We extend our sincere condolences and respectfully honor his memory. Following his sudden pass…
🔥4❤2
안녕하세요, 피기셀 팀입니다. 먼저 무겁고 안타까운 소식을 전하게 되어 진심으로 송구합니다. 그동안 충전돼지(Web2) 와 피기셀(Web3)을 이끌어 온 이종식 대표님께서 지난주 갑작스러운 급환으로 소천하셨습니다. 사인은 운전 중 심장마비이며, 예고 없이 찾아온 비보에 저희 팀 또한 큰 충격과 슬픔 속에 있습니다. 삼가 고인의 명복을 빕니다. 대표님의 갑작스러운 부재로 현재 회사 내부 상황이 평소보다 복잡한 것이 사실입니다. 최근 매도 물량이 늘어난 데에는 시장 전반의 어려움과 더불어, 이러한 내부 상황에 대한 불안감이 일부 반영된 것으로 저희는 보고 있습니다. 그 과정에서 커뮤니티 여러분께서 느끼셨을 혼란과 불안을 충분히 이해하며, 결코 가볍게 여기지 않겠습니다. 우리는 경영 공백을 막기 위해 현재 충전돼지 부대표이사의 대표이사 직무 …
👍1
Piggycell NFT Dashboard Guide is now live.🔥 📊 NFT Dashboard Explore how real infrastructure turns into on-chain rewards. • Track the NFT ecosystem • Explore regional infrastructure activity • Discover top-performing NFTs Real Usage → On-chain Data → NFT Rewards This is what Real-Usage RWA looks like. 👉 Read the full guide
🤮9😁2👍1🤣1🫡1
📢 Piggycell Weekly Update – Week 3 of January We are now in the final stage, not simply waiting, but completing the last phase of validation and recovery. Rather than rushing, we are conducting a full end-to-end final review of the entire recovery process, strengthening safeguards and ensuring every layer is fully verified to restore trust. 📄 Read full report
🤡15👎11❤8🤣8
📢 Piggycell Weekly Update – 1월 1주차 2026년 새해가 밝았습니다. Piggycell은 짧지 않은 시간을 단순한 대기가 아닌 정확함과 신뢰 회복을 위한 과정입니다. 속도보다 정밀한 점검과 더 강력한 보호 장치를 구축했고, 복구 과정 전반을 처음부터 끝까지 다시 확인했습니다. 📄 리포트 보기 👉 트위터
👎7💩4❤2
📢 Piggycell Weekly Update – Week 1 of January The new year of 2026 has begun. Piggycell has treated this period not as simple waiting, but as a process focused on precision and restoring trust. Rather than prioritizing speed, we strengthened safeguards through thorough, end-to-end reviews of the entire recovery process. 📄 Read the report 👉 Twitter
💩5🤮4👎2😡1😴1
📢 Piggycell Weekly Update – 12월 4주차 3주가 지났습니다. 짧지 않은 시간이었지만, Piggycell은 속도보다 정확함과 신뢰 회복을 우선하는 선택을 했습니다. 빠르게 처리하기보다, 더 정밀한 점검과 강력한 보호 장치를 구축하는 데 집중해 왔습니다. 2025년 마지막 주간 업데이트에서는 복구 과정을 처음부터 끝까지 다시 확인하며, 모든 단계가 올바르게 작동하도록 만드는 데 집중했습니다. 📄 리포트 보기 👉 트위터
👎4🤔2💩1
📢 Piggycell Weekly Update – Week 4 of December It has been three weeks. While it hasn’t been a short period, Piggycell chose to prioritize precision and trust recovery over speed. Rather than rushing forward, we focused on thorough reviews and reinforcing stronger safeguards. For the final weekly update of 2025, we revisited the entire recovery process from start to finish, ensuring that every step functions as int…
👍4👎2🤷1
📢 Piggycell Weekly Update - Week3 of December Piggycell’s Weekly Report is now live on Medium. This report summarizes the key actions and progress made since the recent incident. To ensure transparency and reduce information gaps, Piggycell has been publishing official Weekly Reports on a consistent basis, providing verified updates directly from the team. 🗓 The Weekly Report is released every Friday and focuses o…
👎20🔥6❤2💩1
보안사고 복구계획 및 토큰 마이그레이션계획 안내 이번 사고로 인해 홀더 여러분께 심리적 부담과 재정적 손실을 안겨드린 점에 대해 진심으로 사과드립니다. 현재까지 확인된 내용과 향후 대응계획을 공유드립니다. 온체인 데이터 및 거래소 기록을 교차 검토한 결과, 20,000,000 PIGGY 토큰이 부정 발행되었으며, 개인키가 탈취되는 사고로 인해 총 20,312,298 PIGGY가 시장에 유출된 사실을 확인했습니다. 프로젝트의 최우선 목표는 명확합니다. 홀더보호, 재발방지, 그리고 시스템 안정성회복입니다. 이 과정 전반에 걸쳐 바이낸스와 긴밀히 협력하고 있으며, 컨트랙트 구조와 운영 통제 전반을 재설계하는 과정에서 바이낸스 기준에 부합하는 보안 가이드를 반영하고 있습니다. ⚡️ 향후 진행 계획 ✔️ 신규 컨트랙트 배포 및 보안 구조 재설계…
❤7💩5🤔1
Security Incident Recovery Plan & Token Migration We want to sincerely apologize for the stress and losses this incident has caused our holders. Here’s what we’ve confirmed so far and how we’re moving forward. After reviewing on-chain and exchange data, we confirmed that 20,000,000 $PIGGY was illegitimately minted, and due to compromised private keys, a total of 20,312,298 $PIGGY was released into the market. Our …
👏13❤4👎4💩3😁1
안녕하세요, Piggycell 팀입니다. 먼저, 현재 마련된 복구 방안은 각 거래소 및 관련 파트너사들과 최종 조율 단계에 있으며, 모든 절차가 승인되는 즉시 커뮤니티 여러분께 가장 신속하고 정확하게 안내드릴 것을 약속드립니다. 현재 프로젝트의 최우선 목표는 동일한 사고가 발생하지 않도록 보안 구조를 전면 재설계하는 것, 그리고 실질적인 피해를 입은 홀더분들을 중심으로 공정하게 책임을 다하는 것입니다. 이러한 원칙을 바탕으로 전체 복구 플랜을 준비하고 있으며, 구체적인 일정역시 파트너사 및 거래소와의 협의가 마무리되는 대로 공식 채널을 통해 상세히 안내드릴 예정입니다. 이번 해킹 사고로 인해 불편과 우려를 드린 점 진심으로 사과드립니다. 현재 팀은 시스템 정상화와 신뢰 회복을 위해 최선의 노력을 다 하고있습니다. 감사합니다. Pigg…
👍12❤5🤣4💩3🌚2👏1
Showing the 12 most recent of 20 posts we hold for @piggycell_announcement. 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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Piggycell News and Updates” (@piggycell_announcement), 42,514 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/piggycell_announcement.
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.