Channel
@fb9822
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
107subscribers
-8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002836735680 |
|---|---|
| Type | Channel |
| Username | @fb9822 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/fb9822 |
Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 26 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Oct 2026, 00:01 | 107 | -1 |
| 10 Sept 2026, 00:20 | 108 | -4 |
| 24 Aug 2026, 13:24 | 112 | -1 |
| 15 Aug 2026, 20:58 | 113 | -1 |
| 9 Aug 2026, 05:47 | 114 | no change |
| 8 Aug 2026, 13:17 | 114 | -1 |
| 7 Aug 2026, 19:02 | 115 | first reading |
9 posts held, back to 15 July 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 9 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
🌈Line：mt160/bk638 🌈Gleezy：mt160 🌈Telegram：@mt1689 營業時間： 13:00~4:00 📌商城下次Gleezy選妃交流群組：https://c.gleezy.top/4nuZaI0L 🍀北部專區：@mt1678 🍀中部專區：@mt03344 🍀南部專區：@mt16890 🍀新竹專區：@mt1650 🍀學生妹18~22歲：@mt16990 🍀大奶巨乳熟女：@mt16789 🍀人妻熟女專區：@mt5271 #台灣外送茶 #台灣出差找小姐 #高檔茶 #學生妹試車 #旅館一夜情 #口碑茶 #無套內射 #巨乳
Signed 人間小甜甜🇹🇼蜜蜜
楊慧雯 165 / 52 / Ccup/ 40歲 #房仲業務 纖細美腿誘人 黑絲讓你蠢蠢欲動高潮口技 讓不少哥哥甘拜下風床上功夫 值得新老司機都來體驗看看 絕對讓是榨汁機本機喔 熱綫⤵️⤵️⤵️⤵️⤵️· Telegram蜜蜜賬號：jkf0077 Telegram小甜甜賬號：@book166 🍀北部喝茶班表：@jkfa288 🍀中部喝茶班表： @jkfa147 🍀南部喝茶班表： @jkfa269 🍀學生妹18~22歲：@jkf247 🍀熟女人妻大奶區：@jkfa366 🍀特別重口味專區：@jkfq963
Signed 人間小甜甜🇹🇼蜜蜜
玉珊 161cm / 49kg / D杯 / 41歲 肉感豐潤的白嫩熟女 皮膚滑嫩彈性十足，床上很會叫又主動 特別懂男人敏感點，喜歡激烈體位 騎乘時蜜穴又緊又會夾，爽感超強 #熟女 #台灣找小姐 #現金消費 #出差找約 熱綫⤵️⤵️⤵️⤵️⤵️ 💗Gleezy：jkf0077 💗Line：rely168 💗私密蜜蜜TG：@jkf0077 🍀北部喝茶班表：@jkfa288 🍀中部喝茶班表： @jkfa147 🍀南部喝茶班表： @jkfa269 🍀學生妹18~22歲：@jkf247 🍀熟女人妻大奶區：@jkfa366 🍀特別重口味專區：@jkfq963
Signed 人間小甜甜🇹🇼蜜蜜
小雲163cm 50kg F奶 32歲 淫蕩騷妻 撞擊感超級好 愛愛啪啪的聲音 可以給舔噴水潮吹 男人愛不釋手的床上服務 #全程無套 可以玩女上位 滿足你身體跟心裡上的放鬆 熱綫⤵️⤵️⤵️⤵️⤵️ 💗Gleezy：jkf0077 💗Line：rely168 💗私密蜜蜜TG：@jkf0077 🍀北部喝茶班表：@jkfa288 🍀中部喝茶班表： @jkfa147 🍀南部喝茶班表： @jkfa269 🍀學生妹18~22歲：@jkf247 🍀熟女人妻大奶區：@jkfa366 🍀特別重口味專區：@jkfq963
Signed 人間小甜甜🇹🇼蜜蜜
35歲波霸美艷人妻 特色奶大 騷 可奶泡 可舔 可後面 可舌吻 艶艶 163cm 55kg F奶 熱綫⤵️⤵️⤵️⤵️⤵️ 💗Gleezy：jkf0077 💗Line：rely168 💗私密蜜蜜TG：@jkf0077 🍀北部喝茶班表：@jkfa288 🍀中部喝茶班表： @jkfa147 🍀南部喝茶班表： @jkfa269 🍀學生妹18~22歲：@jkf247 🍀熟女人妻大奶區：@jkfa366 🍀特別重口味專區：@jkfq963
Signed 人間小甜甜🇹🇼蜜蜜
淑珍 162 / 54 / Dcup/39歲 #愛心義賣志工 成熟的女人就是漂亮 光是一個眼神就夠讓人受不了 懂你的點，也知道怎麼讓你崩潰 熱綫⤵️⤵️⤵️⤵️⤵️ 💗Gleezy：jkf0077 💗Line：rely168 💗私密蜜蜜TG：@jkf0077 🍀北部喝茶班表：@jkfa288 🍀中部喝茶班表： @jkfa147 🍀南部喝茶班表： @jkfa269 🍀學生妹18~22歲：@jkf247 🍀熟女人妻大奶區：@jkfa366 🍀特別重口味專區：@jkfq963
Signed 人間小甜甜🇹🇼蜜蜜
楊慧雯 165 / 52 / Ccup/ 40歲 #房仲業務 纖細美腿誘人 黑絲讓你蠢蠢欲動高潮口技 讓不少哥哥甘拜下風床上功夫 值得新老司機都來體驗看看 絕對讓是榨汁機本機喔 熱綫⤵️⤵️⤵️⤵️⤵️· Telegram蜜蜜賬號：jkf0077 Telegram小甜甜賬號：@book166 🍀北部喝茶班表：@jkfa288 🍀中部喝茶班表： @jkfa147 🍀南部喝茶班表： @jkfa269 🍀學生妹18~22歲：@jkf247 🍀熟女人妻大奶區：@jkfa366 🍀特別重口味專區：@jkfq963
Signed 人間小甜甜🇹🇼蜜蜜
玉珊 161cm / 49kg / D杯 / 41歲 肉感豐潤的白嫩熟女 皮膚滑嫩彈性十足，床上很會叫又主動 特別懂男人敏感點，喜歡激烈體位 騎乘時蜜穴又緊又會夾，爽感超強 熱綫⤵️⤵️⤵️⤵️⤵️ 💗Gleezy：jkf0077 💗Line：rely168 💗私密蜜蜜TG：@jkf0077 🍀北部喝茶班表：@jkfa288 🍀中部喝茶班表： @jkfa147 🍀南部喝茶班表： @jkfa269 🍀學生妹18~22歲：@jkf247 🍀熟女人妻大奶區：@jkfa366 🍀特別重口味專區：@jkfq963
Signed 人間小甜甜🇹🇼蜜蜜
#文靜內向型 書萱 161cm C杯 51kg 35歲 外表文靜少言，床上意外敏感易高潮 專注被引導與緩慢深入，喘息細微又顫抖 熱綫⤵️⤵️⤵️⤵️⤵️ 💗Gleezy：jkf0077 💗Line：rely168 💗私密蜜蜜TG：@jkf0077 🍀北部喝茶班表：@jkfa288 🍀中部喝茶班表： @jkfa147 🍀南部喝茶班表： @jkfa269 🍀學生妹18~22歲：@jkf247 🍀熟女人妻大奶區：@jkfa366 🍀特別重口味專區：@jkfq963
Signed 人間小甜甜🇹🇼蜜蜜
Showing the 9 most recent of 9 posts we hold for @fb9822. 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.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“婧婧🇹🇼全台熟女大奶頻道” (@fb9822), 107 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/fb9822.
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.