Channel
@minta1688
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
120subscribers
-23 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003232493278 |
|---|---|
| Type | Channel |
| Username | @minta1688 |
| Created | Between 1 October 2025 and 31 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 28 August 2026 |
| On Telegram | t.me/minta1688 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 04:17 | 120 | -1 |
| 21 Aug 2026, 13:28 | 121 | -11 |
| 14 Aug 2026, 21:47 | 132 | -11 |
| 8 Aug 2026, 21:46 | 143 | no change |
| 7 Aug 2026, 18:23 | 143 | first reading |
6 posts held, back to 9 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 pageof 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 6 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 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 1 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 1reactions 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 9 July 2026 to 26 July 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.
妹妹資訊 今日的妹妹外型：身材勻稱 皮膚白皙 五官清秀 穿著簡單但很有氣質 整體給人乾淨舒服的感覺 屬於耐看型而非濃妝型 CP值：以目前的行情來說算不錯 價格合理 服務態度也好 年紀：23實際感覺也差不多 不會有太大落差 罩杯：C手感自然有彈性不會過於假 有無抽煙刺青：無抽煙 無刺青 身體很乾淨 服務內容感受：主動度適中 會配合 會回應 過程自然不冷場 技巧不算特別驚艷 但態度誠懇 不會敷衍 整體感受是舒服放鬆的 整體建議／總結：適合想要乾淨 自然 不用太多溝通的客人 如果追求特別激烈或高技巧的服務 可能會覺得普通 但如果喜歡舒服 乾淨 CP值不錯的體驗 這位妹妹值得一試
妹妹資訊 今日の妹妹外型： 清純系小隻馬 皮膚白嫩 臉蛋可愛 身材纖細有料 穿搭簡單卻很有感覺 CP值滿分10分：9.8 年紀：22 罩杯：C杯 有無抽煙刺青：無抽煙 無刺青 服務內容感受：服務態度親切自然 主動但不做作 全程很配合 技巧中上 一邊抽插一隻手柔捏 奶頭很粉嫩 她一直要求要吃吃 後面她自己就開始加速 一波又一波節奏感 很會觀察反應調整節奏 妹妹很會挑逗 健談 配合度很高 整體體驗舒服放鬆 整體建議／總結：很清純 比較主動類型
哥哥～上次約完覺得還沒過癮 剛好今天瑤瑤這邊來了一位新車模 真的超讚 妹妹資訊
哥哥第二次的回約 約的超級開心 妹妹資訊 今日の妹妹外型：年輕可愛 CP值：100 年紀：21 罩杯：大C小D 有無抽煙刺青：有 服務內容感受：很善解人意溫馴的一個妹妹，沒有距離感 整體建議／總結：年輕妹妹的首選
哥哥很信任瑤瑤 每一次都是要我幫她推薦 出來都沒有讓哥哥失望過嗚嗚嗚 這個妹妹也是來瑤瑤這邊 瑤瑤自己面試過的 服務超好 比較推薦喜歡蘿莉的哥哥去試試 💎約約密書瑤 訊息秒回👩🔧 💎飛機預約 @Minta17 💎LINE預約 minta177 💎Gleezy預約 minta17 🦋書瑤全台外約喝茶總班表 t.me/+k0G1lRydhrVkNjY1 🦋 書瑤の私房獨家優質正妹
今日的妹妹外型： 外型非常正點！身高約165cm 比例勻稱 皮膚白皙細嫩 長直髮清純又帶點嫵媚 臉蛋甜美屬於鄰家妹妹型 看了就很舒服 CP值： 超高！以這個外型和服務態度來說，絕對是物超所值 強力推薦 年紀： 看起來24歲左右，保養得很好，皮膚緊實有彈性，完全沒有年齡感。 罩杯： C罩杯偏D 自然挺翹，手感極佳，視覺和觸覺都滿分 有無抽煙刺青： 完全沒有抽煙味，也沒看到刺青，乾淨清爽，很加分。 服務內容感受： 服務非常主動熱情，從一開始的輕鬆聊天破冰，到後面的全身舔吻、口技、69都讓人超享受。特別是她的騎乘位超主動，扭腰擺臀的技巧一流，眼神交流也很到位，整個過程舒服又放鬆。最後還很細心幫忙清理，感覺很貼心。 整體建議／總結： 今天整體體驗非常棒！妹妹外型佳、服務用心、態度親切，完全沒有敷衍的感覺下次在來
❤1
Showing the 6 most recent of 6 posts we hold for @minta1688. 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.
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.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“書瑤客戶實戰客評🇹🇼” (@minta1688), 120 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/minta1688.
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.