Channel
@bypzbg
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
892subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002460006417 |
|---|---|
| Type | Channel |
| Username | @bypzbg |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 30 August 2026 |
| On Telegram | t.me/bypzbg |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 01:55 | 892 | -1 |
| 15 Aug 2026, 14:58 | 893 | -1 |
| 8 Aug 2026, 04:06 | 894 | +1 |
| 8 Aug 2026, 01:04 | 893 | no change |
| 7 Aug 2026, 18:20 | 893 | first reading |
3 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 1 page 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 3 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 1 of the 3 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 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 5 August 2026 to 7 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.
省份: 浙江 城市: 杭州 年龄: 18 身高: 158 体重: 113 罩杯：C 职业: 无业 是否是chu女: 否 月生活费多少：2天4k 3天5k 可不可以口: 可 SM能不能: 不能 能不能无🍑（体检后）：可 分几次给生活费: 两次 大概姨妈日期: 12 能不能内🐍（体检后）：安全期可 有没有纹身: 无 是否可外省: 可 对老板雷点(不接受):太老太矮太丑太胖 可不可以同居: 不可 是否可过夜: 可 月可陪伴天数: 2-3天 找金主的原因:💰 自我介绍加分项： 纯傻逼女 都到酒店了 不见面 非要全款 事b女一个 满嘴跑火车 损人伤客 卖b都卖不明白 送上vx：：RichW-W901 电话 ：13221818944
省份：江西 城市：上饶 年龄：18 身高：166 体重：99 罩杯：B 职业： 大一在读 是否chu女：否 能否飞外地：能 能否CG：能 港澳通行证：有 能否过夜/同居：能 能否口：可 体检后能否无T不内： 长期可以 能否SM: 轻微m 期望月薪:3天1.5W 7天3w 每月陪伴天数：7天 自我加分项（很重要）: 会一字马钢琴没考过级 乖巧听话懂事不作不闹 介绍费: 7888 骗票妹妹 加800个聊手骗票
省份:江西 城市:上饶 年龄:18 身高:165 体重:95 罩杯:b 学历:大雪 职业:雪生 是否是chu女:否 可不可以kou:可以 能不能内s:否 能不能无t:否 SM能不能:否 有没有纹身:无 是否可外省:可以 是否可过夜:可以 可不可以同居:可以 月可陪伴天数:3天 大概姨妈日期:8 找金主的原因:缺钱 月生活费多少:1.5w 分几次给生活费:2 自我介绍加分项: 会一字马 钢琴,性格熟悉了爱撒娇 水多 对老板雷点(不接受):无 介绍费:7888 骗票妹妹
❤1
Showing the 3 most recent of 3 posts we hold for @bypzbg. 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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“包养圈I曝光I封杀” (@bypzbg), 892 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/bypzbg.
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.