Telegram RegisterThe public register of Telegram
Telegram profile photo for 瓜皮 @guapi

Channel

瓜皮 @guapi

@id0016

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

1subscribers

+0 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-1001812689879
TypeChannel
Username@id0016
Created27 February 2023measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live23 August 2026
Measurements held2
On Telegramt.me/id0016

Growth

17 August 2026 — 1 subscribers14 August 2026 — 1 subscribers7 August 202614 August 2026
2 measurements spanning 7 days. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 11:081no change
7 Aug 2026, 12:411first reading

Engagement

6 posts held, back to 27 February 2023the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 6 posts for this entry, the most recent from 5 September 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
3

Lifetime counters from Telegram’s own channel header, read 14 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.

Recent posts

15 May 2023, 15:44 UTC138 viewsread 14 August 2026

选择id宝开信用卡的10大理由! 1.开卡费低 2.没有月费(月租) 3.没有消费手续费,只有充值手续费 4.支持销毁后退卡余额,余额支持提现 5.永远免实名(免kyc) 6.无限开卡,1分钟发卡,随用随充 7.id宝隐匿在电报中,不会暴露服务器ip/域名,不存在被入侵 8.预付费虚拟信用卡充多少用多少,不怕无良商家乱扣费,不怕商家服务器被入侵或内鬼出售资料,导致信用卡被盗刷损失很多钱 9.VISA和万事卡都有,支持多种消费领域,并告知各卡头实测结果 10.不做垃圾卡头,好用卡头才会上架 ————————————————————— 10 reasons to choose idbao to open a credit card! 1. Low sign-up fee 2. No monthly fee (monthly rental) 3. There is no consumption fee, only recharge

Showing the 6 most recent of 6 posts we hold for @id0016. 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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“瓜皮 @guapi” (@id0016), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/id0016.

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.