Channel
@xd1011
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
334subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001708807630 |
|---|---|
| Type | Channel |
| Username | @xd1011 |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/xd1011 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 21:27 | 334 | -1 |
| 8 Aug 2026, 07:05 | 335 | no change |
| 7 Aug 2026, 09:17 | 335 | first reading |
19 posts held, back to 12 November 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 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 19 posts for this entry, the most recent from 25 August 2024. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
15 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 53.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 8 | 53.3% | |
| 👍 | 6 | 40.0% | |
| 👏 | 1 | 6.67% |
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 13 of the 19 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 15reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 12 November 2023 to 25 August 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.
“為什麽要選擇外送茶，有哪些優勢” 1. 便利性和隱私：顧客可以選擇他們想要會面的地點，無論是酒店、住所還是其他私密場所。這爲那些希望避免被他人看到或偏好在熟悉環境中享受服務的顧客提供便利和隱私。 2. 選擇多樣化：外送茶服務通常通過網站或論壇進行安排，顧客可以瀏覽一系列提供服務的女性照片和簡介。這允許顧客根據自己的個人偏好、外貌吸引力、服務類型等選擇最適合自己口味的女性。 3. 定制化體驗：許多外送茶提供者允許顧客定制他們的體驗。顧客可以根據自己的喜好和禁忌，具體說明他們想要的服務類型、持續時間和其他特殊要求。這確保了獨特而令人滿意的體驗。 4. 隱蔽和離散：外送茶服務通常重視隱私和離散性。提供服務的女性通常知道如何謹慎行事，以避免引起不必要的關注。這可能使那些擔心被人發現或尷尬的顧客感到安心。 5. 時間靈活：外送茶服務可能爲那些繁忙的職業人士、有時間限制或偏好靈活安排的人提供便利。顧客可以根據自己的日程安排約會，…
❤1
#吃魚喝茶會不會很髒？感染得病風險？ 如果今天你想要喝茶，這邊珠珠可以跟你保證，珠珠的小姐都是非常乾淨且健康無慮的！ 除了每個月定期做全身健康檢查之外，每接一次客人都洗2次澡！ 且因為喝外送茶的客戶多屬於社會階層高等人士，9成以上的客戶都全程戴保險套！ 珠珠茶莊都會為客戶層層把關把風險降低趨近於0，畢竟每一次的外送茶都是頂著茶莊的招牌。 至於吃魚的部分就不敢說了，也不是說個工比較髒，是因為沒有管理在幫您把關，也不能確定小姐是否有定期做檢查。 如果不幸吃到中獎魚，就只能說你比較倒楣了
#喝茶吃魚的優缺點比較 如果你想要喝茶： 選擇性多，你想要什麼類型的茶妹，無論是大奶、短髮、可愛型、氣質型，基本上提出要求，客服都會盡全力幫你安排！ 如果你預算夠高，甚至想約到JKF雜誌封面美女、車展小模、網紅等等都有！ 因為外送茶比較多妹妹都是兼職下海，因此種類多元、顏質高，漂亮的茶妹比比皆是！ 缺點就是必須自己開房間、因此花費比較高，但有喝過的茶的，我相信絕對是值得花這個錢！ 如果你想要吃魚： 便宜！如果是個工還免房費！大多數的魚更可以接受大尺度的玩法，例如無套、情趣用品、變裝、SM或者肛交！ 但是通常年紀比較大，素質普遍不高，所以收費便宜配合度高，且魚訊不好找，多數為詐騙陷阱
https://t.me/+H_bvlC_OvHllYWZl
原諒我月底的不打擾 密一個人也需要很大的勇氣 接受一次次的拒絶需要更大的勇氣 但是如果你需要 請一定要記得密珠珠 不是因為不缺而不打擾 而是我的勇氣已用盡 你可以主動一次嗎？
❤1👍1
沒有人會一天不看手機 他只是不想回你訊息 太陽不會突然下山 船也不會開進沙漠 這些我都明白 他只是不想理我
➡️❣️ 領取福利專區
訂閱頻道 十點準時發車 https://t.me/+tL-p-nHg6A5mZmFl
#每個人對於好妹的定義都不一樣 也許你是身經百戰的老司機，也許你只是約過幾次有個大概的了解，甚至一次都沒有約過從未涉獵外送茶這個行業 每個人對於【好妹】都有一套屬於自己的標準 【①身材+②外貿+③年齡 】這些都不是判斷好妹的最終標準，很多新手一上來就要找最年輕漂亮的妹妹，都忽略了還有非常重要的【④服務+⑤情商 】 舉個例子： 某些妹妹你開門見她的第一眼，會覺得跟你之前約的其他妹妹身材外貿年紀都是差不多，甚至讓你第一眼覺得普通就還好，但是你還是因為相信珠珠留下她了，整個服務下來，你就懂得了珠珠口中的什麼叫【好妹】。 她沒有比其他妹妹年輕幾歲，也沒有逆天的顏值跟身材，但是相比於同價位的妹妹，在回約率方面可謂是一騎絕塵!!碾壓眾多妹妹，甚至比其他更高價位的妹妹客評還要更好~ 說回原點，不挑客人，對每一位客人都能做到待客如男友的妹妹到底是不是…
👍1
打炮這種東西太極端 要麼一生，要麼陌生 不會的話 讓我家妹妹教你呀
👍1
#吃魚喝茶有什麼要注意的事情 雖然價格越高，體驗失敗的機率就越低，但仍然要小心有些不肖的茶商可能只對一次生意感興趣。在喝茶時，需要特別注意以下三點： ① 確保價格與預期相符，避免出現過高的價格與實際體驗不符合的情況。 ② 注意茶商是否會以各種名目額外收費，要求付款時需仔細查看收費項目，避免意外花費。 ③ 確保使用安全可靠的付款方式，避免使用現金以外的付款方式，以免出現風險。 正規的茶商通常都以誠信經營，重視信譽，如果你點了妹妹後發現她的表現與價格不符，你有權利提出異議。但需要注意的是，如果你從不同的茶商那裡叫來的妹妹都無法滿足你的期望，那可能是因為你的預算太低了
#吃魚喝茶會不會很髒？感染得病風險？ 如果您選擇喝茶，我們珠珠茶莊可以向您保證，我們的小姐都非常注重衛生，健康無慮！除了定期進行全身健康檢查外，每次接待客人後都會進行兩次淋浴，確保身體清潔。此外，由於喝外送茶的客戶多為社會上層人士，我們茶莊有超過九成的客戶都全程使用保險套，從而進一步降低感染風險。我們珠珠茶莊一直以來都為客戶的健康和安全把關，因此您可以放心享受我們的服務，每一次的外送茶都是我們茶莊的招牌 至於吃魚的部分，這就比較棘手了。並不是說個工比較髒，而是因為缺乏管理和監管，無法確保小姐們是否定期進行健康檢查。如果不幸遇到了品質不佳的情況，只能說您遇到了不幸
Showing the 12 most recent of 19 posts we hold for @xd1011. 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.
@xd1011 named 4 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“新手喝茶+珠珠賴atm668” (@xd1011), 334 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/xd1011.
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.