Channel
@bd1168
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,917subscribers
+97 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002880955998 |
|---|---|
| Type | Channel |
| Username | @bd1168 |
| Created | Between 1 June 2025 and 31 August 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/bd1168 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 16:46 | 1,917 | +5 |
| 27 Aug 2026, 06:44 | 1,912 | +16 |
| 24 Aug 2026, 16:25 | 1,896 | +8 |
| 21 Aug 2026, 02:37 | 1,888 | +22 |
| 17 Aug 2026, 23:32 | 1,866 | +7 |
| 15 Aug 2026, 00:17 | 1,859 | +8 |
| 11 Aug 2026, 14:31 | 1,851 | +27 |
| 8 Aug 2026, 13:38 | 1,824 | +4 |
| 7 Aug 2026, 17:33 | 1,820 | first reading |
9 posts held, back to 7 August 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.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 2 of 9 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 9 (7 August 2026 – 7 August 2026) |
| Views total | 468 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 17:33 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 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 2 of the 9 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 7 August 2026 to 7 August 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.
哈寶 162cm 47kg D奶 26歲 #標準S型身材讓你垂涎欲滴 喜歡刺激和花樣玩法 一道乳溝讓你充滿無限的想象 小穴超級水嫩 超級緊實 一不小心容易榨乾喔 ➖➖➖➖➖➖➖➖➖➖ 北部專區 中部專區 南部專區 學生專區 簽到群組 熟女專區 高檔尤物區 客評專區 新手專區 素人外流 旅館推薦 🌟Gleezy總茶單 🚨一鍵加入小埋所有頻道 📱line：twnic4 ⭐Gleezy私訊 🌐TG私訊 ⭐Gleezy：wjk9921【ID】 🌎營業時間：下午13：00-04：00 #台灣喝茶 #台灣找小姐 #台北外送茶 #台灣外約 #全台外約 #正妹優選
念謠 165cm 47kg C+奶 27歲 #風騷淫蕩的櫃姐 、配合度極高、胸部柔軟又堅挺、可全程無套、 上搖持久高達30分鐘、這個姐姐誰約到誰倒霉、一節就給你射兩次 ➖➖➖➖➖➖➖➖➖➖ 北部專區 中部專區 南部專區 學生專區 簽到群組 熟女專區 高檔尤物區 客評專區 新手專區 素人外流 旅館推薦 🌟Gleezy總茶單 🚨一鍵加入小埋所有頻道 📱line：twnic4 ⭐Gleezy私訊 🌐TG私訊 ⭐Gleezy：wjk9921【ID】 🌎營業時間：下午13：00-04：00 #台灣喝茶 #台灣找小姐 #台北外送茶 #台灣外約 #全台外約 #正妹優選
馨兒 158cm 45kg C奶 19歲 外表甜美笑容迷人 最近想體驗更多的性愛樂趣、服務細緻溫柔體貼，擅長輕柔親吻和溫暖的撫摸 她的甜美聲音和柔軟的小手讓人心動不已！！ ➖➖➖➖➖➖➖➖➖➖ 北部專區 中部專區 南部專區 學生專區 簽到群組 熟女專區 高檔尤物區 客評專區 新手專區 素人外流 旅館推薦 🌟Gleezy總茶單 🚨一鍵加入小埋所有頻道 📱line：twnic4 ⭐Gleezy私訊 🌐TG私訊 ⭐Gleezy：wjk9921【ID】 🌎營業時間：下午13：00-04：00 #台灣喝茶 #台灣找小姐 #台北外送茶 #台灣外約 #全台外約 #正妹優選
姿琪 168cm 51kg E奶 27歲 膚白大奶 服務熱情主動敢玩 #特價6000雙北 ➖➖➖➖➖➖➖➖➖➖ 北部專區 中部專區 南部專區 學生專區 簽到群組 熟女專區 高檔尤物區 客評專區 新手專區 素人外流 旅館推薦 🌟Gleezy總茶單 🚨一鍵加入小埋所有頻道 📱line：twnic4 ⭐Gleezy私訊 🌐TG私訊 ⭐Gleezy：wjk9921【ID】 🌎營業時間：下午13：00-04：00 #台灣喝茶 #台灣找小姐 #台北外送茶 #台灣外約 #全台外約 #正妹優選
▂▄▄▓▄▄▂ ◢◤ █▀▀████▄▄▄▄◢◤ █ 直升機即將降落 █▀▀▀▀╬ ◥███████◤ ══╩══╩══ 快來坐小埋為你提供的私人飛機~~ @wjk9921
沫沫162cm 46kg B+奶 22歲 舞蹈班學生妹私下偷偷兼職 尋求跟大屌玩刺激 給你想不到的玩法 聽她淫叫 喜歡在沙發 陽台 泳池愛愛 無毛乾淨 配合玩自慰棒 跳蛋 #水手服 #可自帶 ➖➖➖➖➖➖➖➖➖➖ 北部專區 中部專區 南部專區 學生專區 簽到群組 熟女專區 高檔尤物區 客評專區 新手專區 素人外流 旅館推薦 🌟Gleezy總茶單 🚨一鍵加入小埋所有頻道 📱line：twnic4 ⭐Gleezy私訊 🌐TG私訊 ⭐Gleezy：wjk9921【ID】 🌎營業時間：下午13：00-04：00 #台灣喝茶 #台灣找小姐 #台北外送茶 #台灣外約 #全台外約 #正妹優選
滿滿 163cm 46kg D奶 22歲 人見人愛花見花開の小浪女 外貌清秀氣質 到了床上哩丟災 床上是個不折不扣的小惡魔 胃口頗大完全是情色女優等級 易濕體質興奮時的模樣好誘人喔 哥哥一定要來約約看 #全程無套 ➖➖➖➖➖➖➖➖➖➖ 北部專區 中部專區 南部專區 學生專區 簽到群組 熟女專區 高檔尤物區 客評專區 新手專區 素人外流 旅館推薦 🌟Gleezy總茶單 🚨一鍵加入小埋所有頻道 📱line：twnic4 ⭐Gleezy私訊 🌐TG私訊 ⭐Gleezy：wjk9921【ID】 🌎營業時間：下午13：00-04：00 #台灣喝茶 #台灣找小姐 #台北外送茶 #台灣外約 #全台外約 #正妹優選
❤1
點心155cm 43kg B奶 18歲 甜甜的奶音欲拒還羞的樣子 超動人愛愛時可輕鬆抱起玩耍各種體位 隨意爽讓點心蹲桌上後背抱著超好玩的 ➖➖➖➖➖➖➖➖➖➖ 北部專區 中部專區 南部專區 學生專區 簽到群組 熟女專區 高檔尤物區 客評專區 新手專區 素人外流 旅館推薦 🌟Gleezy總茶單 🚨一鍵加入小埋所有頻道 📱line：twnic4 ⭐Gleezy私訊 🌐TG私訊 ⭐Gleezy：wjk9921【ID】 🌎營業時間：下午13：00-04：00 #台灣喝茶 #台灣找小姐 #台北外送茶 #台灣外約 #全台外約 #正妹優選
奈奈 163cm 47kg D奶 24歲 可愛 很溫柔 小小的一隻喔 各種服務都很配合 ➖➖➖➖➖➖➖➖➖➖ 北部專區 中部專區 南部專區 學生專區 簽到群組 熟女專區 高檔尤物區 客評專區 新手專區 素人外流 旅館推薦 🌟Gleezy總茶單 🚨一鍵加入小埋所有頻道 📱line：twnic4 ⭐Gleezy私訊 🌐TG私訊 ⭐Gleezy：wjk9921【ID】 🌎營業時間：下午13：00-04：00 #台灣喝茶 #台灣找小姐 #台北外送茶 #台灣外約 #全台外約 #正妹優選
❤1
Showing the 9 most recent of 9 posts we hold for @bd1168. 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 — 32,276 of 1,627,068entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 2 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.
@bd1168 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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“🇹🇼台灣外送茶|小埋全台選妹班表🔞” (@bd1168), 1,917 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/bd1168.
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.