Telegram RegisterThe public register of Telegram
Telegram profile photo for 童心中部/台中/彰化/員林🇹🇼台灣/外送茶 賴y13142

Channel

童心中部/台中/彰化/員林🇹🇼台灣/外送茶 賴y13142

@taiwan00613

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

286subscribers

+49 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002019069561
TypeChannel
Username@taiwan00613
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 November 2026
Measurements held13
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/taiwan00613

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 23 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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 the other topics.

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 in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@taiwan00613/6373 · this entry5 Aug 2026, 09:18 UTC@cc56829/260345 Aug 2026, 09:18 UTC1.00under a minute
@taiwan00613/6376 · this entry5 Aug 2026, 09:18 UTC@cc56829/260375 Aug 2026, 09:18 UTC1.00under a minute
@taiwan00613/6377 · this entry5 Aug 2026, 09:19 UTC@cc56829/260385 Aug 2026, 09:19 UTC1.00under a minute
@taiwan00613/6379 · this entry5 Aug 2026, 09:21 UTC@cc56829/260405 Aug 2026, 09:21 UTC1.00under a minute
@taiwan00613/6381 · this entry6 Aug 2026, 10:52 UTC@cc56829/260556 Aug 2026, 10:52 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@cc568295 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (5–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 28 July 2026 to 6 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).

Of the group of 3 channels, the one whose matching posts we hold earliest is @taiwan00613 — 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 11 November 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.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

237286261.57 August 2026 — 237 subscribers8 August 2026 — 237 subscribers16 August 2026 — 243 subscribers22 August 2026 — 250 subscribers30 August 2026 — 255 subscribers15 September 2026 — 259 subscribers28 September 2026 — 263 subscribers10 October 2026 — 262 subscribers17 October 2026 — 264 subscribers23 October 2026 — 274 subscribers31 October 2026 — 279 subscribers7 November 2026 — 284 subscribers16 November 2026 — 286 subscribers7 August 202616 November 2026
13 measurements spanning 101 days, net +49. 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 230–293 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Nov 2026, 18:20286+2
7 Nov 2026, 17:18284+5
31 Oct 2026, 16:50279+5
23 Oct 2026, 16:36274+10
17 Oct 2026, 07:36264+2
10 Oct 2026, 00:20262-1
28 Sept 2026, 18:41263+4
15 Sept 2026, 10:00259+4
30 Aug 2026, 03:43255+5
22 Aug 2026, 20:34250+7
16 Aug 2026, 04:34243+6
8 Aug 2026, 10:00237no change
7 Aug 2026, 09:33237first reading

Engagement

11 posts held, back to 28 July 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 page of 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 11 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 1 of the 11 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 28 July 2026 to 6 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.

Recent posts

6 Aug 2026, 10:52 UTC14 viewsread 8 August 2026
Photo

沐荷 161cm-47kg-E 奶-27 歲 #台中4000 溫婉幼教 身材熱辣 大E 奶的正妹 細腰 翹臀 賴y13142 皮膚白皙 性格好 超有FU 的 很熱情 講話幽默 不會冷場 還會送你奶炮哦 預約妹妹 密童心❤️ https://t.me/tt06013 童心賴🆔 y13142 妹妹班表 t.me/cc56829 北部 t.me/taiwan0613 中部 t.me/taiwan00613 南部 t.me/taiwan06013 ❤️Line ID : y13142

Signed 我是童心❤️

5 Aug 2026, 09:21 UTC21 viewsread 8 August 2026
Photo

尤珍 161 cm-42kg-B+奶-22歲 #台中 5500 一節 兩節10000 三節14000 骨感賴y13142 可愛類型的女生 很開放 性格很活潑 主動熱情賴y13142 會撒嬌 還會主動上手摸你 有女友fu哦 預約妹妹 密童心❤️ https://t.me/tt06013 童心賴🆔 y13142 妹妹班表 t.me/cc56829 北部 t.me/taiwan0613 中部 t.me/taiwan00613 南部 t.me/taiwan06013 ❤️Line ID : y13142

Signed 我是童心❤️

5 Aug 2026, 09:19 UTC21 viewsread 8 August 2026
Photo

莎穎 164 47 D 23歲 #台中12000 一節 兩節20000 三節27000 女神氣質依然不變 顏值擔當,重外貌身材可預約 超樂觀 熱情 很有女友FU 預約妹妹 密童心❤️ https://t.me/tt06013 童心賴🆔 y13142 妹妹班表 t.me/cc56829 北部 t.me/taiwan0613 中部 t.me/taiwan00613 南部 t.me/taiwan06013 ❤️Line ID : y13142

Signed 我是童心❤️

5 Aug 2026, 09:18 UTC18 viewsread 8 August 2026
Photo

