Channel
@bydb_gq
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
518subscribers
-149 since we began measuring on 9 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003940131364 |
|---|---|
| Type | Channel |
| Username | @bydb_gq |
| Created | Between 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 October 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/bydb_gq |
Adult — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 28 October 2026 and assigned it the closest of 31 fixed categories, at 57% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 10:35 | 518 | -33 |
| 28 Oct 2026, 06:27 | 551 | -22 |
| 20 Oct 2026, 22:16 | 573 | -108 |
| 13 Oct 2026, 08:38 | 681 | +14 |
| 9 Oct 2026, 13:22 | 667 | no change |
| 9 Oct 2026, 12:47 | 667 | first reading |
4 posts held, back to 4 October 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 4 posts for this entry, the most recent from 9 October 2026. 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.
🍓【 𝐒𝐄𝐎𝐔𝐋 · 温柔似水】🍓 🎂 03年 168D 88斤 🥛 皮肤雪白滑嫩无瑕疵 👱♀️ 柔情似水 初恋女友感 💖 独家体验 💖 🍭 善解人意 理想女友 #首尔外围 #首尔高端 #首尔上门 #首尔伴游 #韩国外围 #首尔 #韩国 #日韩 新客户请先看置顶下单流程 糖心集团包养选妃： @tangxin_by 糖心选妃高端外围： @bydb_bb 糖心女孩快餐包夜： @tangxin_girl 糖心集团中转站： @bydbjituan 糖心集团药品： @BYDBfankui 糖心集团幼幼转运珠： @bydb_kf 糖心1V1学生裸聊：@bydb_gg 糖心反差少妇： @zhaonanmo 糖心明星网红： @haowangfaAV 海外包夜包养： @haiwaibaoyang789 糖心客户反馈： @haowangfafankui 糖心集团 月儿 @bydb_01 糖心集团 V姐 @bydb_02 糖心集团 菜菜 @by…
🔥包夜 night 🔥 no.b629 📍地点 location：#上海 #Shanghai 🇨🇳 🍜快餐 quick 1 hr🥢：8000 人 🀄️ 🌙包夜 night 6–8 hrs✌️：1 万 人 🀄️ ✨ 一本本科｜体制内在职教师（可查）｜高中数学教资 🇰🇷 自学韩语｜做过韩国男团活动韩语翻译与接待 🎹 钢琴｜绘画｜烹饪｜健身 🐶 ENFP｜温柔开朗｜活泼｜喜欢小动物 ✨ 不抽烟｜不喝酒｜无纹身｜无整容 #韩国 #日韩 #10000以内 新客户请先看置顶下单流程 糖心集团包养选妃： @tangxin_by 糖心选妃高端外围： @bydb_bb 糖心女孩快餐包夜： @tangxin_girl 糖心集团中转站： @bydbjituan 糖心集团药品： @BYDBfankui 糖心集团幼幼转运珠： @bydb_kf 糖心1V1学生裸聊：@bydb_gg 糖心反差少妇： @zhaonanmo 糖心明星网红： @haowangf…
———生活助理Life Assistant——— no. mm953 🦋国籍Nationality？ 中国 🦋年龄Age？ 21 🦋身高Height？ 170 🦋体重Weight？ 47 🦋目前的地方Current place？ #国内 🦋可以去哪里 where can go? 中东迪拜周边 新加坡 日本 欧洲各地 🦋语言Language? 中文 英语 🦋希望的工资Expected salary? 周8万人 🦋备注remark：新人 没有做过 #新加坡 #日本 #迪拜 #洛杉矶 #日韩 #50000以上 新客户请先看置顶下单流程 糖心集团包养选妃： @tangxin_by 糖心选妃高端外围： @bydb_bb 糖心女孩快餐包夜： @tangxin_girl 糖心集团中转站： @bydbjituan 糖心集团药品： @BYDBfankui 糖心集团幼幼转运珠： @bydb_kf 糖心1V1学生裸聊：@bydb_gg 糖心反差少妇…
省份:日本 城市:东京 年龄:18 身高:162 体重:86 罩杯:B➕ 雪历:本科 工作还是雪生:雪生 职业: 是否chu女:否 能不能口:🉑 能不能内射:否 SM能不能:🉑轻微 有没有纹身:🈚 是否抽烟:否 是否可外省:🉑 是否可村外:🉑（周5,2） 是否可过夜: 🉑 每月可陪伴天数:3 7 期待零花钱:2.5 5.2 分（2-4）次给零花钱:2-3 自我介绍加分项: 很听话 雪生 皮肤白有腰窝，会提供情绪价值女友感，可以玩Cos做爱 对老板雷点(不接受):🈚 介绍费:7888 #日本 #东京 #日韩 #10000以内 新客户请先看置顶下单流程 糖心集团包养选妃： @tangxin_by 糖心选妃高端外围： @bydb_bb 糖心女孩快餐包夜： @tangxin_girl 糖心集团中转站： @bydbjituan 糖心集团药品： @BYDBfankui 糖心集团幼幼转运珠： @bydb_kf 糖心1V1学生裸聊：@bydb…
Showing the 4 most recent of 4 posts we hold for @bydb_gq. 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 6 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.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“糖心集团日本、韩国妹妹” (@bydb_gq), 518 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/bydb_gq.
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.