Channel
@fb9679
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,605subscribers
+7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001881528771 |
|---|---|
| Type | Channel |
| Username | @fb9679 |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 19 August 2026 |
| On Telegram | t.me/fb9679 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Aug 2026, 19:51 | 1,605 | +6 |
| 16 Aug 2026, 19:37 | 1,599 | +4 |
| 13 Aug 2026, 14:17 | 1,595 | -2 |
| 7 Aug 2026, 23:25 | 1,597 | -1 |
| 7 Aug 2026, 09:32 | 1,598 | no change |
| 7 Aug 2026, 09:18 | 1,598 | first reading |
4 posts held, back to 29 June 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 2 pagesof Telegram’s post history, 20 posts per page.
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 7 August 2026 |
|---|---|
| Posts held | 4 (29 June 2026 – 7 August 2026) |
| Views total | 18 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 17:58 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.
#台中客評 人生會建議約一次依依 顏值身材 以及服務都會讓你覺得物超所值的女生 超級有女友fu~ 在一起很舒服很有情調 所以優優也都會建議約到這個妹妹至少二節時間比較夠唷 因為跟她在一起真的能感覺到快樂的時光也總是很短暫哦！！ 名字：依依 目測身高：163 目測體重：目測約47 目測胸部：C 目測年齡：約24-26 服務過程：敲門聲響起，打開門看到的是一位身型精緻，留著黑長直髮的妹妹，熱情的牽著你的手走回房內，講話的聲音嗲嗲的但沒有很娃娃音，小聊一下聽著舒服聊起來更舒服，洗完之後妹妹跨坐在身上，雖然是在聊天但有意沒意的碰觸跟好似要直接開戰又突然跑掉的挑逗惹得人心癢癢的，開始服務後從頭到根部的舌尖輕拂，聽我忍耐的呼吸還虧我幹嘛一直嘆氣？跟她說是因為舒服還給你一個心滿意足的微笑後繼續服務，給你滿滿的情緒價值；正戲開始女上、側身、傳教式、用臀橋開始衝刺還問我怎麼不墊枕頭在下面比較不累？最後直接抱著屁股上提緊密而深入的結束；放了…
#台中客評 第一次配合就很阿撒力的哥哥 把自己的需求喜好寫的非常清楚 過程當然非常享受啦~ 目測名字：艾欣 目測身高：165 目測體重：目測約49-50 目測胸部：C 目測年齡：24 服務過程：約了無照推薦的艾欣，雖然沒了照片無謂的期待值，但要說不期待是騙人的；艾欣皮膚很白摸起來也很舒服，先簡單沖洗一下等放浴缸水時聊了一下天簡單認識一下暖個場，然後艾欣用嘴巴幫我暖身後就直接坐上去開始扭動，頻率跟聲音搭配差點沒忍住，趕緊把她請下來躺著我自己控制速度，柔軟度也很好，換了兩三個姿勢都很好配合互動，最後抱著她的雙腿結束，休息了一下再去泡澡，可惜時間到了沒辦法再多互動一下 服務打分：90 顏值打分：90 身材打分：90 咩咩的優點：服務不冷場，好聊天；雙人活動很主動也很好配合 會加入回約嗎：會 對優優的評價：介紹詳細，很熱心；當天會提醒時間跟注意事項，平時沒事不打擾很好 🤩🤩🌟🌟💜💜🌟🌟🤩🤩 …
#台中客評 台中正妹依依 最近有在報班 一直想要回約的哥哥卡緊唷~ 相信優優 包你滿意的~ 讓客人做完直呼戀愛了的妹妹~ 葛格現在已經在計劃下次回約啦~ 客人認證超級色情 超級適合jk制服的好身材 所以準備下次帶制服讓妹妹穿給他看 （想要看妹妹穿情趣制服的哥哥 可以像這位哥哥這樣自備哦 妹妹是可以配合穿的~） 最近優優客評更新比較少 一方面是因為太忙了 來不及更新太多的東西 還有一方面是很多客人不會寫客評 PS：1.不喜歡麻煩懶得寫 2.喜歡的妹妹想要私藏 擔心約的人多了自己再回約就很難約到的 這位哥哥就是擔心回約很難所以拒絕寫客評的xd 所以 優優好不容易要到的客評 且看且珍惜哦~ 依依客評（一） 依依客評（二） 依依客評（三） 🤩🤩🌟🌟💜💜🌟🌟🤩🤩 ⭐優優Gleezy :yy11 📱優優tg :@yn882 …
#台北客評 謝謝最有魅力的男人帥氣救場 妹妹有多好 不用我過多贅述了 享受過 才敢說真話 值得才會強推哦 妹妹最近都在報班 想要嘗試的哥哥趕緊密我 名額不多~ 名字：可比 身高：166 體重：50 胸部：E 年齡：看起來25歲左右 服務過程：第一位遇到比我還享受性愛的妹妹。雖說只是為了救場，但我確實挺好奇茶姐一直在推廣的30k素質到底是什麼樣的程度，所以就直接約了。 妹妹的外表雖然不是模特等級，但確實是那種路上撇了一眼後會忍不住在多看幾眼的那種，皮膚細緻光滑沒有一絲缺陷，身材窈窕沒有一點贅肉，脂肪全都跑到胸部跟臀部，確實是個尤物。 因為我習慣先自行洗澡再迎接妹妹，所以沒有體驗前殘。在床上寒暄了幾句之後，就開始她的服務。她先慢慢舔著我的老二，越舔越過癮，整根直接塞進她的小嘴，並頂到她的喉嚨抽插，吸吮了幾下之後，開始舔了我的蛋蛋，豪邁的邊舔邊吸，並用她的手繼續服侍我的老二。她的手交非常厲害，在我的老二上淋上潤滑液，嘴巴口了幾下之…
Showing the 4 most recent of 4 posts we hold for @fb9679. 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 — 69,380 of 1,583,249entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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 19 August 2026 — this entry's latest reading, not the date you are reading this.
“正妹真實售後 優優賴tg246” (@fb9679), 1,605 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/fb9679.
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.