🎁 新人抢券 · 红包 × 50 🔒 需真人验证 🎉 50 份已全部抢完 🧧 猫猫 抢到 红包 🧧 痕迹 抢到 红包 🧧 soso 抢到 红包 🧧 噜妹 抢到 红包 🧧 钰钰 抢到 红包 🧧 汉堡 抢到 红包 🧧 社 抢到 红包 🧧 我也要死... 抢到 红包 🧧 水煮鱼 抢到 红包 🧧 落幕 抢到 红包 🧧 银蛇 抢到 红包 🧧 @k7i... 抢到 红包 🧧 凯 抢到 红包 🧧 陈攻仁 抢到 红包 🧧 落泪 抢到 红包 ……
❤5🫡2

Channel
@ysys
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
148,987subscribers
+124,580 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1002209437636 |
|---|---|
| Type | Channel |
| Usernames | @oy333 @ysys |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 121 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/ysys |
Gambling & betting — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 69% 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.
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 in near-verbatim form on 4 other registered channels. This entry also sits inside a group of 5 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @zuanshi/31189 Aug 2026, 03:33 UTC | @ysys/2680 · this entry9 Aug 2026, 03:34 UTC | 1.00 | under a minute |
| @zuanshi/312010 Aug 2026, 03:33 UTC | @ysys/2683 · this entry10 Aug 2026, 03:34 UTC | 1.00 | under a minute |
| @ysys/2695 · this entry12 Aug 2026, 03:32 UTC | @zuanshi/312412 Aug 2026, 03:32 UTC | 1.00 | under a minute |
| @ysys/2701 · this entry14 Aug 2026, 03:31 UTC | @zuanshi/312814 Aug 2026, 03:31 UTC | 1.00 | under a minute |
| @zuanshi/313016 Aug 2026, 03:55 UTC | @ysys/2709 · this entry16 Aug 2026, 03:55 UTC | 1.00 | under a minute |
| @zuanshi/313117 Aug 2026, 01:57 UTC | @ysys/2711 · this entry17 Aug 2026, 01:57 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @zuanshi | 21 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @zuanshi (16–5) |
| @onix | 9 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (5–4) |
| @ysdb | 7 (7/7 hand-verifiable sample passed) | 1.00 | 72 seconds | @ysdb (6–1) |
| @gaoxin | 6 (6/6 hand-verifiable sample passed) | 1.00 | under a minute | @gaoxin (4–2) |
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. 30 of the 30 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 40 comparable posts for this entry, running 20 July 2026 to 22 October 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.
Of the group of 5 channels, the one whose matching posts we hold earliest is @ysys — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual, 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.
This channel is in a group of 5 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 15:01 | 148,987 | -224 |
| 9 Nov 2026, 20:49 | 149,211 | +127,038 |
| 9 Nov 2026, 20:21 | 22,173 | -127,196 |
| 8 Nov 2026, 14:09 | 149,369 | +127,161 |
| 8 Nov 2026, 11:19 | 22,208 | -127,221 |
| 7 Nov 2026, 11:16 | 149,429 | +127,155 |
| 7 Nov 2026, 03:19 | 22,274 | -127,070 |
| 6 Nov 2026, 08:59 | 149,344 | +127,015 |
| 6 Nov 2026, 02:09 | 22,329 | -127,026 |
| 5 Nov 2026, 10:25 | 149,355 | +127,005 |
| 5 Nov 2026, 02:14 | 22,350 | -126,988 |
| 4 Nov 2026, 10:16 | 149,338 | +126,934 |
| 3 Nov 2026, 23:55 | 22,404 | -120,480 |
| 3 Nov 2026, 09:31 | 142,884 | +120,448 |
| 3 Nov 2026, 00:46 | 22,436 | -98,938 |
| 2 Nov 2026, 09:29 | 121,374 | +98,920 |
| 1 Nov 2026, 23:01 | 22,454 | -77,773 |
| 1 Nov 2026, 07:15 | 100,227 | +77,692 |
| 31 Oct 2026, 19:57 | 22,535 | -85,279 |
| 31 Oct 2026, 09:41 | 107,814 | first reading |
77 posts held, back to 20 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 126 pages of Telegram’s post history, 20 posts per page.
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 3 of 4 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 22 October 2026 |
|---|---|
| Posts held | 77 (20 July 2026 – 22 October 2026) |
| Views total | 6,570 |
| Reactions total | 16 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 09:59 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.
Measured directly from 27 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.
268 reactions across 46 posts, in 12 distinct kinds. The most used accounts for 58.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 157 | 58.6% | |
| 👍 | 52 | 19.4% | |
| 💩 | 14 | 5.22% | |
| 🤣 | 12 | 4.48% | |
| 👏 | 11 | 4.10% | |
| 😱 | 9 | 3.36% | |
| 👎 | 5 | 1.87% | |
| 🤮 | 3 | 1.12% | |
| 🫡 | 2 | 0.746% | |
| 👌 | 1 | 0.373% | |
| 🔥 | 1 | 0.373% | |
| 🙏 | 1 | 0.373% |
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 47 of the 77 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 268 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 77 most recent posts we hold, published 20 July 2026 to 22 October 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.
Telegram’s own ‘edited’ marker: 1 of 4 posts held from the last 30 days (25.0%) 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).
🎁 新人抢券 · 红包 × 50 🔒 需真人验证 🎉 50 份已全部抢完 🧧 猫猫 抢到 红包 🧧 痕迹 抢到 红包 🧧 soso 抢到 红包 🧧 噜妹 抢到 红包 🧧 钰钰 抢到 红包 🧧 汉堡 抢到 红包 🧧 社 抢到 红包 🧧 我也要死... 抢到 红包 🧧 水煮鱼 抢到 红包 🧧 落幕 抢到 红包 🧧 银蛇 抢到 红包 🧧 @k7i... 抢到 红包 🧧 凯 抢到 红包 🧧 陈攻仁 抢到 红包 🧧 落泪 抢到 红包 ……
❤5🫡2
红包 https://t.me/ZuanshiYuceBot?start=ref_B42T3JUK
天才交易员开赛|本周盈利第一,独拿 100 USDT! @ZuanshiYuceBot
👍3
🎁 新人抢券 · 红包 × 50 🎉 50 份已全部抢完 🧧 兴和 抢到 红包 🧧 菠萝小薇 抢到 红包 🧧 静冷 抢到 红包 🧧 sad. 抢到 红包 🧧 悲伤 抢到 红包 🧧 空白 抢到 红包 🧧 大肘子 抢到 红包 🧧 冷静 抢到 红包 🧧 逢赌必赢 抢到 红包 🧧 宝妈 抢到 红包 🧧 白泽 抢到 红包 🧧 明月 抢到 红包 🧧 序幕 抢到 红包 🧧 八方来财 抢到 红包 🧧 幼 抢到 红包 ……
❤5🔥1
人生如弈,落子无悔。
👍8❤6
人生没有白走的路,低谷也算数。
👏7❤3
口令:罚款红包
🧧 钻石纠纷... 发送了一个红包 [拼手气口令红包] 总金额:50USDT 剩余(50/50) 输入正确口令后可领取
t.me/wwwkm 此公群老板违规操作罚款100USDT
🤣12😱9💩6❤3🙏1
押金不是越多越好,适合自己才最重要 从当年的汇旺,到如今的新币。 一次次行业风波都在告诉我们:树大招风,人怕出名猪怕壮,枪打出头鸟!担保平台没有绝对安全的,资金过度集中本身就是风险。 所以钻石想提醒所有公群老板: 不要攀比押金,量力而行。 500U就做500U的业务,1000U就做1000U的业务,根据自己的真实业务量合理上押。 生意好不好,从来不是看谁押金多。 真正好的担保,无论押金多少,都应该有流量、有生意。 即日起,转移入驻钻石担保的符合条件公群,可享:800U 资金扶持,可用于供需广告、购买管理、超级索引 @cjsy 广告位等推广消费。 少一点押金攀比,多一点资金安全。 💎钻石恒久远|担保永流传! —— 钻石担保
👍17❤10👏4
飞机第一课。
❤6
😃😃😃😃 提醒您: 😃公群2795 供押500u 全网最稳微信im 话术不死号 量最大 🧧 超狂钻石活动红包将于😄😄:😄😄发放! 😃公群211 供押550u 【租号换钱•诚达公司《咸鱼代聊/PCZM》超强续租•不掉一直续】 🧧超狂钻石活动红包将于😄😄:😄😄发放! 💎 钻石福利限时放送 🎁 幸运惊喜持续掉落 🧧请于当日00:00前领取红包后联系 @ssll 领取活动钻石,过时不统计。 关注钻石官方 @zuanshi,每天预告发红包位置 关注钻石公群导航 @ZSGQ,最新做单情报,尽在这里! 😃😃😃😃😃😃 钻石久远,富贵永恒
❤4
Showing the 12 most recent of 77 posts we hold for @ysys. 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.
We recorded 8 posts on @ysys 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.
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 3 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.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“夏天供需5u/条发布@yuyi” (@ysys), 148,987 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/ysys.
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.