不定时清理僵尸粉,请加入频道主创建的资源群,以防止被误踢 请加入 https://t.me/+COrvbGVdkVZhZGI1 感谢大家的支持,小弟在这谢谢大家了
👍2

Channel
@xuendj1
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
97,383subscribers
+5,341 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002173649713 |
|---|---|
| Type | Channel |
| Username | @xuendj1 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/xuendj1 |
Education — 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 99% 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 |
|---|---|---|---|
| @xuendj1/380157 · this entry19 Aug 2026, 08:15 UTC | @fjwqwr/17829519 Aug 2026, 08:15 UTC | 1.00 | under a minute |
| @xuendj1/410770 · this entry3 Nov 2026, 02:18 UTC | @fjwqwr/1988403 Nov 2026, 02:19 UTC | 1.00 | under a minute |
| @xuendj1/413386 · this entry8 Nov 2026, 08:42 UTC | @fjwqwr/2006058 Nov 2026, 08:42 UTC | 1.00 | under a minute |
| @xuendj1/413393 · this entry8 Nov 2026, 08:45 UTC | @fjwqwr/2006108 Nov 2026, 08:45 UTC | 1.00 | under a minute |
| @xuendj1/414412 · this entry10 Nov 2026, 04:01 UTC | @fjwqwr/20128410 Nov 2026, 04:01 UTC | 1.00 | under a minute |
| @xuendj1/415408 · this entry12 Nov 2026, 02:34 UTC | @fjwqwr/20196212 Nov 2026, 02:34 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @fjwqwr | 288 (6/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (288–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. None of the 0 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 1,977 comparable posts for this entry, running 7 August 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 @xuendj1 — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, 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 |
|---|---|---|
| 16 Nov 2026, 15:09 | 97,383 | +145 |
| 13 Nov 2026, 00:56 | 97,238 | +107 |
| 10 Nov 2026, 17:56 | 97,131 | +48 |
| 9 Nov 2026, 03:21 | 97,083 | +29 |
| 7 Nov 2026, 17:10 | 97,054 | +23 |
| 6 Nov 2026, 18:39 | 97,031 | +25 |
| 5 Nov 2026, 21:37 | 97,006 | +57 |
| 4 Nov 2026, 18:50 | 96,949 | +47 |
| 3 Nov 2026, 18:49 | 96,902 | +74 |
| 2 Nov 2026, 18:55 | 96,828 | +90 |
| 1 Nov 2026, 16:18 | 96,738 | +34 |
| 31 Oct 2026, 13:05 | 96,704 | +57 |
| 30 Oct 2026, 09:27 | 96,647 | +44 |
| 29 Oct 2026, 06:41 | 96,603 | +58 |
| 28 Oct 2026, 04:41 | 96,545 | +46 |
| 27 Oct 2026, 08:11 | 96,499 | +57 |
| 26 Oct 2026, 08:27 | 96,442 | +78 |
| 25 Oct 2026, 08:06 | 96,364 | +55 |
| 24 Oct 2026, 09:08 | 96,309 | +56 |
| 23 Oct 2026, 05:59 | 96,253 | first reading |
2,464 posts held, back to 7 August 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 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. It is computed over the 566 of 740 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 | 2,464 (7 August 2026 – 17 November 2026) |
| Views total | 123,108 |
| Reactions total | 1,338 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 08:03 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. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
1,810 reactions across 776 posts, in 11 distinct kinds. The most used accounts for 92.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,678 | 92.7% | |
| ❤ | 37 | 2.04% | |
| 🤔 | 31 | 1.71% | |
| 😁 | 12 | 0.663% | |
| 🤩 | 10 | 0.552% | |
| 🥰 | 10 | 0.552% | |
| ⚡ | 9 | 0.497% | |
| 👏 | 9 | 0.497% | |
| 🔥 | 7 | 0.387% | |
| 🎉 | 6 | 0.331% | |
| 👎 | 1 | 0.055% |
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 786 of the 1,000 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 1,810 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 6 October 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: 0 of 740 posts 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).
不定时清理僵尸粉,请加入频道主创建的资源群,以防止被误踢 请加入 https://t.me/+COrvbGVdkVZhZGI1 感谢大家的支持,小弟在这谢谢大家了
👍2
《马年新春活动吊旗挂画PS模版2026元旦商超促销插画吊旗设计素材25款》 25款马年主题PS模板,融合传统生肖元素与现代商超促销需求,涵盖元旦新年氛围,助力商家高效打造新春吊旗挂画,提升节日促销视觉吸引力,适配各类商超场景,轻松输出专业设计素材。 [#PS模板 #马年新春促销 #商超吊旗设计 #元旦活动素材 #2026新年插画] 👇 评论区获取资源
👍4
《全宋笔记全十编_102册》 收录宋代笔记102册,涵盖政治、文化、社会等多领域,一手史料价值极高,展现宋代社会百态与文人智慧,是研究宋代历史与文学的珍贵文献库,内容丰富翔实,堪称宋学研究的必备参考。 [#宋代笔记 #全宋笔记 #史料文献] 👇 评论区获取资源
👍2
《抖音封面、快手封面PSD素材》 精选抖音快手热门封面PSD模板,一键替换文字图片,适配竖屏与横屏,自带潮流滤镜与特效,助力视频快速吸引眼球,提升点击率,新手也能秒出专业封面。 [#抖音封面 #快手封面 #PSD素材 #视频封面设计 #短视频运营] 👇 评论区获取资源
👍2
《十五五规划浅谈阅读推荐》 深度解析《十五五规划》核心要义,聚焦政策新动向与发展机遇,结合实例解读产业趋势与民生关切,助你把握时代脉搏,明晰未来方向,为个人与国家发展同频共振提供智慧指引。 [#十五五规划 #政策解读 #发展机遇] 👇 评论区获取资源
👍1
《破顽空:西游知识学[全二册]》 以全新视角解读《西游记》的深层智慧,融合历史、哲学与民俗文化,揭示经典背后的知识密码。既有学术严谨性,又不失通俗趣味,带你跳出传统解读框架,探索神话世界的多维内涵。 [#西游记文化解读 #经典新说 #知识科普] 👇 评论区获取资源
👍1
《金庸小说合集》 金庸小说合集收录经典武侠巨著,侠义情怀与江湖恩怨交织,人物鲜活,情节跌宕,展现中华文化深厚底蕴,是武侠迷不可错过的文学盛宴,陪伴几代人成长。 [#武侠经典 #金庸小说合集 #文学佳作] 👇 评论区获取资源
👍2
《阿德勒心理学实践手册》 超越弗洛伊德的宿命论与荣格的神秘主义,阿德勒心理学强调“目的论”与“共同体感觉”,赋予个体改变命运的力量。本书以实践为核心,提供具体方法,助你摆脱自卑情结,建立健康人际关系,实现人生自由。 [#阿德勒心理学 #自我成长 #人际关系 #人生课题 #实践指南] 👇 评论区获取资源
《了不起的中成药买得到的精粹老方》 深入挖掘经典老方的精粹,结合现代生活场景,让千年智慧变得触手可及。精选实用方剂,详解配伍奥秘,兼顾功效与便捷,为健康生活提供可靠的中成药解决方案。 [#老方精粹 #中成药智慧 #健康生活指南] 👇 评论区获取资源
👍1
《刚刚驾到(郭德纲)》 郭德纲携德云社班底带来全新力作,以经典相声为基底,融入现代幽默元素,包袱密集笑点不断,展现深厚功底与即兴魅力,每一帧都是笑声的盛宴,让观众在轻松氛围中感受传统与创新的碰撞。 [#郭德纲 #刚刚驾到 #德云社] 👇 评论区获取资源
👍2
《怎样科学的学习》 本书打破传统学习误区,融合认知科学方法,提供高效记忆、深度思考、时间管理的实用策略,帮你建立科学学习体系,让学习事半功倍,轻松掌握知识本质,告别低效努力。 [#高效学习 #怎样科学的学习 #学习方法] 👇 评论区获取资源
👍2
《怎样与领导相处》 职场生存必备指南,教你读懂领导心思,掌握沟通技巧,建立信任关系,轻松应对复杂职场场景,实现职业晋升与个人成长的双赢。 [#职场沟通 #领导力 #职场生存指南] 👇 评论区获取资源
👍1
Showing the 12 most recent of 2,464 posts we hold for @xuendj1. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 1 registered channel — 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.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“学习资料分享” (@xuendj1), 97,383 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/xuendj1.
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.