Telegram RegisterThe public register of Telegram
Telegram profile photo for 杭州肯德基工兵

Channel

杭州肯德基工兵

@kdjyrny

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry

20,851subscribers

+8,988 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003795230788
TypeChannel
Username@kdjyrny
Description【聊天主群】 @kdjqjt 【榜单频道】 @hzkdjcd
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live15 November 2026
Measurements held62
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/kdjyrny

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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 forms a group of 2 channels linked by matching posts. 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 (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@hzkdjcd/112919 Aug 2026, 17:46 UTC@kdjyrny/1125 · this entry19 Aug 2026, 17:46 UTC1.00under a minute
@hzkdjcd/140328 Aug 2026, 15:24 UTC@kdjyrny/1390 · this entry28 Aug 2026, 15:24 UTC1.00under a minute
@kdjyrny/4534 · this entry5 Nov 2026, 07:27 UTC@hzkdjcd/35445 Nov 2026, 14:51 UTC1.007.4 hours
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
@hzkdjcd40 (8/8 hand-verifiable sample passed)1.00under a minute@hzkdjcd (34–6)

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. 17 of the 17 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 175 comparable posts for this entry, running 10 August 2026 to 14 November 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 2 channels, the one whose matching posts we hold earliest is @hzkdjcd. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 15 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 2 registered channels linked by matching posts. 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

10,03420,85115,442.510 August 202615 November 2026
62 measurements spanning 97 days, net +8,988. 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 8,411–22,474 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)SubscribersChange
15 Nov 2026, 13:1020,851+615
12 Nov 2026, 08:1520,236-27
10 Nov 2026, 07:4820,263+509
8 Nov 2026, 19:2019,754-4
7 Nov 2026, 13:2119,758-31
6 Nov 2026, 13:1619,789+111
5 Nov 2026, 13:5819,678+293
4 Nov 2026, 12:0619,385+272
3 Nov 2026, 08:2919,113+188
2 Nov 2026, 04:5118,925+264
1 Nov 2026, 02:3818,661+244
30 Oct 2026, 23:3118,417+192
29 Oct 2026, 20:1918,225+166
28 Oct 2026, 23:3118,059+466
27 Oct 2026, 23:2617,593+91
26 Oct 2026, 20:1017,502+158
25 Oct 2026, 17:1117,344+258
24 Oct 2026, 19:2517,086-122
23 Oct 2026, 18:3717,208+85
22 Oct 2026, 17:0117,123first reading

Engagement

219 posts held, back to 10 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 56 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.37%
avg views ÷ 20,851 subscribers
Avg views / post
494
107 posts measured
Reaction rate
0.156%
reactions ÷ views · ER floor
Posts in window
107
of 219 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. It is computed over the 46 of 107 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 November 2026
Posts held219 (10 August 2026 – 15 November 2026)
Views total52,831
Reactions total38
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 04:57 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.

What this channel posts

Photos
≈1,690
Videos
≈628
Links
≈626

Lifetime counters from Telegram’s own channel header, read 16 November 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.

Video runtime
19m 12s
Average length
7s

Measured directly from 159 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

65 reactions across 50 posts, in 2 distinct kinds. The most used accounts for 96.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6396.9%
👍23.08%

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 75 of the 219 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 65 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 219 most recent posts we hold, published 10 August 2026 to 15 November 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

