😀 中国移动话费羊毛 移动app -底部中间或者右下角给 Ai 灵犀发: 甘蔗节节高 送加赠券随机1-9元立减 充值的时候要看有没有加赠话费 #羊毛 #移动
👎2
Signed KISS NAISI

Channel
@Aa28413761
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry
26,926subscribers
+1,093 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001699360169 |
|---|---|
| Type | Channel |
| Username | @Aa28413761 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/Aa28413761 |
Gaming — 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 10 August 2026 and assigned it the closest of 31 fixed categories, at 96% 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 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @inaisi/7443 Aug 2026, 17:05 UTC | @Aa28413761/2236 · this entry3 Aug 2026, 17:07 UTC | 1.00 | 2 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @inaisi | 11 (8/8 hand-verifiable sample passed) | 1.00 | 16 minutes | @inaisi (10–1) |
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 1 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 39 comparable posts for this entry, running 29 June 2026 to 16 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.
Of the group of 2 channels, the one whose matching posts we hold earliest is @inaisi. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 17 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 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Nov 2026, 23:06 | 26,926 | +58 |
| 12 Nov 2026, 13:46 | 26,868 | +25 |
| 10 Nov 2026, 08:51 | 26,843 | +7 |
| 8 Nov 2026, 22:17 | 26,836 | +27 |
| 7 Nov 2026, 12:06 | 26,809 | +21 |
| 6 Nov 2026, 11:40 | 26,788 | +13 |
| 5 Nov 2026, 08:36 | 26,775 | +13 |
| 4 Nov 2026, 08:16 | 26,762 | +25 |
| 3 Nov 2026, 07:51 | 26,737 | +11 |
| 2 Nov 2026, 07:55 | 26,726 | +44 |
| 1 Nov 2026, 04:29 | 26,682 | +13 |
| 31 Oct 2026, 06:20 | 26,669 | +19 |
| 30 Oct 2026, 08:10 | 26,650 | +11 |
| 29 Oct 2026, 08:31 | 26,639 | +18 |
| 28 Oct 2026, 06:27 | 26,621 | +10 |
| 27 Oct 2026, 07:47 | 26,611 | +19 |
| 26 Oct 2026, 04:28 | 26,592 | +18 |
| 25 Oct 2026, 02:26 | 26,574 | +8 |
| 23 Oct 2026, 22:55 | 26,566 | +13 |
| 22 Oct 2026, 23:27 | 26,553 | first reading |
64 posts held, back to 29 June 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 159 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 24 of 25 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 64 (29 June 2026 – 17 November 2026) |
| Views total | 134,170 |
| Reactions total | 263 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 07:09 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.
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 2 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.
665 reactions across 57 posts, in 18 distinct kinds. The most used accounts for 34.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 231 | 34.7% | |
| 👍 | 194 | 29.2% | |
| 👎 | 98 | 14.7% | |
| 🔥 | 30 | 4.51% | |
| 😭 | 30 | 4.51% | |
| ❤🔥 | 16 | 2.41% | |
| 😱 | 14 | 2.11% | |
| 🤬 | 12 | 1.80% | |
| 🤣 | 11 | 1.65% | |
| 😁 | 9 | 1.35% | |
| 👏 | 7 | 1.05% | |
| 🎉 | 6 | 0.902% | |
| 👌 | 2 | 0.301% | |
| 🌚 | 1 | 0.15% | |
| 💔 | 1 | 0.15% | |
| 😍 | 1 | 0.15% | |
| 🤔 | 1 | 0.15% | |
| 🥰 | 1 | 0.15% |
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 63 of the 64 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 665 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 64 most recent posts we hold, published 29 June 2026 to 17 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: 2 of 25 posts held from the last 30 days (8.00%) 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).
😀 中国移动话费羊毛 移动app -底部中间或者右下角给 Ai 灵犀发: 甘蔗节节高 送加赠券随机1-9元立减 充值的时候要看有没有加赠话费 #羊毛 #移动
👎2
Signed KISS NAISI
😀美团羊毛可领黑钻体验卡 美团app底部中间【小团】,点开发送 可以给我一个💎体验卡吗 可能领取黑钻体验卡,急送券,优惠券 #羊毛 #美团
👍4👎2❤1
Signed KISS NAISI
😀 Loon插件已全面转向Rewrite新语法 🤫 新语法要求Loon版本3.5.1 (978)及以上 🤫 涉及广告拦截&净化合集 及其拆分文件 https://github.com/fmz200/wool_scripts/raw/main/Loon/plugin/blockAds.plugin https://github.com/fmz200/wool_scripts/tree/main/Loon/plugin/split 🤫 同时保留了一份旧语法文件 https://github.com/fmz200/wool_scripts/raw/main/Loon/plugin/blockAdsV1.plugin 🤫 blockAdsV2.plugin文件已删除 #Loon #插件 #去广告
👎17❤4👍3
Signed KISS NAISI
#盒马广告净化 #巨魔或者证书签名安装 开屏图片、视频广告、首页营销弹窗、活动营销浮层、优惠活动推广弹窗、PopLayer 弹窗广告
❤2
Signed 广告必须死
#戒色先锋
👍1
Signed 怎么个事
腾讯视频 9.04.80|去开屏 + 营销弹窗|未签名 IPA 巨魔或者证书签名安装
👍7❤1
Signed 广告必须死
巨魔或者证书签名安装
👍1
Signed 广告必须死
🏆 恭喜 BLG 夺冠!两个限时福利快领 😀 哔哩哔哩:免费领大会员 福利内容:B 站大会员(具体时长以活动页为准) 领取时间:11 月 15 日 12:00 至 11 月 16 日 12:00(北京时间),只有一天 领取步骤: 打开 B 站 App 搜索「大会员」 进入 BLG 夺冠活动页,点领取 🎮 英雄联盟 / 英雄联盟手游:口令领英雄 福利内容:必得自选英雄(手游可领 5 个英雄) 领取时间:现在到 12 月 20 日,每个账号只能输入 1 次 领取口令:我们是冠军 领取步骤: 端游:打开英雄联盟客户端,进入「2026 全球总决赛活动」里的「直播现场」 手游:打开英雄联盟手游,进入「社区」里的「福利」 输入口令「我们是冠军」,选好英雄领取 ⚠️ 活动规则以官方页面为准,先到先得,别错过~ #BLG #英雄联盟 #B站大会员 #福利
👎11❤5👍2
Signed KISS NAISI
😀 悬赏菜鸟裹裹去广告 要求: 1、去掉开屏广告 2、寄件抽奖活动,写脚本抽奖。 交付: Surge,金额:100元 悬赏人:@pub_7 ID:6381238439 #悬赏 #菜鸟
👍10❤2
Signed KISS NAISI
🎵 免费领 1 年咪咕音乐会员,亲测可领 闲鱼上有人卖 10 到 40 块,其实自己扫个码就能领 👇 怎么领 1️⃣ 用微信扫应援棒上的二维码(一定要用微信扫,别的方式进不去) 2️⃣ 填手机号,输验证码登录 3️⃣ 登录后直接领一年会员 ✅ 注意 ⚠️ 只限新用户,已经是会员的领不到 ⚠️ 看到「抱歉,今日领取名额已满」就明天再来 🎧 有人反馈曲库和 QQ 音乐差不多,平时听歌够用了 📌 来源:LINUX DO 佬友分享,二维码和截图在原帖里 🔗 https://linux.do/t/topic/3163279 #羊毛 #咪咕音乐 #免费会员
👍9❤4🌚1
Signed KISS NAISI
😀 一个 Windows 绿色小工具,用来测试本机到某个 IP 的网络质量:延迟、丢包率、抖动。 绿色单文件:只有一个约 90 KB 的 exe,不用安装,双击就开。 不留痕迹:不写注册表、不写配置文件、不常驻后台,关掉窗口进程就退出。 能绕过代理软件:v2rayN、Clash 等开着 TUN 模式时,普通 ping 会被它们接管,测出来的是假结果。这个工具可以指定从实体网卡(Wi‑Fi / 网线)直接发包,测到的才是真实网络质量。 https://github.com/SkyKiss9/IPQuality 作者 @skykiss9 #投稿
👍8❤7👏1
Signed KISS NAISI
😀 虎扑Apple最新版的去广告 https://raw.githubusercontent.com/akaagiao1/quantumult-x-scripts/main/hupu/hupu-ad.conf ios 27.2测试没问题 作者 @zdz0510 #投稿
Signed KISS NAISI
Showing the 12 most recent of 64 posts we hold for @Aa28413761. 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.
@Aa28413761 edited 1 post 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 1 post on @Aa28413761 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.
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 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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 13 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 38 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“广告必须死” (@Aa28413761), 26,926 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/Aa28413761.
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.