Telegram RegisterThe public register of Telegram
Telegram profile photo for 桃花优惠频道

Channel

桃花优惠频道

@szkanhua

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

7,764subscribers

-382 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002487927697
TypeChannel
Username@szkanhua
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 16 August 2026
On Telegramt.me/szkanhua

Topic

Giveaways & airdrops — 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 90% 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. 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
@szpeachb/1482318 Jul 2026, 13:52 UTC@szkanhua/1108 · this entry18 Jul 2026, 13:52 UTC1.00under a minute
@szkanhua/1110 · this entry20 Jul 2026, 12:00 UTC@szpeachb/1482620 Jul 2026, 12:00 UTC1.00under a minute
@szpeachb/1482720 Jul 2026, 14:45 UTC@szkanhua/1111 · this entry20 Jul 2026, 14:45 UTC1.00under a minute
@szpeachb/1483022 Jul 2026, 14:45 UTC@szkanhua/1114 · this entry22 Jul 2026, 14:45 UTC1.00under a minute
@szpeachb/1484031 Jul 2026, 05:40 UTC@szkanhua/1117 · this entry31 Jul 2026, 05:41 UTC1.00under a minute
@szkanhua/1118 · this entry2 Aug 2026, 12:24 UTC@szpeachb/148432 Aug 2026, 12:24 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@szpeachb7 (7/7 hand-verifiable sample passed)1.00under a minutethis entry (52)

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 2 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 14 comparable posts for this entry, running 18 July 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 2, the earliest publisher we hold is @szpeachb. 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.

Also posting the same content

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.

Growth

7,7648,1757,969.57 August 2026 — 8,146 subscribers7 August 2026 — 8,149 subscribers10 August 2026 — 8,175 subscribers13 August 2026 — 7,764 subscribers7 August 202613 August 2026
4 measurements spanning 6 days, net -382. 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 7,702–8,237 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 07:447,764-411
10 Aug 2026, 16:118,175+26
7 Aug 2026, 22:368,149+3
7 Aug 2026, 13:028,146first reading

Engagement

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

ERR · 30 days
3.35%
avg views ÷ 7,764 subscribers
Avg views / post
260
32 posts measured
Reaction rate
0.35%
reactions ÷ views · ER floor
Posts in window
32
of 32 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 1 of 32 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 12 August 2026
Posts held32 (18 July 202612 August 2026)
Views total8,312
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 16:41 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

Video runtime
32s
Average length
11s

Measured directly from 3 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

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

Measured over the 32 most recent posts we hold, published 18 July 2026 to 12 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

12 Aug 2026, 08:22 UTC78 viewsread 12 August 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178634277644 🎰 宝安沐沐优惠抽奖 ⚠️ 抽奖说明: 1. 兑奖请联系 @zyp168 2. 开奖后七天内兑换,优惠要提交报告 3. 炸号者中奖作废。 💁 参与人数:212人 🎅 联系领奖:王老邪 1. 能工智人 奖品:100优惠券 2. 潋潋‌ 奖品:100优惠券 3. 十宗罪 奖品:100优惠券 4. emo 奖品:100优惠券 5. Wen Zhuang 奖品:100优惠券 6. Silas 奖品:18口令红包 7. 千纸鹤 奖品:18口令红包 祝大家心想事成好运连连!

12 Aug 2026, 06:05 UTC82 viewsread 12 August 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178633807029 🎰 南山楚楚优惠抽奖 ⚠️ 抽奖说明: 1. 兑奖请联系 @chu3400 2. 开奖后七天内兑换,优惠要提交报告 3. 炸号者中奖作废。 💁 参与人数:114人 🎅 联系领奖:王老邪 1. Einar 奖品:200通用优惠券 2. 烬余灰 奖品:200通用优惠券 3. 脆鲨 奖品:200通用优惠券 4. 咛雾 奖品:200通用优惠券 5. Jerry 奖品:200通用优惠券 6. 慢半拍 奖品:200通用优惠券 7. TL 奖品:200通用优惠券 8. chenhaonan 奖品:200通用优惠券 9. 阿斯匹林 奖品:200通用优惠券 10. 皇冠梨很好吃 奖品:200通用优惠券 11. NULLST 奖品:8.8口令红包 12. Frederick 奖品:8.8口令红包 13. Orion 奖品:8.8口令红包 祝大家心想事成好运连连!

11 Aug 2026, 11:53 UTC116 viewsread 12 August 2026
Photo

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

11 Aug 2026, 11:53 UTC109 viewsread 12 August 2026
Photo

南山绾绾优惠活动: p优惠88✖️3 pp优惠188✖️3 联系:@wanwancsb 频道:https://t.me/wanwanyaoya (自行联系老师领取)

11 Aug 2026, 11:30 UTC109 viewsread 12 August 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178627482133 🎰 南山米娜优惠抽奖 ⚠️ 抽奖说明: 1. 兑奖请联系 @szmina04 2. 开奖后七天内兑换,优惠要提交报告 3. 炸号者中奖作废。 💁 参与人数:183人 🎅 联系领奖:王老邪 1. 想看雪 奖品:p优惠100 2. 汪星人 奖品:p优惠100 3. 零落浮华 奖品:p优惠100 4. Nyx 奖品:p优惠100 5. 泼彩星河 奖品:p优惠100 6. 上山打老虎 奖品:pp优惠200 7. 书亦烧仙草 奖品:pp优惠200 8. 光年之外 奖品:pp优惠200 9. Dorian 奖品:pp优惠200 10. Elliott 奖品:pp优惠200 11. 九五二七 奖品:8.8口令红包 12. TL 奖品:8.8口令红包 13. 斷舍離 奖品:8.8口令红包 14. 等风来 奖品:8.8口令红包 15. 你打我噻 奖品:8.8口令红包

