#南部客評 當你還在質疑月路有沒有學生妹的時候 別人已經在加入回約名單惹~ XD~ 名字:#朝朝 年齡:20 21左右 罩杯:C 體重:46左右 身高:158 對MM整體評分:滿分 服務過程:這次約的妹妹真的很驚喜 外表看起來就是幼齒類型 年輕蘿莉感很明顯 臉蛋很甜美 聲音也很好聽 講話溫柔細膩 相處起來非常有女友fu 不會有那種生硬的距離感 原本以為她就是走可愛路線 結果床上反差超大 該騷的時候完全放得開 主動又投入 而且不會只顧自己 雙方互動很自然 可以感受到兩個人都很享受當下那種節奏 整體來說從外型到互動都很合拍 喜歡年輕系又有女友感的同好真的可以試試 體驗很不錯 是/否回約:有機會回約 有/無刺青:無 對月路的評價:交給月路安排妹妹很可以 好配合 滿意~ 預約點這裡👇 Gleezy搜 🆔tw26y 🆔tw27y(=邀請碼) LINE🆔tw26y 🆔tw28y 月路TG @tw26y @tw27y …

Channel
❶🇹🇼月路家全台好妹喝茶名單Gleezy/賴tw26y
@bqy6332
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
750subscribers
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003793981622 |
|---|---|
| Type | Channel |
| Username | @bqy6332 |
| Description | 密月路TG @tw26y @tw27y 加入Gleezy🆔tw26y 喝茶熱門頻道看這裡 @yl726 |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 October 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 1 |
| On Telegram | t.me/bqy6332 |
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 |
|---|---|---|
| 7 Oct 2026, 14:22 | 750 | first reading |
Engagement
6 posts held, back to 6 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.
- ERR · 30 days
- 15.4%
- avg views ÷ 750 subscribers
- Avg views / post
- 115
- 6 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 6
- of 6 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 7 October 2026 |
|---|---|
| Posts held | 6 (6 October 2026 – 7 October 2026) |
| Views total | 691 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Oct 2026, 14: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
- 747
- Videos
- 2
- Links
- 320
Lifetime counters from Telegram’s own channel header, read 7 October 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.
Recent posts
新報班好妹試車!!! 歡迎來約!!! 預約點這裡👇 Gleezy搜 🆔tw26y 🆔tw27y(=邀請碼) LINE🆔tw26y 🆔tw28y 月路TG @tw26y @tw27y 🇹🇼月路家·妹妹本人照群組 https://c.gleezy.top/tw27y 點擊這裡一鍵加入🌙月路所有頻道
特別推薦 ! 特別推薦 ! 特別推薦 ! 月路今天有一個學生妹 家裡發生了點事急需用錢 短期下海2天 價位可以商議 非常清純漂亮 價位比試車價位還優惠 資料:158.D.20.45kg 私訊月路 @tw26y 或 @tw27y
嗚嗚嗚嗚 還是我寶好😚 澳客請退退退退退退退散😤
#月路北部可約 #台北 #新北 星空 166-25歲-D奶-46kg 嘴上功夫很厲害 粉紅穴穴可品鮑 會主動進攻 喜歡愛愛 最喜歡女上位 體力好 很耐幹喲 預約點這裡👇 Gleezy搜 🆔tw26y 🆔tw27y(=邀請碼) LINE🆔tw26y 🆔tw28y 月路TG @tw26y @tw27y 🇹🇼月路家·妹妹本人照群組 https://c.gleezy.top/tw27y 點擊這裡一鍵加入🌙月路所有頻道
第一次配合不啰嗦 直接給需求預算 交給月路安排 結束感歎!!妹妹很棒👍 人可愛可愛的 這次我也體驗很好 下次約❤️ 名字:可兒 年齡:21 罩杯:C 體重:45kg 身高:162 對MM整體評分:整體蠻不錯 服務過程:妹妹非常健談,從見面開始就自然聊天 完全不會有冷場感覺 相處過程會讓人有種親切感 很像交了一個可愛的小女友 互動過程中她的技術也很棒 很能抓住要點 知道怎麼配合 怎麼回應 整段體驗非常流暢舒服 會讓人不知不覺就放鬆下來享受當下 是/否回約:有機會一定會 有/無刺青:無 對月路的評價:月路安排絕對滿意~ 預約點這裡👇 Gleezy搜 🆔tw26y 🆔tw27y(=邀請碼) LINE🆔tw26y 🆔tw28y 月路TG @tw26y @tw27y 🇹🇼月路家·妹妹本人照群組 https://c.gleezy.top/tw27y 點擊這裡一鍵加入🌙月路所有頻道
Showing the 6 most recent of 6 posts we hold for @bqy6332. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@tw27y9 · 14410 posts🌙月路♥️北部喝茶名單
@tw23y · 1529 posts🌙月路♥️無套內射專區
@tw26y6 · 1569 posts🌙月路♥️平價熟女人妻專區
@tw27y8 · 1448 posts🌙月路家 · 喝茶心得分享
@tw29y · 1487 posts🌙月路♥️南部喝茶名單
@tw28y · 1456 posts🌙月路♥️中部喝茶名單
@tw25y · 1425 posts🌙月路♥️學生妹專區
@tw27y7 · 1455 posts❸🌙月路家全台好妹喝茶名單更新中
@bqy6666 · 7174 posts
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 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.
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.
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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“❶🇹🇼月路家全台好妹喝茶名單Gleezy/賴tw26y” (@bqy6332), 750 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/bqy6332.
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.