Channel
@zk8567
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
209subscribers
+9 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002315299813 |
|---|---|
| Type | Channel |
| Username | @zk8567 |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/zk8567 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 16:37 | 209 | -3 |
| 22 Aug 2026, 13:14 | 212 | +7 |
| 14 Aug 2026, 03:28 | 205 | +5 |
| 8 Aug 2026, 11:32 | 200 | no change |
| 7 Aug 2026, 16:02 | 200 | first reading |
20 posts held, back to 24 January 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 20 posts for this entry, the most recent from 18 July 2026. An engagement rate over an empty window would be a number about nothing.
5 reactions across 4 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 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 4 of the 20 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 5reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 24 January 2026 to 18 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.
🚨 到現在還是常常聽到客人被騙… 每天都有人私訊跟我分享 原本只是想找人聊聊天 完成一筆交易 結果卻遇到詐騙 辛苦賺來的錢就這樣沒了 最常見的三種詐騙手法就是： ❌ 要求先付款、先匯款、先買點數。 ❌ 一開始談好價格，後面又一直加收各種費用 ❌ 假客服、假網站、假平台，引導你一直轉帳。 💛 小埋提醒大家： 遇到一直催付款 一直加價 或要求到不明網站操作時 一定要提高警覺 多查證 多確認 不要因為一時心急而掉進詐騙陷阱 希望大家都能平平安安 把錢花在值得的地方 而不是落入詐騙集團的口袋 🙏 #防詐騙 #新手必看 #網路交易 #提高警覺 #小埋茶姐 #反詐騙
外送茶不收港幣的喔 只收 #台幣 #人民幣 #美金！！！這三種 其他貨幣一律不收！！！ 只收 #台幣 #人民幣 #美金！！！這三種 其他貨幣一律不收！！！ 只收 #台幣 #人民幣 #美金！！！這三種 其他貨幣一律不收！！！
💎提前預約 VS 臨時預約 差在哪？ 很多哥哥都會問： 「現在可以約嗎？」 「兩個小時後有沒有妹妹？」 其實不是不能安排 而是臨時預約很多時候真的要看運氣 提前預約的好處很簡單： ✅喜歡的類型可以先挑 ✅時間比較好安排 ✅成功率更高 ✅條件好的妹妹比較容易預留 ✅加時、小包夜、大包夜也比較好協調 反過來說 臨時預約常常會遇到： ❌喜歡的妹妹已經被約走 ❌時間剛好排滿 ❌符合預算的選擇變少 ❌熱門時段需要碰運氣 尤其是假日、連假、晚上12點後的熱門時段 越早預約選擇越多 小埋當然也會盡力幫大家安排 但如果想要「穩、爽、選擇多」 提前預約永遠是最好的選擇❤️ 小埋Gleezy：wjk9921
#小埋心裡話
🇹🇼台灣外送茶|小埋新手專區 pinned a photo
#小埋家VIP等級方案 預約找小埋： ➡️Telegram： @wjk9921 ➡️Gleezy： wjk9921 😆茶單頻道 人生何其長 哪能只上一張床🌟
12星座福利優惠開放~ 約妹自動領取 專屬你的星座福利~ @wjk9921
哥哥們可以註冊一下小埋的論壇喲~ 謝謝大家🫶🫶🫶 📱小埋官網： www.twnic4.com
不知道自己喜歡什麼類型的 可以看看哦~
#新手指南👆👆👆 #溫馨提示 ❤️北部外送地區❤️ 北投區 士林區 內湖區 中山區 大同區 松山區 中正區 信義區 南港區 萬華區 大安區 文山區 廬州區 泰山區 三重區 新莊區 板橋區 中和區 永和區 土城區 新店區，汐止區 五股區 （淡水區 林口區 龜山區 八里區）+200車資 ❤️中部外送地區❤️ 東區 西區 北區 南區 中區 北屯區 西屯區 南屯區 大里區 （沙鹿區 豐原區）+200車資 烏日區(限高鐵戀館可送) 大雅鄉（杜拜風情時尚旅館/城市水棧） ❤️高雄外送地區❤️ 小港區 鳳山區+300車資 楠梓區+400車資 (左營區 三民區 前金區 前鎮區 新興區 苓雅區 鼓山區)+200車資 ❤️台南外送地區❤️ （東區 北區 南區 中西區）+200車資 （永康 仁德）+400車資 ❤️新竹外送地區❤️ 新竹市 竹北市 東區 北區 香山區 以上有備註需要車資的地區之外 其他的區域 都是不用給車資的 …
小埋家完整預約流程來啦 沒有約過外約 不明白 不懂的~ 都可以看這裡喲嘻嘻
有送地區可參考 #桃園 #彰化 暫時沒有了哦~
Showing the 12 most recent of 20 posts we hold for @zk8567. 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 — 208,299 of 1,627,445entries 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.
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 3 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.
@zk8567 named 1 handle 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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“🇹🇼台灣外送茶|小埋新手專區” (@zk8567), 209 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/zk8567.
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.