Channel
@pu229
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
4,185subscribers
+30 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002529755770 |
|---|---|
| Type | Channel |
| Username | @pu229 |
| Created | 24 March 2025 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/pu229 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 07:04 | 4,185 | +32 |
| 8 Aug 2026, 04:55 | 4,153 | -2 |
| 7 Aug 2026, 18:18 | 4,155 | first reading |
6 posts held, back to 24 March 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 3 pagesof 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 1 April 2025. An engagement rate over an empty window would be a number about nothing.
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.
1,996 reactions across 3 posts, in 13 distinct kinds. The most used accounts for 27.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 556 | 27.9% | |
| 👍 | 264 | 13.2% | |
| 🔥 | 239 | 12.0% | |
| 🤩 | 239 | 12.0% | |
| 👏 | 238 | 11.9% | |
| 🥰 | 229 | 11.5% | |
| 🎉 | 209 | 10.5% | |
| 😁 | 9 | 0.451% | |
| 🫡 | 4 | 0.2% | |
| 😈 | 3 | 0.15% | |
| 🌚 | 2 | 0.1% | |
| 👎 | 2 | 0.1% | |
| 😇 | 2 | 0.1% |
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 3 of the 6 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,996reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 24 March 2025 to 1 April 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
👉🏻灰产吃瓜 @Sviprr 👉🏻吃瓜曝光 @Xocow 👉🏻东南亚大新闻 @Bc716 👉🏻安危事件 @Svipzz 👉🏻新闻大爆炸 @bc721 👉🏻东南亚情报网 @bc725 ❤️求职招聘 @uozzo 😮吃瓜美女 @oevey 😮吃瓜群众 @cg776 😮吃瓜搞笑 @cga33 😮吃瓜群众 @Ton5c 😮色色吃瓜 @Eysiy 😮吃瓜搞笑 @cg776 😘欧美 @uowem 😘日本 @Obcos 😘…
❤157👍85🔥84👏83🤩82🎉70🥰70😁3
表情包合集 https://t.me/addstickers/Svipzz https://t.me/addstickers/Svipzz1 https://t.me/addstickers/Svipzz2 https://t.me/addstickers/Svipzz3 https://t.me/addstickers/Svipzz4 https://t.me/addstickers/Svipzz5 https://t.me/addstickers/Svipzz6 https://t.me/addstickers/Svipzz7 https://t.me/addstickers/Svipzz8 https://t.me/addstickers/Svipzz9 https://t.me/addstickers/Svipzz10 https://t.me/addstickers/Svipzz11 http…
❤229👍101🔥89🤩85👏80🥰76🎉72😁6
解除对 iOS 端成人色情内容的限制 ➊登录Telegram web网页版 链接： https://web.telegram.org/ ❷点击左上角菜单 (三横) 依次点击Settings(设置) → Privacy and Security(隐私与安全) → 打钩选项Disable filtering(禁用筛选) ❸划掉iOS端Telegram软件后台，重新打开软件即可。 ios客户端被限制看色情频道与群组 用手机解决方法 Telegram web网页版链接： https://web.telegram.org/ ⚡️操作： 登录WEB网页版后 ➊点击「Settings/设置」 ➋把 Show Sensitive Content 打开 ➌重启 iOS 客户端即可。 或者 登录PC客户端，下载地址： https://desktop.telegram.org ➊点击「Settings/设置」 ➋点击「Privacy and S…
❤170🥰83👍78👏75🤩72🎉67🔥66😇2
Channel name was changed to «频道合集»
Channel name was changed to «@pu229»
Channel created
Showing the 6 most recent of 6 posts we hold for @pu229. 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 — 466,589 of 1,151,006entries 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.
Named by 7 registered channels — 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.
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.
@pu229 named 2 handles 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.
References a handle that is not a live channel — we have no record it ever was one.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“频道合集.防封中专” (@pu229), 4,185 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/pu229.
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.