快粉互推助手【频道C1】 1. 菲菲裸聊馆~超多骚逼妹妹在线等你来💋💋💋 2. 萝莉御姐足控菲菲裸聊馆都可满足~超多妹妹任你挑选处置👄👄👅👅 3. 日本无码av【强奸破坏版】 4. 柏林引流|Telegram引流增粉|Telegram频道运营|Telegram涨粉技巧|推广方法 5. 芯欣裸聊馆1v1👅语音视频💋磕炮裸聊👄性格御姐可爱少萝 6. 柏林引流|Telegram引流增粉|Telegram频道运营|Telegram涨粉技巧|推广方法 7. 男模/异性SPA/男技师与富婆私密趣事🔞 8. 💯💯[信诚香烟]💎💎信誉品牌坚信可靠 9. 骚气蓬勃生机妹妹在线裸聊一对一 10. 素材馆-美食-美景~自拍旅游 11. Telegram增长指南 12. 娟姐真实约炮 13. 菲菲裸聊馆👅超多大胸妹妹 14. 西瓜色漫剧场 15. 肤白貌美大长腿女大学生在线裸聊~菲菲裸聊馆 16. 抖音反差群 17. 眼镜婊反差视频 18. 酒店监控…

Channel
💯百万ts伪娘养成计划
@QLXGC667
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
5,273subscribers
+15 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1003719417344 |
|---|---|
| Type | Channel |
| Username | @QLXGC667 |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/QLXGC667 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 03:01 | 5,273 | +15 |
| 10 Aug 2026, 09:00 | 5,258 | first reading |
Engagement
21 posts held, back to 9 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 3 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.452%
- avg views ÷ 5,273 subscribers
- Avg views / post
- 23.9
- 21 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 21
- of 21 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.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 21 (9 August 2026 – 12 August 2026) |
| Views total | 501 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 05:39 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
- 92
- Videos
- 87
- Links
- 9
Lifetime counters from Telegram’s own channel header, read 12 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.
- Video runtime
- 2h 05m
- Average length
- 15m 44s
Measured directly from 8 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
🚀️能量互推-D4车🚀 AD: TRX供应/能量租赁 1:AI动漫视频放映室 2:国女媚黑黑人 3:高中生初夜轮奸~菲菲裸聊馆一对一裸聊 4:萝莉御姐足控菲菲裸聊馆都可满足~超多妹妹任你挑选处置👄👄👅👅 5:麟烟阁TS伪娘人妖肛交 6:电报频道群组资源 7:口爆颜射大奶子母狗 8:口爆口交颜射 9:💯百万ts伪娘养成计划 10:新澳门六合#资料免费公开 11:高颜值美女口爆 12:鱼刺日本AV-全中字 13:口交颜射小母狗 14:【每日学生】精选收藏夹 15:黄果Ai动漫更新❕ 16:菲菲裸聊馆👅超多大胸妹妹 AD: 中文搜索/超级引搜/飞机搜索 AD: 广告位招商
一个很邪恶的频道 未满十八岁禁止入内 🚀来自百度互推【 D5 】组🚀 1. bdsm高质量调教群 2. 男技师/富婆/探花/异性SPA/私密视频㊙️ 3. 🔞J•【裸聊馆】射不出来算我的🔞 4. ❤️印度日本等海外进口药丨🇮🇳专业印度性药丨源头供应丨正品保证|靶向抗癌|迷药(诚招代理) 5. 伪娘TS👒人妖🧕🏻大屌妹妹 6. 裸贷裸条肉偿大学生曝光 7. 菲菲裸聊极品妹妹包涩 8. 满级服务听话妹妹1v1裸聊 9. 【麟烟阁】TS伪娘学院 10.嘉嘉❤️线上 裸聊一对一视频 听话听指挥欲女 11.光年-抖音粉丝小红书粉丝快手粉丝抖音点赞微博数据快手视频号涨粉 12.【深绿文化】绿帽人妻出轨NTR 13.💯百万ts伪娘养成计划 😍一个很牛逼的频道 限时免费开放 👙失足少女求调教(人妻被逼出轨😍) 💋性瘾少女嫩穴想被插入😍
天眼互推【频道C1】 1. 中文字幕 | 日本AV即是正义! 2. 鱼刺日本AV-全中字 3. 日本好片无码AV高颜值FC2 4. 日本无码av(强奸破坏版) 5. 柏林引流|Telegram引流增粉|Telegram频道运营|Telegram涨粉技巧|推广方法 6. 柏林引流|Telegram引流增粉|Telegram频道运营|Telegram涨粉技巧|推广方法 7. 💖中文字幕日本AV合集💖 8. 微密圈|觅圈|密语空间 🔥优质广告位招商
一个很邪恶的频道 未满十八岁禁止入内 🚀来自百度互推【 D5 】组🚀 1. bdsm高质量调教群 2. 男技师/富婆/探花/异性SPA/私密视频㊙️ 3. 🔞J•【裸聊馆】射不出来算我的🔞 4. ❤️印度日本等海外进口药丨🇮🇳专业印度性药丨源头供应丨正品保证|靶向抗癌|迷药(诚招代理) 5. 伪娘TS👒人妖🧕🏻大屌妹妹 6. 裸贷裸条肉偿大学生曝光 7. 菲菲裸聊极品妹妹包涩 8. 满级服务听话妹妹1v1裸聊 9. 【麟烟阁】TS伪娘学院 10.嘉嘉❤️线上 裸聊一对一视频 听话听指挥欲女 11.光年-抖音粉丝小红书粉丝快手粉丝抖音点赞微博数据快手视频号涨粉 12.【深绿文化】绿帽人妻出轨NTR 13.💯百万ts伪娘养成计划 😍一个很牛逼的频道 限时免费开放 👙失足少女求调教(人妻被逼出轨😍) 💋性瘾少女嫩穴想被插入😍
天眼互推【频道C1】 1. 中文字幕 | 日本AV即是正义! 2. 柏林引流|Telegram引流增粉|Telegram频道运营|Telegram涨粉技巧|推广方法 3. 💖中文字幕日本AV合集💖 4. 柏林引流|Telegram引流增粉|Telegram频道运营|Telegram涨粉技巧|推广方法 5. 日本无码av(强奸破坏版) 6. 微密圈|觅圈|密语空间 7. 鱼刺日本AV-全中字 8. 日本好片无码AV高颜值FC2 🔥优质广告位招商
🚀️能量互推-D2车🚀 AD: TRX供应/能量租赁 1:【色欲阁】精神小妹粉嫩萝莉 2:Telegram增长指南 3:中文字幕 | 日本AV即是正义! 4:高颜值美女口爆 5:黄漫❗成人动漫大全❗ 6:智能ai 7:💯百万ts伪娘养成计划 8:🔥Ai动漫视频 9:激情四射免费在线匹配裸聊一对一❤️❤️❤️ 10:电报热门资源 11:Ai成人短剧| Ai动漫🔞 12:【每日学生】精选收藏夹 13:酒店监控偷拍 14:25年最新女大少妇|裸贷资料 15:口爆口交颜射 16:❤️ 18+ 反差 母狗 泄露 🐶 AD: 中文搜索/超级引搜/飞机搜索 AD: 广告位招商
快粉互推助手【频道C1】 1. ️✨东南亚大事件️_无广告_评论抽TRX版 2. 柏林引流|Telegram引流增粉|Telegram频道运营|Telegram涨粉技巧|推广方法 3. 酒店监控 4. 萝莉御姐足控菲菲裸聊馆都可满足~超多妹妹任你挑选处置👄👄👅👅 5. 骚货小妹妹多种道具轮流裸聊~菲菲裸聊馆 6. 素材馆-美食-美景~自拍旅游 7. 日本无码av【强奸破坏版】 8. 柏林引流|Telegram引流增粉|Telegram频道运营|Telegram涨粉技巧|推广方法 9. 菲菲裸聊馆~超多骚逼妹妹在线等你来💋💋💋 10. 抖音反差群 11. 芯欣裸聊馆1v1👅语音视频💋磕炮裸聊👄性格御姐可爱少萝 12. 菲菲裸聊馆👅超多大胸妹妹 13. Telegram数字生活指南 14. 男模/异性SPA/男技师与富婆私密趣事🔞 15. 肤白貌美大长腿女大学生在线裸聊~菲菲裸聊馆 16. 💯💯[信诚香烟]💎💎信誉品牌坚信可靠 1…
一个很邪恶的频道 未满十八岁禁止入内 🚀来自百度互推【 D5 】组🚀 1. bdsm高质量调教群 2. 男技师/富婆/探花/异性SPA/私密视频㊙️ 3. 🔞J•【裸聊馆】射不出来算我的🔞 4. ❤️印度日本等海外进口药丨🇮🇳专业印度性药丨源头供应丨正品保证|靶向抗癌|迷药(诚招代理) 5. 伪娘TS👒人妖🧕🏻大屌妹妹 6. 裸贷裸条肉偿大学生曝光 7. 菲菲裸聊极品妹妹包涩 8. 满级服务听话妹妹1v1裸聊 9. 【麟烟阁】TS伪娘学院 10.嘉嘉❤️线上 裸聊一对一视频 听话听指挥欲女 11.光年-抖音粉丝小红书粉丝快手粉丝抖音点赞微博数据快手视频号涨粉 12.【深绿文化】绿帽人妻出轨NTR 13.💯百万ts伪娘养成计划 😍一个很牛逼的频道 限时免费开放 👙失足少女求调教(人妻被逼出轨😍) 💋性瘾少女嫩穴想被插入😍
快粉互推助手【频道C1】 1. 中文资源导航合集 2. Telegram数字生活指南 3. 骚货小妹妹多种道具轮流裸聊~菲菲裸聊馆 4. 【涩盟】TS伪娘可爱男娘完整合集 5. 西瓜色漫剧场 6. 酒店监控 7. 眼镜婊反差视频 8. 日本无码av【强奸破坏版】 9. 柏林引流|Telegram引流增粉|Telegram频道运营|Telegram涨粉技巧|推广方法 10. 男模/异性SPA/男技师与富婆私密趣事🔞 11. 柏林引流|Telegram引流增粉|Telegram频道运营|Telegram涨粉技巧|推广方法 12. 💯💯[信诚香烟]💎💎信誉品牌坚信可靠 13. 骚气蓬勃生机妹妹在线裸聊一对一 14. 芯欣裸聊馆1v1👅语音视频💋磕炮裸聊👄性格御姐可爱少萝 15. 娟姐真实约炮 16. 萝莉御姐足控菲菲裸聊馆都可满足~超多妹妹任你挑选处置👄👄👅👅 17. 抖音粉丝小红书粉丝快手粉丝抖音刷粉小红书买粉快手涨粉点赞 18.…
天眼互推【频道C1】 1. 微密圈|觅圈|密语空间 2. 中文字幕 | 日本AV即是正义! 3. 💖中文字幕日本AV合集💖 4. 鱼刺日本AV-全中字 5. 日本好片无码AV高颜值FC2 6. 柏林引流|Telegram引流增粉|Telegram频道运营|Telegram涨粉技巧|推广方法 7. 柏林引流|Telegram引流增粉|Telegram频道运营|Telegram涨粉技巧|推广方法 8. 日本无码av(强奸破坏版) 🔥优质广告位招商
🚀️能量互推-D3车🚀 AD: TRX供应/能量租赁 1:海角社区丨熟女乱交 2:💯百万ts伪娘养成计划 3:智能ai 4:酒店监控偷拍 5:动漫里番二次元 6:Telegram增长指南 7:柏林引流|Telegram引流增粉|Telegram频道运营|Telegram涨粉技巧|推广方法 8:嘉嘉❤️线上 裸聊一对一视频 听话听指挥欲女 9:日本AV 中文字幕 10:🔥Ai动漫视频 11:25年最新女大少妇|裸贷资料 12:娟姐真实约炮 13:菲菲裸聊馆~超多骚逼妹妹在线等你来💋💋💋 14:高中生初夜轮奸~菲菲裸聊馆一对一裸聊 15:口交颜射小母狗 16:学生反差白虎系列 AD: 中文搜索/超级引搜/飞机搜索 AD: 广告位招商
Showing the 12 most recent of 21 posts we hold for @QLXGC667. 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 — 920,190 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.
Mentions
Named by 3 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.
Handles this channel named that no longer answer
- Dead references
- 6
- 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
- 6
- vacant every time we have ever looked
@QLXGC667 named 6 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 3 posts, 11 August 2026 – 13 August 2026
named in 3 posts, 11 August 2026 – 13 August 2026
named in 3 posts, 11 August 2026 – 13 August 2026
named in 3 posts, 11 August 2026 – 13 August 2026
named in 3 posts, 11 August 2026 – 13 August 2026
named in 3 posts, 11 August 2026 – 13 August 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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“💯百万ts伪娘养成计划” (@QLXGC667), 5,273 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/QLXGC667.
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.