Telegram RegisterThe public register of Telegram
Telegram profile photo for trumpyun•频道

Channel

trumpyun•频道

@trumpyun_2025

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

984subscribers

+13 since we began measuring on 27 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003144886796
TypeChannel
Username@trumpyun_2025
CreatedBetween 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 August 2026
Last confirmed live26 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/trumpyun_2025

Topic

Other / unclassifiable — 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 69% 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

971988979.527 August 2026 — 971 subscribers28 August 2026 — 973 subscribers4 September 2026 — 975 subscribers12 September 2026 — 988 subscribers26 September 2026 — 984 subscribers98427 August 202626 September 2026
5 measurements spanning 29 days, net +13. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 968–991 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Sept 2026, 02:00984-4
12 Sept 2026, 14:39988+13
4 Sept 2026, 12:58975+2
28 Aug 2026, 17:52973+2
27 Aug 2026, 23:30971first reading

Engagement

20 posts held, back to 16 April 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 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 20 posts for this entry, the most recent from 21 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

62 reactions across 12 posts, in 10 distinct kinds. The most used accounts for 40.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💩2540.3%
🤮1219.4%
❤69.68%
🥰69.68%
👍46.45%
👏34.84%
👎23.23%
😁23.23%
🤡11.61%
🤯11.61%

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 12 of the 20 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 62 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 16 April 2026 to 21 August 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.

Recent posts

21 Aug 2026, 07:05 UTCviews —

trumpyun•频道 pinned «客服tg:@trumpyun 联系不上的话 双向机器人:@trumpyun001_bot»

21 Aug 2026, 07:05 UTCviews —

trumpyun•频道 pinned «⭐️交流群 @trumpyun2025 ⭐️防走失指南:https://main.subyunnode.com ⭐️永久官网(已被墙):https://trumpyun.com»

21 Aug 2026, 07:05 UTC189 viewsread 27 August 2026

⭐️交流群 @trumpyun2025 ⭐️防走失指南:https://main.subyunnode.com ⭐️永久官网(已被墙):https://trumpyun.com

7 Aug 2026, 13:27 UTC670 views10 reactionsread 27 August 2026

标准中转上游出问题,等找到新资源会立马恢复。

💩5👍3❤2

7 Jul 2026, 15:40 UTC≈1,340 viewsread 27 August 2026

部分节点落地服务提供商需要对近期 Linux KVM 虚拟化平台披露了一个高危安全漏洞(CVE-2026-53359,代号 "Januscape")进行处理,部分节点可能会出现短暂的中断

6 Jul 2026, 20:44 UTC≈1,310 views2 reactionsread 27 August 2026

1.8倍率的线路目前调整到2.0

💩2

29 Jun 2026, 06:09 UTC≈1,230 viewsread 27 August 2026

7月打算进行线路以及倍率进行优化调整,并会考虑增加一些不同的线路,有什么需求可以说一下,会进行考虑采纳。

8 Jun 2026, 10:51 UTC≈1,690 views5 reactionsread 27 August 2026

我已投降,我打算换vless了

👏3👎2

7 Jun 2026, 14:50 UTC≈1,700 viewsread 27 August 2026
File

⏱️测试耗时= 26s ⏱️总体耗时= 52s #uid_8382342955 #timestamp_1780843764

7 Jun 2026, 14:39 UTC≈1,540 viewsread 27 August 2026
File

⏱️测试耗时= 73s ⏱️总体耗时= 116s #uid_8382342955 #timestamp_1780842937

9 May 2026, 16:13 UTC≈1,970 views16 reactionsread 27 August 2026
Photo

广告图好看🥰

🥰6💩5❤2😁2🤮1

Showing the 12 most recent of 20 posts we hold for @trumpyun_2025. 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.

Forward network

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.

Mentions

Named by 2 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.

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 26 September 2026 — this entry's latest reading, not the date you are reading this.

“trumpyun•频道” (@trumpyun_2025), 984 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/trumpyun_2025.

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.