Channel
@ddmnd869
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
23subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001696760905 |
|---|---|
| Type | Channel |
| Username | @ddmnd869 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 5 times, most recently 8 October 2026 |
| On Telegram | t.me/ddmnd869 |
Other / unclassifiable — 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 1 October 2026 and assigned it the closest of 31 fixed categories, at 57% 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 |
|---|---|---|
| 29 Aug 2026, 23:52 | 23 | -1 |
| 11 Aug 2026, 10:31 | 24 | no change |
| 7 Aug 2026, 05:47 | 24 | first reading |
6 posts held, back to 14 June 2023 — 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 6 posts for this entry, the most recent from 20 December 2024. 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 1 reactions 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 14 June 2023 to 20 December 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 10 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
老點妹妹再次下海 第一時間通知到了哥哥 許久沒見 再見感覺依舊 這種感覺是最好的
跟了奶酪整整一年的老客戶了 去年約到艷子 很喜歡 就讓奶酪加入口袋名單 哥哥這次想要回約 所以就又把已經上岸的艷子請回來了 兩個重溫一下 艷子妹妹也還送了原味內褲 一段時間沒見了 聊天聊了蠻久 下個月再回約...
🤯1
謝謝一路來對奶酪🧀的信任和支持
來自 #高雄客評 身高：165 身材：50 罩杯：C 年齡：23 服務：親親 洗澡 按摩 口交 無套吹 69 評分：95分 加入口袋名單 下次回約 謝謝一路來的信任和支持
妹妹：米莉 160/48/E+/26歲 地點：#台南 客評：身高：適中 體重：有點肉肉 罩杯：目測E以上 服務：很健談開朗的妹妹 評分：80分 💫💫恭喜哥哥加入奶酪茶坊的vip 也謝謝信任和支持 給奶酪一次配合的機會 希望以後你在喝茶的路上一直都有奶酪🧀的陪伴
Showing the 6 most recent of 6 posts we hold for @ddmnd869. 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.
Named by 1 registered channel — 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.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“奶酪恩客喝茶售後分享地” (@ddmnd869), 23 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/ddmnd869.
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.