Channel
@tg869t
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
680subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001194232729 |
|---|---|
| Type | Channel |
| Username | @tg869t |
| Description | 一鍵加入小嵐頻道：https://t.me/addlist/1nssbhSJNcI4ZThl 🔥論壇：www.tg869.com |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/tg869t |
Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 91% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @yjinx15/32227 Jan 2026, 09:16 UTC | @tg869t/4523 · this entry27 Jan 2026, 09:16 UTC | 1.00 | under a minute |
| @yjinx15/32328 Jan 2026, 05:46 UTC | @tg869t/4524 · this entry28 Jan 2026, 05:46 UTC | 1.00 | under a minute |
| @yjinx15/32428 Jan 2026, 07:11 UTC | @tg869t/4525 · this entry28 Jan 2026, 07:11 UTC | 1.00 | under a minute |
| @yjinx15/32629 Jan 2026, 05:14 UTC | @tg869t/4527 · this entry29 Jan 2026, 05:14 UTC | 1.00 | under a minute |
| @yjinx15/32830 Jan 2026, 13:25 UTC | @tg869t/4528 · this entry30 Jan 2026, 13:25 UTC | 1.00 | under a minute |
| @yjinx15/32931 Jan 2026, 06:49 UTC | @tg869t/4529 · this entry31 Jan 2026, 06:49 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @yjinx15 | 8 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (8–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 10 comparable posts for this entry, running 25 January 2026 to 13 July 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @tg869t — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 00:47 | 680 | no change |
| 7 Aug 2026, 00:36 | 680 | first reading |
18 posts held, back to 25 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 18 posts for this entry, the most recent from 13 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 7 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
#台中推薦 星辰 155/45/D/22 整體感想以及過程：進門後 按照慣例先繳費 這點很重要 必須尊重人家的職業精神 妹妹穿著一件超短裙 坐下後意外發現她穿著可愛的小褲褲 長腿又直又細 讓人眼前一亮 當她開始脫衣服時 我瞬間被她的身材所震撼——超大的巨乳 加上完美的除毛 整個畫面直接打中我的心 快速沖完澡後 我們躺到床上進入正題 妹妹的嘴技讓我大開眼界 她熟練地用舌頭探索 讓我瞬間回憶起被口的快感 久違的體驗讓我沉浸其中 接著 妹妹主動坐上來 她的巨乳帶來了視覺和觸覺的双重享受 讓我欲罢不能 妹妹累了之後 換我進攻 一陣激烈的抽插後 我把所有的精力都留在了她體內 第一輪結束後 我們泡了個澡，然後進入第二輪 果然 一分錢一分貨 妹妹迅速恢復體力 我們像猴子一樣瘋狂地繼續 嘗試了各種姿勢和體位 享受著雞雞與小穴的完美結合 我特別推薦後背式 緊致的感覺讓整個床都在搖晃 手也不安分地攻撃她的巨乳 最後 我們換回正常體位 再次…
點擊以下加入大G版喝茶頻道（目前最穩定的APP）
🌐line：36jkf 加瀨加瀨加瀨加瀨加瀨加瀨加瀨
拉拉隊報班 有人有興趣嗎 @LZY52
https://t.me/+8ehsk_APwl00Mzk1
歡迎騷擾我
學生妹妹 孕婦 奶水媽媽 特殊行業的都有哦~~~
全部秒殺價5000-15000 📌 #台北 喵喵：160.D.46.22歲 #台大學生妹 小妍：165.D.48.24歲 #展場Showgirl 柔柔：168.E.49.25歲 #華航美女空姐 📌 #台中 小雨：160.C.45.20歲 #逢甲學生妹 小比：169.E.49.24歲 #夜店辣妹 姬姬：163.D.48.24歲 #撞球場美女 📌 #高雄 小希：163.D.47.24歲 #萌系護士 貝貝：161.E.45.22歲 #波霸學生妹 莎莎：165.D.46.20歲 #甜美舞蹈妹 📌 #新竹 喬伊：160.D.48.24歲 #甜美小秘書 果果：163.C.47.23歲 #鄰家小妹 海盜：165.E.48.25歲 #巨乳模特兒 倩倩：165.D.48.24歲 #性感學生妹 夏夏：163.C.46.22歲 #Showgirl 沐沐：160.E.46.25歲 #巨乳甜妹 📌 #台南 小雅：160.C.46.24歲 #…
#今日學生妹試車 #台北推薦 試車價：8000 小雅 162cm F罩杯 46kg 20歲 甜美純情，身材火辣，初戀般的體驗 #台中推薦 試車價：9000 語涵 165cm E罩杯 48kg 21歲 高挑纖細，清純溫柔，貼心服務 #高雄推薦 試車價：7000 芷晴 160cm D罩杯 45kg 19歲 青春活力，初戀悸動，很有女友fu #新竹推薦 試車價：7000 依依 158cm C罩杯 43kg 22歲 小隻馬，溫柔甜美，戀愛感滿滿 #台南推薦 試車價：6000 妍希 163cm D罩杯 47kg 20歲 氣質甜美，大眼正妹，服務溫柔體貼 #台北推薦 試車價：10000 清雅 164cm E罩杯 49kg 20歲 高挑性感，學院派女神，互動自然 #台中推薦 試車價：8000 安妮 159cm C罩杯 44kg 21歲 清純可人，小家碧玉，性格溫柔 #高雄推薦 試車價：7000 玥玥 161cm F罩杯 48k…
粉色奶韻 超讚的 可愛妹子 20歲 魯魯 160cm 45kg D杯 20歲 小女生 慾望膨脹 希望被調教 性愛方面知識 很充足喔 今天很阿沙力的哥哥幫我捧場 約的是私藏的紅牌妹妹 臉蛋超級好看 身材高挑瘦 皮膚白皙 只是在學校有做兼職模特 氣質很讚 #娜娜 162 45 22歲 D+奶 水超多 互動好 主動熱情大方 可愛清純學生妹 喜歡學生妹的 即可預約 #萌萌 164 47kg C杯 21歲 喜歡有FU 的大哥哥 大叔叔 溫柔的愛 性愛經驗不多 但是會配合對方喔 小可 162cm Ccup 20歲 46kg #台中 吃起來酥酥脆脆 很有女友FU 纖細好操控 喜歡頂到最深處嗨到最高點 皮膚白皙服務好 BJ.殘廢澡 看互動可LG 重點是不趕時間配合度高 MM剛兼職不久鮑魚還是嫩嫩粉紅色的 緊緊鮑魚 兼職地區：雙北 ??敢玩敢拍大學生直播主 林雪琪/158/B+/43kg/21y 她真的很優秀 對…
沒業績不敢大聲說話 沒業績不敢遲到請假 沒業績不敢抬頭講話 沒業績都感覺自卑了 誰能給我一個抬頭講話的機會？ 價位不限 低消也是愛 如果你今晚還在猶豫去哪 請給我捧場一下 優惠都給你 敲我TG：@LZY52 Gleezy賬號：LZ1124 Gleezy私密入口：https://gleezy.net/xt52dv 一個男生很喜歡的頻道 https://t.me/+cTD08L70ODxhNWM1 加入送特殊影片 論壇： www.tg869.com
嗚嗚嗚 謝謝哥 業績爛到連親媽都不認識了 嗚嗚嗚 有哥哥加持的6000 還差很多 還有沒有哥哥幫我加持的啊 嗚嗚嗚 今天算上最後3天 不算最後2天 還有沒有哥來幫我捧場啊 求求你了 小女子不才 只能以身相許了 嗚嗚嗚 有沒有哥 可以幫幫我啊 嗚嗚嗚 大姐說 我在沒有業績就送我去柬埔寨了 嗚嗚嗚 有沒有好心的哥 哪些 下次哥 等等哥 消失哥 你們在哪裡啊 哪些畫餅哥 可以兌現誠諾了嗎 嗚嗚嗚 😭😭😭😭 敲我TG：@LZY52 Gleezy賬號：LZ1124 Gleezy私密入口：https://gleezy.net/xt52dv 一個男生很喜歡的頻道 https://t.me/+cTD08L70ODxhNWM1 加入送特殊影片 論壇： www.tg869.com
Showing the 12 most recent of 18 posts we hold for @tg869t. 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 — 1,047,684 of 1,183,361entries 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 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.
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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“小嵐家正妹客評🔥🔥🔥” (@tg869t), 680 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/tg869t.
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.