Telegram RegisterThe public register of Telegram

Channel

🇹🇼小美|高CP值外約 gleezy:like28

@ss5296

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

1,930subscribers

-6 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001731439752
TypeChannel
Username@ss5296
CreatedBetween 1 January 2022 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/ss5296

Topic

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 67% 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. They sit inside a group of 3 channels that share the same post bodies with each other. 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@uc5689/22726 Aug 2026, 07:09 UTC@ss5296/22907 · this entry6 Aug 2026, 07:15 UTC1.006 minutes
@uc5689/22746 Aug 2026, 07:09 UTC@ss5296/22905 · this entry6 Aug 2026, 07:15 UTC1.006 minutes
@uc5689/22766 Aug 2026, 07:10 UTC@ss5296/22903 · this entry6 Aug 2026, 07:15 UTC1.004 minutes
@uc5689/22786 Aug 2026, 07:11 UTC@ss5296/22901 · this entry6 Aug 2026, 07:15 UTC1.004 minutes
@uc5689/22806 Aug 2026, 07:12 UTC@ss5296/22899 · this entry6 Aug 2026, 07:15 UTC1.003 minutes
@uc5689/22826 Aug 2026, 07:13 UTC@ss5296/22897 · this entry6 Aug 2026, 07:15 UTC1.002 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@uc56897 (7/7 hand-verifiable sample passed)1.004 minutes@uc5689 (70)

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 15 comparable posts for this entry, running 5 August 2026 to 7 August 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 3, the earliest publisher we hold is @xchat87. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, 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.

Growth

1,9301,9361,9337 August 2026 — 1,936 subscribers7 August 2026 — 1,935 subscribers10 August 2026 — 1,930 subscribers7 August 202610 August 2026
3 measurements spanning 4 days, net -6. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,929–1,937 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 14:381,930-5
7 Aug 2026, 12:351,935-1
7 Aug 2026, 01:321,936first reading

Engagement

17 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.963%
avg views ÷ 1,930 subscribers
Avg views / post
18.6
17 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
17
of 17 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held17 (5 August 20267 August 2026)
Views total316
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:13 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.

Recent posts

7 Aug 2026, 07:00 UTC17 viewsread 7 August 2026
Forwarded from @xchat87Photo

欣怡 165-C+-49-24歲 高挑身材 長腿細腰 #氣質模特 皮膚白皙 五官精緻 個性優雅聽話 服務細膩 主動配合 深吻技術很好 ➖➖➖➖➖➖➖➖➖➖ 🤪北部外約 | 中部外約 🤪南部外約 | 熟女外約 🤪新手外約 | 客評專區 🤪學生外約 | 📱Line:tag91 ⭐gleezy私訊 📱TG私訊 ⭐gleezy:tw6699【ID】 🌎營業時間:下午13:00-04:00 #台灣喝茶 #台灣找小姐 #台灣外流 #台灣外約 #全台外約 #正妹優選

7 Aug 2026, 07:00 UTC11 viewsread 7 August 2026
Forwarded from @xchat87Photo

小迪 165cm.Dcup.47kg.26歲 床上是個很熱情淫蕩的妹妹 屬於主動服務型,會主動上搖,艷舞挑逗 浴室就會開始挑逗讓你感覺讓你有舒服 會引領你的雙手和肉棒找尋她的G點 喜歡同時高潮 PS:喜歡喇舌 (加節免費送絲襪) ➖➖➖➖➖➖➖➖➖➖ 🤪北部外約 | 中部外約 🤪南部外約 | 熟女外約 🤪新手外約 | 客評專區 🤪學生外約 | 📱Line:tag91 ⭐gleezy私訊 📱TG私訊 ⭐gleezy:tw6699【ID】 🌎營業時間:下午13:00-04:00 #台灣喝茶 #台灣找小姐 #台灣外流 #台灣外約 #全台外約 #正妹優選

7 Aug 2026, 07:00 UTC12 viewsread 7 August 2026
Forwarded from @xchat87Photo

婉茹167.50.D.23歲 活力辣妹 身材火辣又柔軟 每天練舞維持完美曲線,大奶翹臀超有料 外表陽光開朗、笑容甜美 床上卻超會扭腰、超會用翹臀夾你 運動型女孩的體力與騷度一次滿足! ➖➖➖➖➖➖➖➖➖➖ 🤪北部外約 | 中部外約 🤪南部外約 | 熟女外約 🤪新手外約 | 客評專區 🤪學生外約 | 📱Line:tag91 ⭐gleezy私訊 📱TG私訊 ⭐gleezy:tw6699【ID】 🌎營業時間:下午13:00-04:00 #台灣喝茶 #台灣找小姐 #台灣外流 #台灣外約 #全台外約 #正妹優選

7 Aug 2026, 07:00 UTC12 viewsread 7 August 2026
Forwarded from @xchat87Photo

蘇蘇 162cm・46kg・E奶・30歲 性感熟女姐姐 慾望很大 做愛花樣招式多 殘廢澡 LG 69 ➖➖➖➖➖➖➖➖➖➖ 🤪北部外約 | 中部外約 🤪南部外約 | 熟女外約 🤪新手外約 | 客評專區 🤪學生外約 | 📱Line:tag91 ⭐gleezy私訊 📱TG私訊 ⭐gleezy:tw6699【ID】 🌎營業時間:下午13:00-04:00 #台灣喝茶 #台灣找小姐 #台灣外流 #台灣外約 #全台外約 #正妹優選

