Channel
@ting52995
On this record: Topic · Growth · Engagement · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry
58subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003104106155 |
|---|---|
| Type | Channel |
| Username | @ting52995 |
| Created | Between 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/ting52995 |
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 29 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 10 Oct 2026, 01:01 | 58 | +1 |
| 29 Sept 2026, 20:20 | 57 | -1 |
| 15 Sept 2026, 20:56 | 58 | -1 |
| 9 Sept 2026, 00:57 | 59 | +1 |
| 30 Aug 2026, 00:07 | 58 | +1 |
| 10 Aug 2026, 07:01 | 57 | no change |
| 8 Aug 2026, 12:47 | 57 | +1 |
| 7 Aug 2026, 17:48 | 56 | first reading |
13 posts held, back to 22 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 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 13 posts for this entry, the most recent from 27 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 13 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 13 most recent posts we hold, published 22 June 2026 to 27 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.
⚠️ 防詐騙公告 ⚠️ 📢 請各位哥哥務必注意！ 🚫 我們沒有與任何店家 個人 群組或第三方合作！ 最近有客人反映 有人自稱是「合作對象」 「推薦人」 甚至說是我們配合的窗口 但這些人我們完全不認識！ ❌ 請不要相信任何聲稱與我們合作的人 ✅ 為了保障您的權益 ✔️ 所有資訊請以官方聯絡方式為準 ✔️ 若有人主動私訊 介紹 拉群或要求付款 請先向我們確認真偽 ✔️ 有任何疑問 都可以先詢問我們 不要輕易相信陌生人的說法 🔔 再次提醒 我們沒有與任何人 任何店家合作 請提高警覺 避免受騙！ 保護好自己的荷包 也保護自己的個人資訊 🙏
哥哥們～今天是星期六！
The shares total 121%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
這邊跟哥哥提醒一下唷😊 部分地區會需要另外支付妹妹的車馬費 因為我們這邊的妹妹都是自己搭車去旅館的 所以特定區域會依照距離收相對應的車馬費 就像哥哥去定點需要支付房費一樣 至於其他店家是否有收取車馬費 我這邊就不太清楚了 我們這邊的話相對性的地方 會需要支付相對應的車馬費 還請哥哥理解與體諒唷 謝謝💕 📍 可送達地區
❤1
再次提醒一下桃園的哥哥唷 我們桃園的話 只送龜山或者林口呢
📢 哥哥們請注意一下唷🤍 有些旅館我們這邊目前暫時沒有配合送達 主要是因為有些旅館的櫃檯會偷偷的和警察配合 ..... 如果哥哥有指定的旅館 建議可以提前跟婷婷確認 如果不確定要選哪一間 也可以直接跟我說 我們會推薦適合哥哥的旅館給您參考🥰
📢 公告｜預約須知 🔥注意注意！！！ 各位哥哥請注意一下唷 我們這邊的話黑人哥哥是沒有在安排的唷 外籍客人的尺寸和我們這邊的有點差異 我們這邊的話宗旨就是希望每一次安排都能讓雙方自在 舒適 避免因彼此條件或需求不同而影響整體體驗 造成不便敬請見諒 也謝謝哥哥們的理解與配合🥰
📢 注意一下喔哥哥們～ 最近 LINE 有點不穩定 🥹 婷婷的 LINE 帳號目前被限制發訊息了 如果有找不到婷婷 或是訊息一直沒回 不是故意不理哥哥唷 有需要預約 詢問妹妹或優惠活動的哥哥 可以直接用下面方式聯絡婷婷👇或者直接打電話 📱 官方聯絡方式 💚 LINE：@765cguwg 🩵 Gleezy：ting ✈️ TG：@w157d 先加其他聯絡方式 比較不會突然失聯❤️ 婷婷看到訊息都會盡快回覆哥哥 等你來找我聊天唷🥰 👑豐瑞茶莊← 主頻道（最新消息、活動） 👑豐瑞・私生活← 高級私密分享 👑豐瑞・中都會館← 台中地區妹妹 👑豐瑞・南都會館← 台南 高雄地區妹妹 👑豐瑞・北都會館← 台北 新北 新竹地區妹妹 👑豐瑞・金牌特選← 頂級 / 高質感妹妹專區 👑豐瑞・安心預約處← 預約 咨詢 安排 👑豐瑞・深夜福利社← 極致深夜慰藉 👉官方聯絡方式 LINE：@765cguwg Gleezy：ting TG：@w157d
⚔️【傳說玩家集合！】 還在煩惱新造型太貴捨不得買嗎？😆 那就把這次的娛樂一次滿足！ 約妹妹放鬆一下 回家還能直接領《傳說對決》造型 快樂直接加倍🔥 📅 活動期間：7/13～7/19 🎁 消費滿 6,000 元 ✅ 送《勇者造型》任選一款 🎁 消費滿 10,000 元 ✅ 送《史詩造型》任選一款 🎁 消費滿 15,000 元 ✅ 送《傳說造型》任選一款 🎁 消費滿 20,000 元 ✅ 再加送 300 點點券 💜 不管你是單排 雙排還是五排 先把自己放鬆一下 再回去秀造型！ ⏰ 7/13～7/19 限時七天 錯過就要等下次啦！ 快來找婷婷預約 讓你今晚玩得開心 回家登入遊戲還有驚喜等著你！ ✔️ 熱門妹妹可提前預約 ✔️ VIP 會員享優先安排 ✔️ 贈品數量有限 送完為止 這次不只帶你上分 還要讓你的英雄穿新衣！ 👑豐瑞茶莊← 主頻道（最新消息、活動） 👑豐瑞・私生活← 高級私密分享 👑豐瑞・中都會館← 台中…
還有哥哥沒有睡覺的嗎？？？
哥哥們注意～ 我這邊也要特別提醒大家： 我們永遠只見面滿意現金消費 絕對不會要求線上轉帳 付定金或先付款 凡是遇到說要先轉錢 線上交易 給定金的 一律都是詐騙！ 請大家擦亮眼睛 保護好自己 也保護我們彼此的信任❤️ 有任何疑問都可以直接問我 謝謝大家的支持！ #只有這些是我的賬號 其他的一律不是我！！！！ 👑豐瑞茶莊← 主頻道（最新消息、活動） 👑豐瑞・私生活← 高級私密分享 👑豐瑞・中都會館← 台中地區妹妹 👑豐瑞・南都會館← 台南 高雄地區妹妹 👑豐瑞・北都會館← 台北 新北 新竹地區妹妹 👑豐瑞・金牌特選← 頂級 / 高質感妹妹專區 👑豐瑞・安心預約處← 預約 咨詢 安排 👑豐瑞・深夜福利社← 極致深夜慰藉 👉官方聯絡方式 LINE：sy8307 LINE：@765cguwg Gleezy：ting TG：@w157d
晚安小菠蘿蜜 大菠蘿蜜們
原來頻道裏面還可以開直播喔 如果哥哥想要和菠蘿蜜一起聊天嗨皮的可以點這裏進去喔 https://t.me/shanshan567 3點半準備開始喔 有想要參加的哥哥 請準時參加！！！
Showing the 12 most recent of 13 posts we hold for @ting52995. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
哥哥們～今天是星期六！
The shares total 121%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 13 most recent posts we hold, published 22 June 2026 to 27 July 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 5 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.
@ting52995 named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“豐瑞・安心預約處” (@ting52995), 58 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/ting52995.
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.