庆祝频道人数45k 给大家发一个红包

Channel
汉堡追锁
@hb52066
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
45,393subscribers
-119 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1002830772773 |
|---|---|
| Type | Channel |
| Username | @hb52066 |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/hb52066 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 05:07 | 45,393 | -47 |
| 12 Aug 2026, 02:32 | 45,440 | +8 |
| 11 Aug 2026, 04:44 | 45,432 | -36 |
| 10 Aug 2026, 07:12 | 45,468 | -37 |
| 9 Aug 2026, 09:51 | 45,505 | -7 |
| 8 Aug 2026, 18:00 | 45,512 | first reading |
Engagement
81 posts held, back to 5 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 14 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.976%
- avg views ÷ 45,393 subscribers
- Avg views / post
- 443
- 78 posts measured
- Reaction rate
- 1.45%
- reactions ÷ views · ER floor
- Posts in window
- 81
- of 81 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. It is computed over the 75 of 78 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 81 (5 August 2026 – 12 August 2026) |
| Views total | 34,570 |
| Reactions total | 483 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 21:40 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
- 2m 40s
- Average length
- 27s
Measured directly from 6 videos 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
483 reactions across 71 posts, in 6 distinct kinds. The most used accounts for 92.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 448 | 92.8% | |
| ❤ | 23 | 4.76% | |
| 🔥 | 8 | 1.66% | |
| 🥰 | 2 | 0.414% | |
| 🌭 | 1 | 0.207% | |
| 🤩 | 1 | 0.207% |
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 75 of the 81 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 483reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 81 most recent posts we hold, published 5 August 2026 to 12 August 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
🧧红包发送成功🧧 🔥蚂蚁MaYi 发送了 一个红包! 💵总金额: 1888 U🪙 🚦剩余: 68/88 🥇 88.88 USDT - 小小心意…. 🥈 78.26 USDT - 国王 🥉 68.61 USDT - 好你哦
🐶15岁少萝在别墅被7位金主爸爸內射到sao穴 轮奸再一个个粗壮的肉棒的蹂躏下小穴被干的通红 曾多次高潮尿失禁 避孕套都用光了几盒视频
👍5
汉堡提卡链接 https://luoye.chyidc.cn/shop/xiaoyu
👍2❤1
内核里面最全面的内核 汉堡内核下单 https://luoye.chyidc.cn/shop/luoye
👍12🔥1
🚀 New Update #Game和平 Game和平 Update: ✔️新增陀螺仪自瞄灵敏度自适应适完完全全自动不需要点击了 ✔️灵敏度自适应刷新改为了完完全全自动的不需要去点击了 ✔️解决了自瞄的一些bug ✔️修复自瞄温馨提示没有适配横屏模式问题导致卡屏出现 ✔️解决自瞄追踪圈莫名其妙变大问题 ✔️新增开启洗头模式追踪自动打开 ✔️新增雷达优化项{ 1.在无人的时候不会显示雷达避免挡视野 } ✔️适配市面上所有的驱动基本上99.9%淋雨的驱动需要等今天他发我密钥所以你们可能连接不上 ✔️新增背敌预警or雷达绘制加入玩家掩体判断功能,可以在绘制设置里的颜色设置修改颜色 ✔️适配地铁模式的所有宝箱包括古墓模式 ✔️修复用户所反馈的所有bug 更新网盘: https://wwbll.lanzoul.com/b01883ijhg 密码:6666 tips:可以一键获取配置,还有一些其他的可玩性功能你们可以自行研究如迫击炮…
👍13🔥1
Photo, posted without a caption
👍7
Photo, posted without a caption
👍6
Photo, posted without a caption
👍5❤1
Photo, posted without a caption
👍7
Photo, posted without a caption
👍8
Photo, posted without a caption
👍7
Showing the 12 most recent of 81 posts we hold for @hb52066. 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
Citation-graph rank — 543,793 of 1,160,990entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“汉堡追锁” (@hb52066), 45,393 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/hb52066.
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.