Telegram’s own ‘edited’ marker: 2 of 107 posts held from the last 30 days (1.87%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

15 Nov 2026, 10:51 UTC690 views1 reactionsread 16 November 2026
Photo

【花名】#玥玥 【联系】@yueyuepa 【位置】#上城 【价格】#800p 【罩杯】#B 【标签】#御姐 #舌吻 #69互舔 #水中萧 #毒龙 【报告】 🍗服务系御姐 工兵优惠6折工兵2名 500p/900pp 剩余0 返回工兵链接 ❶群内发送兑换获取工兵名额 ❷提示兑换成功后把截图以及工兵报名表发送机器人 @qjttgbbot ❸工兵时效48小时,到期未出击或未提交报告取消工兵资格并拉黑 群内发送“报告”获取模板,报告提交 @qjttgbbot 📌工兵频道 📌报告频道 📌投诉售后 📌认证商家 🍗肯德基精选优质频道推荐 🏙肯德基最美好声音集合🗣

❤1

15 Nov 2026, 08:08 UTC389 views0 reactionsread 16 November 2026
Forwarded from @hzkdjcdPhoto

【花名】#遥遥 【联系】@yaonn88 【位置】#拱墅 【价格】#1000p 【罩杯】#C 【标签】#嫩妹 #舌吻 #69互舔 【报告】报告1 报告2 🍗刚破处嫩妹,主动降价200 📌工兵频道 📌报告频道 📌投诉售后 📌认证商家 🍗肯德基精选优质频道推荐 🏙肯德基最美好声音集合🗣

15 Nov 2026, 08:00 UTC446 viewsread 16 November 2026
Forwarded from @hzkdjcdPhoto

【花名】#刘念 【联系】@xyz123aa 【位置】#上城 【价格】#1200p 【罩杯】#C 【标签】#御姐 #69互舔 #kiss 【报告】 🍗好看的皮囊千篇一律,合格的秘书百里挑一 📌工兵频道 📌报告频道 📌投诉售后 📌认证商家 🍗肯德基精选优质频道推荐 🏙肯德基最美好声音集合🗣

15 Nov 2026, 07:30 UTC737 viewsread 16 November 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_1519069196

15 Nov 2026, 07:30 UTC598 views0 reactionsread 16 November 2026
Photo

【花名】#婉婉 【联系】@wanwan988877 【位置】#拱墅 【价格】#800p 【罩杯】#B 【标签】#嫩妹 #舌吻 #69互舔 #水中萧 【报告】 🍗女友感很强 工兵优惠6折工兵2名 500p/900pp 剩余1 返回工兵链接 ❶群内发送兑换获取工兵名额 ❷提示兑换成功后把截图以及工兵报名表发送机器人 @qjttgbbot ❸工兵时效48小时,到期未出击或未提交报告取消工兵资格并拉黑 群内发送“报告”获取模板,报告提交 @qjttgbbot 📌工兵频道 📌报告频道 📌投诉售后 📌认证商家 🍗肯德基精选优质频道推荐 🏙肯德基最美好声音集合🗣

15 Nov 2026, 07:20 UTC452 views0 reactionsread 16 November 2026
Forwarded from @hzkdjcdPhoto

【花名】#泡泡糖 【联系】@cyhft678 【位置】#拱墅 【价格】#800p 【罩杯】#A 【标签】#嫩妹 #kiss #69互舔 【报告】报告1 报告2 报告3 报告4 🍗女友感,三点粉嫩水多 📌工兵频道 📌报告频道 📌投诉售后 📌认证商家 🍗肯德基精选优质频道推荐 🏙肯德基最美好声音集合🗣

15 Nov 2026, 04:49 UTC41 viewsread 15 November 2026
Forwarded from @hzkdjcdPhoto

【花名】#佳佳 【联系】@jiajia5478 【位置】#上城 【价格】#900p 【罩杯】#D 【标签】#嫩妹 #69互舔 #舌吻 【报告】报告1 🍗童颜巨乳 📌工兵频道 📌报告频道 📌投诉售后 📌认证商家

15 Nov 2026, 04:49 UTC41 viewsread 15 November 2026
Forwarded from @hzkdjcdPhoto

【花名】#思思 【联系】@A9Uio 【位置】#拱墅 【价格】#900p 【罩杯】#C 【标签】#嫩妹 #舌吻 #69互舔 【报告】报告1 报告2 报告3 报告4 报告5 报告6 报告7 🍗好评思思 📌工兵频道 📌报告频道 📌投诉售后 📌认证商家 🍗肯德基精选优质频道推荐 🏙肯德基最美好声音集合🗣

14 Nov 2026, 17:37 UTC623 viewsread 15 November 2026
Video

🍗肯德基上榜老师推荐 〰️〰️〰️〰️〰️〰️〰️〰️〰️ 🍐妍宝 清纯可爱型嫩妹,人照9分,女友感很强,服务主动可爱 🍐豆包 E奶嫩妹,喜欢大熊bbw的可以试试,带水中萧,奶头粉嫩 🍐司令令 素颜女大生,带水中萧,性价比还是可以的,蝴蝶逼,紧度很紧 🍐西西 人照9分嫩妹,黄白皮颜值很高,身材反馈都很不错 🍐怡宝 三点水嫩嫩妹,C胸,带水中萧800性价比嫩妹 🍐小璐 800档颜值嫩妹,水中萧也带,人照8.5分,带战袍舌吻管够,亲的时候就水汪汪,待调教。 🍐清宁 600性价比御姐,水多吊感都不错,姐姐很会,服务拉满 〰️〰️〰️〰️〰️〰️〰️〰️〰️ 以上内容均来自工兵报告摘要 榜单持续更新中~

14 Nov 2026, 15:11 UTC454 views1 reactionsread 15 November 2026
Forwarded from @hzkdjcdPhoto

【花名】#小雪 【联系】@hzxuexue07 【位置】#上城 【价格】#1200p 【罩杯】#B 【标签】#嫩妹 #69互舔 #舌吻 #白虎 #萝莉 【报告】报告1 报告2 报告3 报告4 报告5 🍗高颜值白虎萝莉 📌工兵频道 📌报告频道 📌投诉售后 📌认证商家 🍗肯德基精选优质频道推荐 🏙肯德基最美好声音集合🗣

❤1

14 Nov 2026, 12:00 UTC746 viewsread 15 November 2026
Photo

💐💐💐开奖了💐💐💐 慧中慧上榜福利 开奖了! 本期总参与人数: 5300 1- 看不厌 获得:400优惠卷 2- 酷半生 获得:400优惠卷 3- 抽烟伤心不伤肺 获得:400优惠卷 4- 你喜秋冬 获得:18.8口令 谨祝中奖用户大吉大利万事顺意

14 Nov 2026, 09:06 UTC658 views0 reactionsread 15 November 2026
Photo

【花名】#燕燕 【联系】@yanyan11211 【位置】#余杭 【价格】#700p 【罩杯】#C 【标签】#嫩妹 #舌吻 #69互舔 【报告】 🍗换装嫩妹 工兵优惠6折工兵2名 400p/800pp 剩余1 返回工兵链接 ❶群内发送兑换获取工兵名额 ❷提示兑换成功后把截图以及工兵报名表发送机器人 @qjttgbbot ❸工兵时效48小时,到期未出击或未提交报告取消工兵资格并拉黑 群内发送“报告”获取模板,报告提交 @qjttgbbot 📌工兵频道 📌报告频道 📌投诉售后 📌认证商家 🍗肯德基精选优质频道推荐 🏙肯德基最美好声音集合🗣

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

Posts recorded as deleted after publishing

We recorded 2 posts on @kdjyrny as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
27 August 2026
Most recent seen missing
4 November 2026
Median time before seen missing
25 hours
Seen missing in the last 30 days
1

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.

Mentions

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

“杭州肯德基工兵” (@kdjyrny), 20,851 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/kdjyrny.

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.