Posted without readable text

Channel
NewYun NEWS
@newyunnews
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
854subscribers
-19 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001633623229 |
|---|---|
| Type | Channel |
| Username | @newyunnews |
| 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 | 13 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/newyunnews |
Topic
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 60% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 19:39 | 854 | -2 |
| 6 Sept 2026, 06:18 | 856 | -5 |
| 28 Aug 2026, 01:17 | 861 | -3 |
| 21 Aug 2026, 22:15 | 864 | -4 |
| 14 Aug 2026, 12:55 | 868 | -5 |
| 7 Aug 2026, 18:27 | 873 | no change |
| 7 Aug 2026, 06:02 | 873 | first reading |
Engagement
18 posts held, back to 30 January 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 6 June 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
264 reactions across 17 posts, in 9 distinct kinds. The most used accounts for 31.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 4918131754608362797 | 84 | 31.8% | |
| custom 4917937265604297655 | 65 | 24.6% | |
| 👎 | 43 | 16.3% | |
| custom 6264594711890103684 | 29 | 11.0% | |
| 💩 | 23 | 8.71% | |
| custom 4918346528742966070 | 8 | 3.03% | |
| custom 4965701012787561143 | 6 | 2.27% | |
| 👍 | 4 | 1.52% | |
| 🤔 | 2 | 0.758% |
Custom emoji. 5 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 17 of the 18 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 264 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 30 January 2024 to 6 June 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
感谢大佬给的单线程测速(v6是测试节点测试不到,不是坏了哦)
👎41custom 49183465287429660707👍4🤔2
流媒体解锁测试
💩23custom 49657010127875611433
除夕安徽,南京测速参考,祝大年龙年大吉
custom 49179372656042976554custom 49657010127875611433
支付接口费率下降为6.5%,节假日5%
custom 49179372656042976556custom 49181317546083627976
所有套餐开放专线,祝大家新年快乐,新的一年平步青云!
custom 491793726560429765511custom 49181317546083627974
香港节点抽检
custom 49181317546083627978custom 49179372656042976554
本频道将于今日13:00和21:00分别放出6折和5折优惠码。届时将发送四选一的选择题,正确选项即为优惠码。注意:善用搜索引擎,手动输入优惠码。再次祝您在新的一年里身体健康,事事顺利,心想事成!
custom 491793726560429765518custom 49181317546083627977
尊敬的各位亲爱的朋友们, 在这辞旧迎新之际,我谨代表新云团队,向大家致以最诚挚的新年祝福! 2023年已经成为过去,而2024年将为我们开启崭新的篇章。回首过去一年,我们经历了无数挑战,但也收获了许多宝贵的经验和教训。在新的一年里,让我们携手共进,勇往直前,迎接更多挑战,创造更多机遇,共同书写更加辉煌的未来! 在这特别的时刻,我想对我们的团队成员表示最诚挚的感谢。是你们的辛勤付出和奉献精神,才有了我们取得的每一份成绩。愿我们在新的一年里继续团结合作,共同努力,实现更大的成功! 同时,我也想借此机会,向我们的合作伙伴和客户致以诚挚的谢意。感谢你们一直以来的信任与支持,愿我们在新的一年里继续携手合作,共同成长、共创辉煌! 最后,我要向每一位亲爱的朋友送上最美好的祝愿。愿新的一年里,你们身体健康、事业顺利、家庭幸福、万事如意! 让我们共同期许,2024年将是充满希望和美好的一年! 此,从今日起开始新年优惠活动,规则如下:…
custom 491793726560429765515custom 49181317546083627976
Signed 好润姐
新云IPV6使用教程 https://newyunsblog.pages.dev/
custom 49181317546083627976
Signed 好润姐
订阅请使用香港代理更新或者不使用代理更新
👎1
Signed 好润姐
请各位用户保护好自己的订阅地址,请勿泄露节点IP
👎1
Signed 好润姐
Showing the 12 most recent of 18 posts we hold for @newyunnews. 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.
Mentions
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.
Cite this entry
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“NewYun NEWS” (@newyunnews), 854 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/newyunnews.
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.