https://t.me/smss?start=spread_8013897256
Channel
04SM捆绑虐待强奸
@cgjxxgjjjbvvg
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
2,815subscribers
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1004368834816 |
|---|---|
| Type | Channel |
| Username | @cgjxxgjjjbvvg |
| Description | 完整版 https://t.me/smyhqbot |
| Created | Between 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 1 |
| On Telegram | t.me/cgjxxgjjjbvvg |
Growth
Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 22:22 | 2,815 | first reading |
Engagement
20 posts held, back to 13 September 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.
- ERR · 30 days
- 2.58%
- avg views ÷ 2,815 subscribers
- Avg views / post
- 72.8
- 20 posts measured
- Reaction rate
- 0%
- reactions ÷ views · ER floor
- Posts in window
- 20
- of 20 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 1 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 18 September 2026 |
|---|---|
| Posts held | 20 (13 September 2026 – 18 September 2026) |
| Views total | 1,455 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Sept 2026, 22:22 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
- Photos
- 5
- Videos
- 75
- Links
- 5
Lifetime counters from Telegram’s own channel header, read 18 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.
- Video runtime
- 31m 44s
- Average length
- 1m 59s
Measured directly from 16 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.
Recent posts
🔥TeleTop 频道推荐 📢西安 小四精选洗浴全套会所 📢ASMR 📢苏州SPA/苏州修车/苏州半套/苏州会所 📢长沙GT俱乐部·公开榜 📢深圳 95/96 休闲 SPA 会所|便... 📢💋💋精品AV无码丝袜恋足制服 📢全国外围/学生/呦女约💋 📢石家庄上门约 📢泸州~外围兼职-精选 📢中文字幕 | 日本AV❤️ 💎广告推荐 📢🔰开元官方🔥代理70%|电子棋牌|A... 📢诚邀各类代理丨收单推广团队丨SEO劫持等... 📢🅾️AG官网直营✅大客必备✅注册送15... 🔍互推公示 🪧流量互推说明
来自速搜推荐 @SSOU 📢性感|比基尼|泳装|韩国... 📢郑州性感小野猫 📢亚星私网🅰️欧博私网�... 📢泸州~外围兼职-精选 📢欧博代理 欧博私网 亚星... 📢欧博官网 亚星官网 欧博... 📢皇冠足球 欧博代理 欧博... 📢皇冠私网🅰️138彩票... 📢皇冠网址|皇冠开户|皇冠... 📢(汕头)外围兼职精选 📢真人百家乐 百家乐代理 ... 📢裸舞 x🈲 抖音🫵主... 📢欧博私网|亚星私网|利博... 📢热点曝光台 📢欧博代理|亚星代理|欧博... 👉流量互推规则介绍💥 以下是广告推荐 📢🔥最强平台强势来袭,掀起智能合约新风暴! 🔥 📢🅾️免费试玩✅大客必备✅注册送158🅾️ 📢💎 【8.cc】U投领导者 千万域名 百亿大盘 充值笔笔加赠3% 📢⚽️注册送138🧧百家乐/棋牌/电竞体育信誉平台 🥇2G.COM 品牌定位全球 实力超乎想象 🇨🇳 简体中文包 —————————-- 🔥将 @TonGrou…
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
完整版 @smyhqbot Lolita女孩的脚镣日常-新到的脚镣和新任务
完整版 @smyhqbot 捆绑女大
完整版 @smyhqbot 《黑吃黑2》
完整版 @smyhqbot 高挑妹子直臂吊杆固定缚--旗袍、丝袜、高跟、TK、电击
完整版 @smyhqbot 橘子紧缚献舞……曾经的空乘168完美身材的橘子,绳瘾发做怎么办?紧
完整版 @smyhqbot 被邻居妹妹色诱,大门敞开勾引邻居,只好让她如愿带走调教强制GC
完整版 @smyhqbot 丰满女大学生超多绳子柱子缚+牢笼体验+郊狼+丝巾堵嘴
完整版 @smyhqbot 80多斤女学生被制成人体家具椅,郊狼+炮机+AV棒组合,超级折磨套餐,
Showing the 12 most recent of 20 posts we hold for @cgjxxgjjjbvvg. 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.
Forward network
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.
@TeleTopOrg · 34,0912 posts🅾️博彩信誉网站🅾️
@AGBCA · 60,4281 post皇冠足球 欧博代理 欧博私网 亚星私网
@Aibiansheng_773 · 1,6091 post深圳 95/96 休闲 SPA 会所|便捷预约
@baiheqin8 · 20,6541 post💋💋精品AV无码丝袜恋足制服
@feiyang990611 · 1,7131 post♨️尊龙凯时♨️尊龙官网♨️博天堂官网♨️918博天堂♨️百家乐官网♨️捕鱼官网♨️PG直营♨️PG官网♨️电子官网♨️世界杯直播♨️
@GATG8 · 9,4501 post性感|比基尼|泳装|韩国女团|车模
@greenplanetbbc · 2,5171 post裸舞 x🈲 抖音🫵主播
@gtkankan10422 · 2,8171 post皇冠网址|皇冠开户|皇冠客服|皇冠正网|皇冠正盘
@huangguanxzm · 1,0071 post郑州性感小野猫
@jcghwqre · 1,0471 post☁️开云体育官方🏆开云招商 匡
@kyzsklz · 62,2201 post长沙GT俱乐部·公开榜
@mmdbxx2 · 3,5821 post石家庄上门约
@osyilponyn · 1,1981 post真人百家乐 百家乐代理 欧博百家乐 亚星百家乐 利博百家乐
@ouboaay · 1,9421 post欧博代理 欧博私网 亚星代理 亚星私网
@ouboxxw · 1,9501 post欧博私网|亚星私网|利博私网|欧博包杀|利博包杀
@oubozai · 1,0101 post欧博代理|亚星代理|欧博网址|亚星网址
@oubozxt · 1,0061 post热点曝光台
@SEA999NEWS · 1,5171 post苏州SPA/苏州修车/苏州半套/苏州会所
@szbths · 901 post速搜❤️🔥流量互推/广告交易
@TonAdNews · 11,5401 post西安 小四精选洗浴全套会所
@XAXSXY · 5,6581 post皇冠私网🅰️138彩票信用网🅰️利博私网🅰️亚星欧博
@yaxingdailicc · 1,0531 post(汕头)外围兼职精选
@yiyinqyqnn · 1,3301 post全国外围/学生/呦女约💋
@younvdkesong · 551 post
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@cgjxxgjjjbvvg named 1 handle 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 19 September 2026 – 19 September 2026
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“04SM捆绑虐待强奸” (@cgjxxgjjjbvvg), 2,815 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/cgjxxgjjjbvvg.
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.