Channel
@mc869
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
781subscribers
-5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001968663541 |
|---|---|
| Type | Channel |
| Username | @mc869 |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/mc869 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 10:22 | 781 | -4 |
| 16 Aug 2026, 16:48 | 785 | -1 |
| 8 Aug 2026, 05:23 | 786 | no change |
| 7 Aug 2026, 10:18 | 786 | first reading |
6 posts held, back to 26 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 1 pageof 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 5 August 2026 |
|---|---|
| Posts held | 6 (26 June 2026 – 5 August 2026) |
| Views total | 29 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 10:18 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.
3 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 2 of the 6 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 3reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 26 June 2026 to 5 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
➡️小晴老司機客評 #姓名：禾羽 #年齡：19 #身高：大概165 #體重：49 #胸部：C+ #服務過程： 開門看到一張很美的混血美女臉，聊起天來卻是直爽的個性，很好聊，也非常享受性愛。 身材非常的好，修長白皙的美腿，腳趾很美，足底嫩滑。 滑嫩緊實的皮膚，充滿彈性的翹臀，胸前的激凸嫣紅非常迷人， 身體非常敏感也很色，喜歡被溫柔又持久的對待。 迷醉顫抖的樣子看起來非常享受，配合度非常高，很愉快的約會體驗。 #對小晴的評價：介紹的妹子都很出色，而且來的都很快，不會浪費很多時間等待，這點非常棒。 _____💯喝小晴外送茶❤️_____ 📱小晴のTG： @zq968 🌐小晴のline：99zqm ⭐小晴のGleezy：zq9688 📢 小晴正妹班表 📱 一鍵加入小晴所有頻道 ➡️分類班表更方便： 北部 中部 南部 🤓🤓🤓🤓🤓🤓🤓🤓🤓
❤1
有需要想約約馬上想起小晴 直接寫出想要的需求預算 相信交給小晴安排 直接四節❤️ 荳米 164-22歲-C奶-43kg #外貌：可愛型帶點小豔麗，眼睛很漂亮，是路上回頭率高的妹妹😍😍 #年紀：22 #身材：164/42 C #態度：非常好，非常健談，聊開很容易聊過頭😂 #服務： 開門瞬間看到妹妹時，直接被她的眼睛勾走我的靈魂，妹妹很健談讓我覺得非常放鬆～洗澡後辦起正事也是不馬虎，叫聲非常好聽，基本上只要溫柔對待她都願意配合，尤其妹妹喜歡被舔，淡淡清香配上酥麻叫聲真的很讓人上火🔥🔥邊做還會邊用撫媚的眼神及櫻桃小嘴吸手指，完全A片情節啊啊啊～第一發就這樣被妹妹榨乾了😍😍 休息過後抱著開起聊天模式～真的天南地北聊，很有小女友的感覺，第二次運動妹妹放福利讓我可以無套進入，真的被小驚艷到❤️❤️幾乎什麼姿勢都玩了一輪，最後用背後式一路衝撞屁股，那視覺真的是無與倫比的美麗，只能說無套真的很有感，會回不去啦啦啦～ #整體給幾分：給妹…
#北部心得 #私房菜系列 名字：不知道 身高/體重：162 45 年紀/罩杯：20歲目測有 D+ #本日爽翻紀錄：開門見著妹妹，夭壽可愛啦主動問候，氣氛滿分！完全不尷尬，聊一聊，就去洗澡，洗澡時，一直就開始親來親去，真是甜死人了！後來進入主題，先是繼續喇，然後她翹屁股直接戴上雨衣開始後入，69，小穴很美，一直舔，她就一直發出可愛的聲音，越聽越上癮，開始了激情的對決，妹妹配合度百分百，玩了很多姿勢，一直抖個不停，累癱才停下來休息，休息時也繼續喇，第二輪，讓妹妹坐上來，不得了，搖得快飛起來！好幾次都頂到最深處，她還能自己搖到高潮，真是厲害！看她這樣子，是要壓著猛衝呀，直到她受不了，才停下來喝口水，喘口氣，沒想到，她又來口技攻擊，實在是太厲害了，忍不住就噴了，結束今天的約會 妹妹真的超級有女友fu #對小晴的評價：配合了兩次，小晴還是一樣不簡單，本想簡單放鬆，沒想到介紹高手，直接榨乾我的子彈，在線佩服，不愧是專業人士。
#北部好評+1 #希希真實反饋+1 被老朋友嫌棄安排的太好，說口味會被養刁的一天 #感謝老朋友的捧場跟支持 名字：希希 身高/體重：161 46 年紀/罩杯：E 23歲 #本日爽翻紀錄：一碰面我內心就os：哇塞！這是我可以享受的嗎？妹妹的身材是真的很讚（尤其是奶子，不是特別控奶的我都覺得愛不釋手）。妹妹本身就很好聊。，也很熱情，聊聊之後就是標準的洗澡環節，妹妹的手法比較青澀一點，但教一下一點就通，非常有成就感，接著開始辦正事，正常位，女上，後背，不論哪種，妹妹的奶子都非常的加分，特別是淫叫聲真的很好聽 還會說騷騷的話 特別要講正常位，做到一半妹妹雙腳突然纏上來，當下讓我非常興奮，一陣性福感滿滿的活塞運動後交槍，總體下來非常滿足 #對小晴的評價：這次全全交給小晴安排 照片都是不用看 都是安排的那麼好 私房菜真的很香 以後多多幫我推薦私房菜
昨天剛面試的騷妹妹客評來了 試車價位好康 妹妹素質又很讚 真的是撿到了便宜了 心得：姓名：素錦 身高：164左右 胸部：F 體重：47幾吧 年紀：25 過程： 一進門妹妹就先熱情地打招呼，妹妹屬於清純漂亮類型，互相認識一下後，就繳錢開始服務，妹妹的身材真的很好，胸型非常漂亮，雖是大奶但完全不垂，甚至有點挺，全身都白白嫩嫩的，摸起來非常舒服，他的奶真的好好摸，欲罷不能的那種，我玩奶玩到妹妹問我說是有這麼好玩嗎?回答當然就是"沒錯"!就是這麼好玩。 我們先洗第一次澡後，就先一起去泡澡聊天，泡完擦乾身體後，我們就到床上互相探索對方的身體，第一次就在我們探索的差不多，直接用傳教士結束第一回合，簡單整理後，我們便回到床上聊天，妹妹口條很好，也很健談，天南地北都能聊，完全沒有第一次見面的尷尬，反而很像朋友一般的聊天。 恢復的差不多後，我就請妹妹開始幫我全身摸來摸去，然後幫我口交根用手套弄，就在妹妹努力不屑的持續進攻10幾分鐘後，第二回合就…
❤2
不管什麼時候約亦菲都是好評滿滿 永不變の態度服務互動都是一流的 這次一樣聽小晴建議約亦菲 直接四節走起 射好射滿 💖 客評： #外貌： 水汪汪眼睛, 鵝蛋臉龐, 漂漂亮亮想捧著認真的親 #年紀： 24左右囉 #身材： 怎麼可以裝備這麼驚人的胸器呢,一定要享受乳悶, 乳晃, 沈甸甸又跟棉花糖一起軟綿綿, 兩顆女乃豆頁小小的, 皮膚滑不溜丟的, 吹彈可破似的, 妹妹的妹妹小小又粉嫩粉嫩, 棒棒der #態度： 眼睛都在笑, 非常棒的服務, 把你當男朋友來呵護 #服務： 門關上後, 就先來個大大的擁抱, 開啟夜晚的激情, 然後幫忙你慢慢的脫衣, 在牽著你一起去沐浴洗漱一番, 然後再對你的分身、全身泡泡沐浴, 回到床上後, 熱情的看著你親吻喇舌, 在用小手潤滑撫摸分身, 摸著摸著後就口著口著並伴隨著吸允的聲音, 舒服的感受, 誘人的聲音, 請妹妹來一下69互口後, 戴上雨衣, 第一次就在妹妹的身體裡完成第一發； 休息時, 妹子…
Showing the 6 most recent of 6 posts we hold for @mc869. 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 — 807,056 of 1,627,068entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 2 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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“小晴客評轉區” (@mc869), 781 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/mc869.
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.