7 Aug 2026, 07:00 UTC15 viewsread 7 August 2026
Forwarded from @xchat87Photo

心雅 163 C+ 27歲 曲線自然漂亮 穿搭簡單卻很耐看 個性溫柔穩重 相處起來會慢慢抓住你的心 ➖➖➖➖➖➖➖➖➖➖ 🤪北部外約 | 中部外約 🤪南部外約 | 熟女外約 🤪新手外約 | 客評專區 🤪學生外約 | 📱Line:tag91 ⭐gleezy私訊 📱TG私訊 ⭐gleezy:tw6699【ID】 🌎營業時間:下午13:00-04:00 #台灣喝茶 #台灣找小姐 #台灣外流 #台灣外約 #全台外約 #正妹優選

7 Aug 2026, 07:00 UTC16 viewsread 7 August 2026
Forwarded from @xchat87Photo

語嫻 170 52 D杯 29歲 高挑比例很吸睛 #御姐 曲線自然有女人味 氣質成熟穩重 ➖➖➖➖➖➖➖➖➖➖ 🤪北部外約 | 中部外約 🤪南部外約 | 熟女外約 🤪新手外約 | 客評專區 🤪學生外約 | 📱Line:tag91 ⭐gleezy私訊 📱TG私訊 ⭐gleezy:tw6699【ID】 🌎營業時間:下午13:00-04:00 #台灣喝茶 #台灣找小姐 #台灣外流 #台灣外約 #全台外約 #正妹優選

6 Aug 2026, 09:42 UTC29 viewsread 7 August 2026

有些人 真的無力吐槽 還說自己是專一的男人 真不要臉

6 Aug 2026, 07:15 UTC16 viewsread 7 August 2026
Forwarded from @xchat87Photo

艾蜜 160.45.E+.19歲 美腿纖細. 小蠻腰柔軟 翹臀有肉 後背式撞擊很爽 皮膚白皙,粉嫩小穴超緊實,敏感度極高 摸一摸就會噴水 ➖➖➖➖➖➖➖➖➖➖ 🤪北部外約 | 中部外約 🤪南部外約 | 熟女外約 🤪新手外約 | 客評專區 🤪學生外約 | 📱Line:tag91 ⭐gleezy私訊 📱TG私訊 ⭐gleezy:tw6699【ID】 🌎營業時間:下午13:00-04:00 #台灣喝茶 #台灣找小姐 #台灣外流 #台灣外約 #全台外約 #正妹優選

6 Aug 2026, 07:15 UTC26 viewsread 7 August 2026
Forwarded from @xchat87Photo

悠悠 158cm/Ccup/20歲/45kg 首次兼職學生妹 皮膚滑嫩香氣乾淨 聲音奶奶的 說話輕輕軟軟 ➖➖➖➖➖➖➖➖➖➖ 🤪北部外約 | 中部外約 🤪南部外約 | 熟女外約 🤪新手外約 | 客評專區 🤪學生外約 | 📱Line:tag91 ⭐gleezy私訊 📱TG私訊 ⭐gleezy:tw6699【ID】 🌎營業時間:下午13:00-04:00 #台灣喝茶 #台灣找小姐 #台灣外流 #台灣外約 #全台外約 #正妹優選

6 Aug 2026, 07:15 UTC33 viewsread 7 August 2026
Forwarded from @xchat87Photo

球球:156.43.C.18歲 可愛俏皮 鄰家女孩的感覺 很會聊天 性慾很強 很會配合做愛 身體很敏感 ➖➖➖➖➖➖➖➖➖➖ 🤪北部外約 | 中部外約 🤪南部外約 | 熟女外約 🤪新手外約 | 客評專區 🤪學生外約 | 📱Line:tag91 ⭐gleezy私訊 📱TG私訊 ⭐gleezy:tw6699【ID】 🌎營業時間:下午13:00-04:00 #台灣喝茶 #台灣找小姐 #台灣外流 #台灣外約 #全台外約 #正妹優選

6 Aug 2026, 07:15 UTC13 viewsread 7 August 2026
Forwarded from @xchat87Photo

晴天 156cm 44kg B奶 19歲 小璇 155cm 44kg B奶 19歲 #學生3P 配合度100% 享受尊貴服務 ➖➖➖➖➖➖➖➖➖➖ 🤪北部外約 | 中部外約 🤪南部外約 | 熟女外約 🤪新手外約 | 客評專區 🤪學生外約 | 📱Line:tag91 ⭐gleezy私訊 📱TG私訊 ⭐gleezy:tw6699【ID】 🌎營業時間:下午13:00-04:00 #台灣喝茶 #台灣找小姐 #台灣外流 #台灣外約 #全台外約 #正妹優選

Showing the 12 most recent of 17 posts we hold for @ss5296. 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

Citation-graph rank — 608,047 of 1,151,006entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Cite this entry

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 August 2026 — this entry's latest reading, not the date you are reading this.

“🇹🇼小美|高CP值外約 gleezy:like28” (@ss5296), 1,930 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/ss5296.

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.