巧音 162.46.B.20歲 台中6000一節 兩節11000 三節16000 一個賴y13142 很可愛俏皮的正妹 聲音很好聽 顏值很正 很有女友FU 慾望很強 很會挑逗 小穴緊緊的像是會呼吸一樣 很會吸 很會夾 預約妹妹 密童心❤️ https://t.me/tt06013 童心賴🆔 y13142 妹妹班表 t.me/cc56829 北部 t.me/taiwan0613 中部 t.me/taiwan00613 南部 t.me/taiwan06013 ❤️Line ID : y13142

Signed 我是童心❤️

5 Aug 2026, 09:18 UTC15 viewsread 8 August 2026
Photo

天天 164 D 47kg 27 歲 #台中 5000 一節 全程無套 嫩妻!人妻y13142 !淫妻!按耐不住寂寞的她,出來兼職滿足性慾!價格不高 超級敢玩!興奮到激凸的奶頭快來咬一口吧! 短期限定 無刺青抽菸 預約妹妹 密童心❤️ https://t.me/tt06013 童心賴🆔 y13142 妹妹班表 t.me/cc56829 北部 t.me/taiwan0613 中部 t.me/taiwan00613 南部 t.me/taiwan06013 ❤️Line ID : y13142

Signed 我是童心❤️

5 Aug 2026, 09:17 UTC13 views1 reactionsread 8 August 2026
Photo

泡泡 160-E奶-24y #台中 5500 一節 兩節10000 三節14000 淫蕩 尤物賴y13142 型辣妹 身材火辣 奶大 床上大方直接 服務大膽不敷衍 做完還會躺在懷裏休息聊天~ 態度、技術、外貌、身材都是五星 預約妹妹 密童心❤️ https://t.me/tt06013 童心賴🆔 y13142 妹妹班表 t.me/cc56829 北部 t.me/taiwan0613 中部 t.me/taiwan00613 南部 t.me/taiwan06013 ❤️Line ID : y13142

❤1

Signed 我是童心❤️

5 Aug 2026, 09:17 UTC14 viewsread 8 August 2026
Photo

嬌嬌 168.E.50 .27歲 笑容甜美賴y13142 的氣質型妹妹,皮膚很好身材也很棒胸型還很美,完美的色情body,為哥哥的「性」福而生的完美肉體,還會主動撅起屁股向哥哥你索求肉棒!! 預約妹妹 密童心❤️ https://t.me/tt06013 童心賴🆔 y13142 妹妹班表 t.me/cc56829 北部 t.me/taiwan0613 中部 t.me/taiwan00613 南部 t.me/taiwan06013 ❤️Line ID : y13142

Signed 我是童心❤️

5 Aug 2026, 09:15 UTC17 viewsread 8 August 2026
Photo

吸吸 158.C.45.25 歲 淫蕩小妖精賴y13142 , 女上超會搖,性格火辣的電臀、無情的電動馬達榨乾著哥哥,想體驗被搖出來的快感嗎那哥哥絕對不能錯過這個床上小旋風呦~ 預約妹妹 密童心❤️ https://t.me/tt06013 童心賴🆔 y13142 妹妹班表 t.me/cc56829 北部 t.me/taiwan0613 中部 t.me/taiwan00613 南部 t.me/taiwan06013 ❤️Line ID : y13142

Signed 我是童心❤️

5 Aug 2026, 09:15 UTC17 viewsread 8 August 2026
Photo

婷子 164.46.D.32歲 #台中3500 一節 兩節6500 三節9500 氣質熟女 賴y13142 人妻 很敢玩 老公常常出差 沒有時間陪伴 很缺少愛的陪伴 性慾很強 預約妹妹 密童心❤️ https://t.me/tt06013 童心賴🆔 y13142 妹妹班表 t.me/cc56829 北部 t.me/taiwan0613 中部 t.me/taiwan00613 南部 t.me/taiwan06013 ❤️Line ID : y13142

Signed 我是童心❤️

28 Jul 2026, 12:17 UTC46 viewsread 8 August 2026
Photo

#童心台中 5000一節 婷萱 身高162cm 50kg D+cup 30 Y 大奶好看 ~服務主動又淫蕩~口爆~顏射 無套bj 氣質+主動+熱情+不會趕時間 預約妹妹 密童心❤️ https://t.me/tt06013 童心賴🆔 y13142 妹妹班表 t.me/cc56829 北部 t.me/taiwan0613 中部 t.me/taiwan00613 南部 t.me/taiwan06013 ❤️Line ID : y13142

Signed 我是童心❤️

28 Jul 2026, 09:45 UTC36 viewsread 8 August 2026
Photo

小喬 160cm 45kg Bcup 20歲 #童心台中 #特價推薦 好看的皮囊有趣的靈魂 互動好口技好 健談不冷場 #小穴敏感易濕 水水的 叫床身好聽不假 配合高 耐操 做起來很有女友FU

Signed 我是童心❤️

Showing the 11 most recent of 11 posts we hold for @taiwan00613. 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.

Mentions

Named by 7 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.

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.

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

“童心中部/台中/彰化/員林🇹🇼台灣/外送茶 賴y13142” (@taiwan00613), 286 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/taiwan00613.

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.