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

Channel
@yingditongzhijsq
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
10,211subscribers
-600 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002470780006 |
|---|---|
| Type | Channel |
| Username | @yingditongzhijsq |
| Created | Between 1 September 2024 and 31 March 2025 — 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/yingditongzhijsq |
Gaming — 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 88% 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 sits inside a group of 10 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 |
|---|---|---|---|
| @TY406/121777 Aug 2026, 17:27 UTC | @yingditongzhijsq/28133 · this entry8 Aug 2026, 08:53 UTC | 1.00 | 15 hours |
| @TY406/122178 Aug 2026, 04:31 UTC | @yingditongzhijsq/28767 · this entry17 Aug 2026, 11:56 UTC | 1.00 | 9 days |
| @TY406/1254912 Aug 2026, 17:55 UTC | @yingditongzhijsq/28534 · this entry12 Aug 2026, 20:46 UTC | 1.00 | 2.9 hours |
| @TY406/1272217 Aug 2026, 04:41 UTC | @yingditongzhijsq/28761 · this entry17 Aug 2026, 11:56 UTC | 1.00 | 7.2 hours |
| @TY406/1299622 Aug 2026, 13:33 UTC | @yingditongzhijsq/28901 · this entry25 Aug 2026, 15:26 UTC | 1.00 | 3 days |
| @TY406/1319326 Aug 2026, 15:02 UTC | @yingditongzhijsq/28963 · this entry26 Aug 2026, 18:16 UTC | 1.00 | 3.2 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @TY406 | 7 (7/7 hand-verifiable sample passed) | 1.00 | 7.2 hours | @TY406 (7–0) |
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. 7 of the 7 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 49 comparable posts for this entry, running 6 August 2026 to 2 September 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 10 channels, the one whose matching posts we hold earliest is @klzrr. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 14 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 10 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 |
|---|---|---|
| 15 Nov 2026, 15:51 | 10,211 | -51 |
| 12 Nov 2026, 07:59 | 10,262 | -18 |
| 10 Nov 2026, 09:21 | 10,280 | -35 |
| 8 Nov 2026, 19:46 | 10,315 | -26 |
| 7 Nov 2026, 12:40 | 10,341 | -16 |
| 6 Nov 2026, 10:10 | 10,357 | -32 |
| 5 Nov 2026, 07:01 | 10,389 | -60 |
| 4 Nov 2026, 05:17 | 10,449 | -14 |
| 3 Nov 2026, 04:48 | 10,463 | -3 |
| 2 Nov 2026, 04:50 | 10,466 | -58 |
| 1 Nov 2026, 03:58 | 10,524 | -15 |
| 31 Oct 2026, 01:38 | 10,539 | -16 |
| 30 Oct 2026, 03:20 | 10,555 | -10 |
| 29 Oct 2026, 01:58 | 10,565 | -3 |
| 28 Oct 2026, 00:27 | 10,568 | -11 |
| 26 Oct 2026, 21:55 | 10,579 | -8 |
| 25 Oct 2026, 21:07 | 10,587 | -4 |
| 24 Oct 2026, 21:16 | 10,591 | -19 |
| 23 Oct 2026, 19:18 | 10,610 | -4 |
| 22 Oct 2026, 17:27 | 10,614 | first reading |
134 posts held, back to 6 August 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 70 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 4 November 2026 |
|---|---|
| Posts held | 134 (6 August 2026 – 4 November 2026) |
| Views total | 1,490 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 00:10 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 18 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 6 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.
116 reactions across 73 posts, in 6 distinct kinds. The most used accounts for 69.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 81 | 69.8% | |
| ❤ | 27 | 23.3% | |
| 👎 | 5 | 4.31% | |
| 👏 | 1 | 0.862% | |
| 💩 | 1 | 0.862% | |
| 😱 | 1 | 0.862% |
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 76 of the 134 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 116 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 134 most recent posts we hold, published 6 August 2026 to 4 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: 0 of 1 post held from the last 30 days (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).
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_5842486647
👍3❤2
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_5842486647
❤2
🎮AX高系统 9.3王者 反馈
👍2
🎮噜噜大王 国际服定制周卡内部版本 反馈9月2日 🔥无视举报 明透 ✅周卡零售300 ✅支持13-26全系统签名或者巨魔安装! 全程会议教学 提卡https://wqfk.cn/shop/gddz
👍3
🎮 三角洲【ZOP】巨魔双版本,长期稳定不追封追缴 iOS 15.0─16.6.1 内部专用内核级 跨进程 完美解决切屏掉绘制 支持主播无痕与菜单缩放 ⚠️全功能版:追踪/自瞄/无后/暴力加速 暴力特征明显易被举 需自备防护 风险自负 ✅视觉单板:透视/雷达/物资/骨骼 不易察觉,高稳丝滑不掉针 主号带老板安全首选 💡注意:更新必重启手机 连接失败多试几次
🔥和平全系统【T3】已更新适配新版本龙狮城,优化防封,内测稳定奔放持续中,猛攻兄弟们 支持iOS13-26系统签名安装,支持任意签名工具 独家函数防封 极致流畅绘制 子弹追踪 打击加速 自动瞄准 掩体判断 无后据点 范围打击 全物资显示 支持地铁 上号即玩稳定持续中,杀疯了兄弟们
👍2
⚠️重要通知:明天和平精英版本更新,本次是非强制更新! 暂时不要更新游戏!! 等辅助适配更新完成之后,再升级版本,提前更新会导致辅助失效用不了
👍1
🎮王者荣耀AE满天星 百里梓瞄反馈 零售300 ✅全功能 绘制 视距 过行为 自瞄 ✅支持14-17.0系统 纯巨魔
👍1
🎮iOS-学习强国 9月2日反馈 🔋兼容14-17系统纯巨魔裸奔绘制 ✅无需端口,丝滑流畅 🏪每天稳定上分操作简单 提卡https://wqfk.cn/shop/gddz ⭐️代理批卡:@heziapp 打图私聊
👍1
Photo, posted without a caption
👍1
🟢Core-SK失控进化 iOS高系统内核V1.2(自签版) ✅绘制、追踪、自瞄、物资、自动采集 ⚡核心:iOS17-26高系统内核绘制 ✅功能说明:过直播、绘制、方框、骨骼、射线、距离、队编、血量、手持、领地柜、人数统计、自动采矿、漏打、掩体变色、自瞄、追踪、无后、聚点、物资箱等功能十分齐全 ✅ 非直装辅助!游戏客户端依旧使用App Store下载的失控进化客户端即可!辅助是独立的ipa文件,自签方式安装在设备上即可使用。 🍏Core自签版适配范围: iOS 17.0-18.7.0(支持) iOS 26.0.0(部分设备支持) 其中18.0.0/17.0.0系统不支持 iPhone17系列以及M5的iPad不支持 🎁零售指导30天/ 200周
👍1
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_5842486647
Showing the 12 most recent of 134 posts we hold for @yingditongzhijsq. 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.
@yingditongzhijsq edited 2 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.
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.
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 15 November 2026 — this entry's latest reading, not the date you are reading this.
“IOS王者/和平/三角洲/暗区/科技/通知” (@yingditongzhijsq), 10,211 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/yingditongzhijsq.
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.