11 Aug 2026, 07:58 UTC117 viewsread 12 August 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178625449553 🎰 南山柯美优惠抽奖 ⚠️ 抽奖说明: 1. 兑奖请联系 @kemeixa 2. 开奖后七天内兑换,优惠要提交报告 3. 炸号者中奖作废。 💁 参与人数:12人 🎅 联系领奖:王老邪 1. 臭弟弟 奖品:pp优惠100 2. Jackson He... 奖品:pp优惠100 3. world li 奖品:pp优惠100 4. Tugf 奖品:pp优惠100 5. Jia Mr 奖品:pp优惠100 6. huang 奖品:包时优惠200 7. Roy dick 奖品:包时优惠200 8. 李 夫鱼 奖品:包时优惠200 9. Luke Morga... 奖品:包时优惠200 10. king jac 奖品:包夜优惠300 11. peter wang 奖品:包夜优惠300 12. 我溜了 奖品:包夜优惠300 祝大家心想事成好运连连!

10 Aug 2026, 06:22 UTC247 viewsread 12 August 2026
Photo

🎰 宝安沐沐优惠抽奖 📮 参与条件: 🌏️ 归属地 广东 🪪 必须设置用户名 🎫 加入-🌹沐沐的后宫🌹 🎫 加入-桃花优惠频道 🎁 奖品内容: 💰️ 100优惠券 × 5 💰️ 18口令红包 × 2 ⚠️ 抽奖说明: 1. 兑奖请联系 @zyp168 2. 开奖后七天内兑换,优惠要提交报告 3. 炸号者中奖作废。 📅 开奖日期:(北京时间) 2026年08月12日 16时22分00秒

10 Aug 2026, 05:04 UTC152 viewsread 12 August 2026
Photo

🎰 南山楚楚优惠抽奖 📮 参与条件: 🌏️ 归属地 广东 🪪 必须设置用户名 🎫 加入-暑假工学生妹的秘密 🎫 加入-桃花优惠频道 🎁 奖品内容: 💰️ 200通用优惠券 × 10 💰️ 8.8口令红包 × 3 ⚠️ 抽奖说明: 1. 兑奖请联系 @chu3400 2. 开奖后七天内兑换,优惠要提交报告 3. 炸号者中奖作废。 📅 开奖日期:(北京时间) 2026年08月12日 14时05分00秒

9 Aug 2026, 12:00 UTC165 viewsread 12 August 2026

抽奖初音疗愈抓龙筋SP抽奖(编号L178611557694)已成功开奖: 已参与人数:1341 中奖名单如下: TL[6595884144](奖品为100米优惠卷) 大人拾答辩了[6717472342](奖品为12.88瑞幸咖啡) 再战五百年[6813538573](奖品为100米优惠卷) 鱼桑(学生勿踢)[7814808045](奖品为12.88瑞幸咖啡) Alaric[8036460246](奖品为100米优惠卷) 薄荷冰淇淋[8040611912](奖品为100米优惠卷) 生情[8135617559](奖品为100米优惠卷) 菊花一惊[8721258854](奖品为12.88瑞幸咖啡)

9 Aug 2026, 11:31 UTC238 viewsread 12 August 2026
Photo

🎰 南山米娜优惠抽奖 📮 参与条件: 🌏️ 归属地 广东 🪪 必须设置用户名 🎫 加入-南山米娜🌈个人首开 🎫 加入-桃花优惠频道 🎁 奖品内容: 💰️ 8.8口令红包 × 5 💰️ pp优惠200 × 5 💰️ p优惠100 × 5 ⚠️ 抽奖说明: 1. 兑奖请联系 @szmina04 2. 开奖后七天内兑换,优惠要提交报告 3. 炸号者中奖作废。 📅 开奖日期:(北京时间) 2026年08月11日 19时30分00秒

9 Aug 2026, 05:59 UTC203 viewsread 12 August 2026
Photo

🎰 南山柯美优惠抽奖 📮 参与条件: 🌏️ 归属地 广东 🪪 必须设置用户名 🎫 加入-柯美的后宫三千 🎫 加入-桃花优惠频道 🎁 奖品内容: 💰️ pp优惠100 × 5 💰️ 包夜优惠300 × 5 💰️ 包时优惠200 × 5 ⚠️ 抽奖说明: 1. 兑奖请联系 @kemeixa 2. 开奖后七天内兑换,优惠要提交报告 3. 炸号者中奖作废。 📅 开奖日期:(北京时间) 2026年08月11日 15时58分00秒

7 Aug 2026, 15:15 UTC230 viewsread 12 August 2026
Photo

抽奖汇总: https://t.me/pbluckydraw 🎟️ 抽奖标题:初音疗愈抓龙筋SP抽奖 📪抽奖说明:中奖者机器人会发送中奖信息 1. 兑奖请联系 @GK388633 2. 开奖后七天内兑换,优惠要提交报告 3. 炸号者中奖作废。 中奖者请私聊标题当事人领取,领取优惠的需写报告 🎁 奖品内容: 💰️ 100米优惠卷 × 5 💰️ 12.88瑞幸咖啡 × 3 🎫 参与条件: 🎫 必须有用户名 🎫 加入-南山 初音· あんじ 疗愈私密抓龙筋SPA 🎫 加入-桃花优惠频道 📅 开奖时间:2026-08-09 20:00自动开奖 👉 参与抽奖链接: https://t.me/pbluckydraw_bot?start=join-L178611557694

Showing the 12 most recent of 32 posts we hold for @szkanhua. 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 — 539,111 of 1,481,243entries 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.

Mentions

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

“桃花优惠频道” (@szkanhua), 7,764 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/szkanhua.

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.