Telegram RegisterThe public register of Telegram
Telegram profile photo for 简绝通知频道

Channel

简绝通知频道

@JIAN424

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,402subscribers

-3 since we began measuring on 15 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002321486486
TypeChannel
Username@JIAN424
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live19 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 19 August 2026
On Telegramt.me/JIAN424

Growth

1,4021,4071,404.515 August 2026 — 1,405 subscribers15 August 2026 — 1,405 subscribers16 August 2026 — 1,407 subscribers19 August 2026 — 1,402 subscribers15 August 202619 August 2026
4 measurements spanning 4 days, net -3. 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 1,401–1,408 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Aug 2026, 12:011,402-5
16 Aug 2026, 16:061,407+2
15 Aug 2026, 09:151,405no change
15 Aug 2026, 09:051,405first reading

Engagement

19 posts held, back to 19 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
22.3%
avg views ÷ 1,402 subscribers
Avg views / post
312
18 posts measured
Reaction rate
0.283%
reactions ÷ views · ER floor
Posts in window
18
of 19 held

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 6 of 18 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 August 2026
Posts held19 (19 July 202610 August 2026)
Views total5,622
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 09:15 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.

What this channel posts

Video runtime
6s
Average length
3s

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.

Reaction mix

7 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 85.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
685.7%
🍌114.3%

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

Measured over the 19 most recent posts we hold, published 19 July 2026 to 10 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

10 Aug 2026, 05:33 UTC131 viewsread 15 August 2026
Forwarded from @jianjue888Photo

🔴 ❗️❗️❗️❗️❗️🔴 ➡️优化雷达。 ➡️优化整体性能。 📊2026年08月10日已云更新

9 Aug 2026, 10:26 UTC145 viewsread 15 August 2026
Forwarded from @jianjue888Photo

🔴 ❗️❗️❗️❗️❗️🔴 ➡️新增小游戏在设置页。 📊2026年08月09日已云更新

9 Aug 2026, 10:26 UTC156 views1 reactionsread 15 August 2026
Forwarded from @jianjuenpPhoto

🔣🔠🔡🔡🔡🔡🔡🔣🎮🏅 📊凯撒云更新内容: ➡️新增投影方式选项。 ➡️新增小游戏在设置页。 🎥云更新,重启凯撒即可更新完毕。 ⏱更新日期:2026年08月09日。

1

4 Aug 2026, 11:29 UTC275 viewsread 15 August 2026
Forwarded from @jianjuenpPhoto

🔣🔠🔡🔡🔡🔡🔡🔣🎮🏅 📊凯撒云更新内容: ➡️尝试修复新版雷达部分用户问题。 ➡️雷达支持迫击炮地图,大地图HUD支持存活队伍显示。 🎥云更新,重启凯撒即可更新完毕。 ⏱更新日期:2026年08月04日。

4 Aug 2026, 11:29 UTC241 viewsread 15 August 2026
Forwarded from @jianjuenpPhoto

🔣🔠🔡🔡🔡🔡🔡🔣🎮🏅 📊凯撒云更新内容: ➡️优化雷达显示。 ➡️增加全局人物显示。 🎥云更新,重启凯撒即可更新完毕。 ⏱更新日期:2026年08月04日。

3 Aug 2026, 10:07 UTC213 views1 reactionsread 15 August 2026
Forwarded from @jianjuenpPhoto

🔣🔠🔡🔡🔡🔡🔡🔣🎮🏅 📊凯撒云更新内容: ➡️优化载具上漏人问题。 ➡️雷达绘图优化。 ➡️自瞄算法2.0 输入模型优化。 🎥云更新,重启凯撒即可更新完毕。 ⏱更新日期:2026年08月03日。

1

28 Jul 2026, 17:01 UTC336 viewsread 15 August 2026
Forwarded from @TopJian

v0.4.27 Update / 更新日志 English New Features - Added position diagnostic file export, sharing, and file management for technical support. Fixes - Improved Decrypt Coordinates compatibility with the latest game update. 中文 新增功能 - 新增位置诊断文件导出、分享和文件管理,便于向技术客服反馈问题。 问题修复 - 优化解密坐标对最新游戏更新的兼容性。

28 Jul 2026, 12:16 UTC325 viewsread 15 August 2026
Video

🔴 ❗️❗️❗️❗️❗️🔴 ➡️更新最新解密,解决闪框问题。 📊2026年07月28日已云更新

28 Jul 2026, 10:17 UTC262 viewsread 15 August 2026
Forwarded from @jianjue888

zey增加样本导出功能,帧率上限提升至165帧,闪框的兄弟导出样本包,点击导出,点击分享,点击mt管理器,mt管理器打开压缩包长按分享给客服!!!

26 Jul 2026, 10:58 UTC356 viewsread 15 August 2026

此频道已添加双向机器人✅ 双向账号可正常私聊售后✅

26 Jul 2026, 10:32 UTC362 viewsread 15 August 2026

402 企发【诚邀您加入】 注册&福利: 流水挑战【拉多少反多少】随赚随提[dO-直清秒到]无视投诉[硬抗拒绝退款]免费保证金+官方认证大V无二次隐形加费虚假套路 安全&服务: 国际企业打款100%匿名数据30天自动销毁去痕迹支持区块链[匿名无痕】 企业特邀商户支持并发不死 卡网官方QQ通知群聊 671287767 官网: www.402faka.com

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

Citation-graph rank

Citation-graph rank — 376,058 of 1,569,089entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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

“简绝通知频道” (@JIAN424), 1,402 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/JIAN424.

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.