Telegram RegisterThe public register of Telegram
Telegram profile photo for BigJackson的频道

Channel

BigJackson的频道

@CNBigJackson

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

570subscribers

+222 since we began measuring on 31 August 2026

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

Register entry

Telegram ID-1002523538805
TypeChannel
Username@CNBigJackson
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded31 August 2026
Last confirmed live18 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/CNBigJackson

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 21 September 2026 and assigned it the closest of 31 fixed categories, at 51% 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

34657045831 August 2026 — 348 subscribers31 August 2026 — 346 subscribers9 September 2026 — 456 subscribers18 September 2026 — 570 subscribers31 August 202618 September 2026
4 measurements spanning 18 days, net +222. 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 312–604 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 11:01570+114
9 Sept 2026, 09:55456+110
31 Aug 2026, 14:07346-2
31 Aug 2026, 03:32348first reading

Engagement

18 posts held, back to 24 January 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.

ERR · 30 days
2.46%
avg views ÷ 570 subscribers
Avg views / post
14.0
1 post measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1
of 18 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 August 2026
Posts held18 (24 January 2026 – 30 August 2026)
Views total14
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken31 Aug 2026, 03:32 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.

Reaction mix

2 reactions across 1 post, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤150.0%
👎150.0%

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 1 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 2 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 24 January 2026 to 30 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

30 Aug 2026, 16:25 UTC14 viewsread 31 August 2026

#频道互推 #相似推荐 ------------------------------ 📢 🦙资源整合|线报|羊毛|软件|破解|电影 📢 【你的收藏夹】中文资源频道 📢 中文搜索官方频道 📢 资源情报局 | 学习 · 工具 · AI · 副业 📢 惠州资源榜 📢 资源公社 |CXSNS Resource Hub 📢 太原资源堂 📢 玖玖玖资源部落 📢 全行业资源 📢 搜索引擎/中文搜索/超级索引 ------------------------------ ☁️ 互推入口:@SosoCnBot

17 Aug 2026, 14:43 UTC61 viewsread 31 August 2026
Forwarded from @DNSPODT

GitHub 多项核心服务出现故障,网页与 API 错误率约 20% 8 月 17 日晚,GitHub 发布故障通告,称部分服务出现性能异常。故障于北京时间约 21:40 开始,API Requests、Webhooks、Issues、Pull Requests 与 GitHub Actions 均出现性能下降。 截至北京时间 22:04,GitHub 表示网页端与 API 流量的错误率约为 20%,代码仓库 Archive 下载及 Raw 原始文件下载的错误率则达到约 50%。 GitHub 目前仍在调查故障根因,官方尚未宣布事件恢复。 来源:GitHub Status 官方故障通告

22 Jul 2026, 06:01 UTC129 viewsread 31 August 2026
Photo

太牛逼了,hexo官网有我做的主题了 https://github.com/tud8951/hexo-theme-frutiger-aero

20 Jul 2026, 02:45 UTC134 viewsread 31 August 2026

https://youtu.be/-ITj9WjDaTo?si=0YMG2l3fuLKvOmN6 博客: https://www.bigjackson.top 电报频道: https://t.me/CNBigJackson 项目地址:https://github.com/tud8951/bilibili_follow

31 May 2026, 10:12 UTC217 viewsread 31 August 2026

https://www.youtube.com/watch?v=QUWqIU1kKLk 部署文档https://cfbed.sanyue.de/ 创建 D1 数据库 在 Cloudflare Dashboard 中选择 "存储和数据库" 点击 "D1 SQL 数据库" 点击 "创建数据库" 输入数据库名称:img_d1(建议使用此名称) 点击 "创建" 初始化 D1 数据库 创建完成后,点击进入数据库详情页 选择 "控制台" 选项卡 在 SQL 输入框中粘贴并执行注释区域以下的内容(见项目仓库) 点击 "执行" 绑定 D1 到项目 返回您的 Pages 项目 选择 "设置" → "绑定" 点击 "添加" → "D1 数据库" 填写绑定信息: 变量名称:img_d1(必须是这个名称) D1 数据库:选择刚创建的数据库 点击 "保存" 访问管理后台 访问 你的域名/dashboard

28 May 2026, 13:06 UTC189 viewsread 31 August 2026
Photo

主播自主开发了一个Hexo主题,是frutiger-aero风格的,已申请上架Hexo官网,敬请期待

10 May 2026, 05:39 UTC237 viewsread 31 August 2026

『来自123云盘用户BigJackson的分享』Win11_25H2_Pro_Chinese_Simplified_x64_v2.iso 链接:https://1812480370.share.123865.com/123pan/M6V8Vv-OlvSh

10 May 2026, 05:39 UTC230 viewsread 31 August 2026
File

VMware17激活许可证 JU090-6039P-08409-8J0QH-2YR7F MC60H-DWHD5-H80U9-6V85M-8280D MC60H-DWHD5-H80U9-6V85M-8280D(亲测有效)

9 May 2026, 16:58 UTC214 viewsread 31 August 2026

下期预告: 0基础搭建一个属于自己的Hexo博客

5 May 2026, 11:01 UTC247 viewsread 31 August 2026

youtube.com/watch?v=5u67fxU-0pQ&feature=youtu.be #Blog #博客 #BIgJackson

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

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.

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

“BigJackson的频道” (@CNBigJackson), 570 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/CNBigJackson.

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.