❤️ 纸飞机无法加载登录使用? 现在免费开放高速代理链接,拒绝垃圾VPN加速器 只要使用代理就不需要VPN加速器,而且不违法‼️‼️‼️ 🔥 每天签到领取个人高速代理! 🎁 每日签到免费每天使用代理 🚀个人使用减少公共线路拥堵 ⚡️ 高速日常使用下载更加顺畅 📌 每天签到代理持续领取! 👍聊天群里 发送“ 签到 ” 获取专属代理 点我加入高速代理群聊获取代理 点我加入高速代理群聊获取代理
👍51❤1

Channel
@Sakurayyda
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Handles named that no longer answer · Cite this entry
57,072subscribers
+14,291 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002249533361 |
|---|---|
| Type | Channel |
| Username | @Sakurayyda |
| Created | 18 July 2024 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/Sakurayyda |
Technology — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 39% 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 7 other registered channels. 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 |
|---|---|---|---|
| @Sakurayyda/33395 · this entry30 Sept 2026, 14:59 UTC | @HeiXuePD/2982430 Sept 2026, 15:25 UTC | 1.00 | 26 minutes |
| @Sakurayyda/33826 · this entry10 Oct 2026, 05:31 UTC | @HeiXuePD/3176910 Oct 2026, 05:32 UTC | 1.00 | under a minute |
| @Sakurayyda/34291 · this entry19 Oct 2026, 10:30 UTC | @HeiXuePD/3287619 Oct 2026, 15:38 UTC | 1.00 | 5.1 hours |
| @pj7645/6312210 Oct 2026, 05:31 UTC | @Sakurayyda/33826 · this entry10 Oct 2026, 05:31 UTC | 1.00 | under a minute |
| @pj7645/6346715 Oct 2026, 08:47 UTC | @Sakurayyda/34118 · this entry15 Oct 2026, 08:47 UTC | 1.00 | under a minute |
| @pj7645/6368517 Oct 2026, 22:44 UTC | @Sakurayyda/34272 · this entry18 Oct 2026, 03:21 UTC | 1.00 | 4.6 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @HeiXuePD | 13 (8/8 hand-verifiable sample passed) | 1.00 | 62 minutes | this entry (8–5) |
| @pj7645 | 7 (7/7 hand-verifiable sample passed) | 1.00 | under a minute | this entry (4–3) |
| @TwT_driver | 11 (8/8 hand-verifiable sample passed) | 1.00 | 3.2 hours | this entry (6–5) |
| @yhtjdk | 9 (7/8 hand-verifiable sample passed) | 1.00 | 22 minutes | @yhtjdk (6–3) |
| @time_pd | 7 (7/7 hand-verifiable sample passed) | 1.00 | 2.4 hours | this entry (5–2) |
| @EO66789 | 6 (6/6 hand-verifiable sample passed) | 1.00 | under a minute | this entry (4–2) |
| @My_Name_Sheep | 7 (7/7 hand-verifiable sample passed) | 1.00 | under a minute | this entry (5–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. 8 of the 8 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 280 comparable posts for this entry, running 17 October 2025 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.
Recorded under the keys clone_copy · clone_mutual · clone_source, 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 21:51 | 57,072 | +103 |
| 11 Nov 2026, 23:18 | 56,969 | +553 |
| 10 Nov 2026, 02:58 | 56,416 | -2 |
| 8 Nov 2026, 14:56 | 56,418 | -7 |
| 7 Nov 2026, 08:25 | 56,425 | +61 |
| 6 Nov 2026, 05:31 | 56,364 | +107 |
| 5 Nov 2026, 07:47 | 56,257 | +846 |
| 4 Nov 2026, 04:17 | 55,411 | +13 |
| 3 Nov 2026, 07:11 | 55,398 | +65 |
| 2 Nov 2026, 07:20 | 55,333 | +340 |
| 1 Nov 2026, 05:37 | 54,993 | +247 |
| 31 Oct 2026, 02:49 | 54,746 | +411 |
| 29 Oct 2026, 23:10 | 54,335 | +119 |
| 28 Oct 2026, 21:35 | 54,216 | +244 |
| 27 Oct 2026, 22:00 | 53,972 | +645 |
| 26 Oct 2026, 19:55 | 53,327 | +222 |
| 25 Oct 2026, 20:59 | 53,105 | -76 |
| 23 Oct 2026, 21:36 | 53,181 | +1 |
| 22 Oct 2026, 19:21 | 53,180 | -7 |
| 21 Oct 2026, 16:41 | 53,187 | first reading |
599 posts held, back to 18 July 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 210 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.
| Window | Rolling 30 days · latest post in window 14 November 2026 |
|---|---|
| Posts held | 599 (18 July 2024 – 14 November 2026) |
| Views total | 423,406 |
| Reactions total | 12,355 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 20:40 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 28 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.
20,166 reactions across 595 posts, in 32 distinct kinds. The most used accounts for 91.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 18,408 | 91.3% | |
| ❤ | 1,149 | 5.70% | |
| 👏 | 225 | 1.12% | |
| 🥰 | 101 | 0.501% | |
| 🔥 | 88 | 0.436% | |
| 😁 | 45 | 0.223% | |
| 🎉 | 38 | 0.188% | |
| 🤔 | 20 | 0.099% | |
| 💩 | 13 | 0.064% | |
| 🤓 | 8 | 0.04% | |
| 😭 | 7 | 0.035% | |
| 🤡 | 7 | 0.035% | |
| ⚡ | 6 | 0.03% | |
| 👎 | 6 | 0.03% | |
| 😍 | 6 | 0.03% | |
| 🤣 | 5 | 0.025% | |
| 👀 | 4 | 0.02% | |
| 🙈 | 4 | 0.02% | |
| 🌚 | 3 | 0.015% | |
| 🌭 | 3 | 0.015% | |
| 12 further kinds | 20 | 0.099% |
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 596 of the 599 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 20,166 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 599 most recent posts we hold, published 18 July 2024 to 14 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.
Telegram’s own ‘edited’ marker: 8 of 217 posts held from the last 30 days (3.69%) 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).
❤️ 纸飞机无法加载登录使用? 现在免费开放高速代理链接,拒绝垃圾VPN加速器 只要使用代理就不需要VPN加速器,而且不违法‼️‼️‼️ 🔥 每天签到领取个人高速代理! 🎁 每日签到免费每天使用代理 🚀个人使用减少公共线路拥堵 ⚡️ 高速日常使用下载更加顺畅 📌 每天签到代理持续领取! 👍聊天群里 发送“ 签到 ” 获取专属代理 点我加入高速代理群聊获取代理 点我加入高速代理群聊获取代理
👍51❤1
AY全防 三角洲 三服 裸奔子弹追踪 自带解密 卡网 https://dg.001122.top/shop/DCO7DPS4 TG群 https://t.me/cfsYYDSAN 反馈以及各种问题↓ t.me/cfsYYDSAN?direct
👍65❤1
此频道已经被官方盯上了.即将停止使用.点击下面蓝色字体进入新频道更新⬇️⬇️ 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道
👍84❤3🤓2
我操他妈的电报上骗子怎么这么多啊!!直到我遇到他 @adggnbkefu 我才知道一小时可以挣1988元 目前已经拿下苹果18了😁
👍73👎1🤔1😭1
大肥鱼2.5三角洲公益算法解密 11.13最新更新解密 下载地址 📥📥📥📥📥📥📥📥📥📥 https://pan.quark.cn/s/6061a5d18530 更新日志 更新适配新算法解密 适配最新par驱动 优化辅助卡顿 ✈️大肥鱼新手/老手不会使用的点我查看视频和文字教程 公益卡密: 联系机器人获取 @bbblajibot ❗️❗️➡️ 点我加入官方频道 ❗️❗️➡️ 点我加入官方群组 收费解密都不一定有我这个好,长期稳定更新公益解密辅助
👍85❤3😭3
🔍 发送关键词来寻找群组、频道或视频。 🫰各种爆火资源都可以搜索🧑🎓 🧸都是独一无二的搜索结果🧒 🤡频道主都推荐这个🤟 🤯超多不限量火爆资源应有尽有🤝 🌈无延迟 无重复 无卡顿 无没结果🤙
👍97
三角洲台服/国际服/越南服_SDK 开发者使用 通知频道 @Sakurayyda 交流群 @EngineHacker
👍109
三角洲越南服要适配吗
👍101🤔6🔥3👏2❤1👎1
半夜想要看片👀找不到的各种资源群里都可以搜索的到 🔍 相关游戏外挂安装包也可以搜的到 关键词:萝莉 黑丝 御姐 少萝 白丝 老师 洛丽塔 JK 等等 ⬇️⬇️⬇️⬇️⬇️⬇️⬇️ https://t.me/sos73781 https://t.me/sos73781 https://t.me/sos73781
👍76
最近出现一种骗局,他会当做你的朋友或者谁的拉你进一个ai作图群然后让你下东西,下了你的号就没了
👍95👏4🤔4👎1
我操他妈的电报上骗子怎么这么多啊!!直到我遇到他 @adggnbkefu 我才知道一小时可以挣1988元 目前已经拿下苹果18了😁
👍89🤔2
三角洲大肥鱼国服永久公益解密内核 认准:BIG FAT FISH(大肥鱼) 已适配三角洲最新S12赛季 采用算法/udp双解密方案 正在永久公益中!正在永久公益中! ❤️ 支持设备:安卓 ROOT ❤️ 支持内核:4.x - 6.x 全系 ❤️支持天机/骁龙 处理器 ❤️支持区服:C国服 ❤️支持模式:内核/纯c 功能说明🎚 ✅方框 ✅骨骼 ✅干员 ✅血量 ✅距离 ✅手持 ✅头甲 ✅物资 🟢全图模型漏打 🟢战斗模式 🟢添加独立大小雷达 ✅自瞄配置:陀螺仪自瞄+触摸自瞄 🔗下载安装包 ✔️大肥鱼点我公益解密卡密 ✈️大肥鱼新手/老手不会使用的点我查看视频和文字教程 🌟🙃🌟➡️ @BIGFATFISH6 🎉肥鱼我呀会坚持一直一直一直工艺下去哒!
👍105❤1🤔1
Showing the 12 most recent of 599 posts we hold for @Sakurayyda. 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.
@Sakurayyda edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
We recorded 12 posts on @Sakurayyda 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
需要先更新哪个游戏
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 599 most recent posts we hold, published 18 July 2024 to 14 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
Named by 36 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
@Sakurayyda named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“啊米诺思(KX追踪)” (@Sakurayyda), 57,072 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/Sakurayyda.
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.