Telegram RegisterThe public register of Telegram
Telegram profile photo for 杰克备用频道

Channel

杰克备用频道

@jiekechadang

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

134subscribers

+4 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-1003840184265
TypeChannel
Username@jiekechadang
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/jiekechadang

Growth

1301341327 August 2026 — 130 subscribers9 August 2026 — 130 subscribers16 August 2026 — 134 subscribers7 August 202616 August 2026
3 measurements spanning 8 days, net +4. 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 129–135 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 07:25134+4
9 Aug 2026, 01:16130no change
7 Aug 2026, 19:37130first reading

Engagement

14 posts held, back to 22 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
64.7%
avg views ÷ 134 subscribers
Avg views / post
86.6
14 posts measured
Reaction rate
0.901%
reactions ÷ views · ER floor
Posts in window
14
of 14 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 4 of 14 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 5 August 2026
Posts held14 (22 July 20265 August 2026)
Views total1,213
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 01:16 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

3 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3100.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 4 of the 14 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 3reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

5 Aug 2026, 14:47 UTC52 viewsread 9 August 2026

无盲流水 周四晚12点发车,周六前稳定回 二月 😀⚡️😀😀 四月 😀⚡️😀😀 七月 ⚡️⚡️⚡️⚡️ 一年 ⚡️⚡️😀😀 二年 😀⚡️😀😀 三年 ⚡️⚡️⚡️⚡️ 利息短信费一样收费,有记录就收费,没记录不收 发现私户卡改名成对公卡扣双倍不给单

5 Aug 2026, 12:18 UTC54 viewsread 9 August 2026
Photo

京东快递➕外卖一体 ⚡️⚡️⚡️ 新增:带详细商品 出一年内记录 价格依然不变 认准杰克 @Gzc_888

5 Aug 2026, 11:14 UTC53 viewsread 9 August 2026
Photo

房屋抵押查封状态 😀⚡️⚡️ 提供房屋产权号查询 部分地区需要详细地址 当天隔天回 认准杰克 @Gzc_888

5 Aug 2026, 10:12 UTC52 viewsread 9 August 2026
Photo

新版全户(非刑侦) ⚡️⚡️⚡️ 当天隔天回 不赚钱,主打陪伴 认准杰克 @Gzc_888

5 Aug 2026, 03:26 UTC59 views0 reactionsread 9 August 2026
Photo

强登12123交管 ⚡️⚡️⚡️ 回单 备案驾驶证+名下车辆+车辆状态+违章(有就给) 查空给图一样收费 证件号➕手机号码报单 认准杰克 @Gzc_888

3 Aug 2026, 11:53 UTC83 viewsread 9 August 2026
Photo

邮政地址带单号 ⚡️⚡️⚡️ 综合大数据地址 ⚡️⚡️⚡️ 数据涵盖:历史外卖地址 快递地址 各种app泄露地址 综合地址不是实时玩意 出单不扯皮

3 Aug 2026, 06:47 UTC80 viewsread 9 August 2026
Photo

源头医保社保文档 ⚡️⚡️⚡️ 出的是全部社保 包含历史 目前可以出工作单位唯一渠道 查敏感和在职工作单位以及历史工作单位 医保 社保 什么险种类型都有都出 当天回当天回 稳定 认准杰克 @Gzc_888

3 Aug 2026, 05:51 UTC74 views1 reactionsread 9 August 2026
Photo

全国出生证明 😀⚡️⚡️ 稳定当天隔天回单,一天一车 人在就秒,全国可出, 报单需自带大头 部分地区要有效期 专业事交给专业的人 认准杰克 @Gzc_888

1

1 Aug 2026, 06:54 UTC96 views1 reactionsread 9 August 2026
Photo

源头全网最全地区个户😀 😀 😀 12天津 32 江苏 43 湖南 45 广西 46海南 65新疆 13 河北 ⚡️⚡️ 42 湖北 ⚡️⚡️ 36江西 37山东 52贵州 62甘肃⚡️⚡️ 33浙江 34安徽 44 广东⚡️⚡️ 假地址大头 ⚡️⚡️ 拼接个户 ⚡️⚡️ 主打出单快 效率高 批量可刀 认准杰克 @Gzc_888 春江8100为您保驾护航

1

31 Jul 2026, 04:33 UTC104 views1 reactionsread 9 August 2026

收五十单小档 今晚回 文字回单 车架号,发动机号,车主姓名,车主身份证,电话 车子品牌

1

30 Jul 2026, 10:25 UTC113 viewsread 9 August 2026
Photo

公网车辆违章记录 ⚡️⚡️⚡️ 报单提供车牌号 两天内回单 无遗漏 已测试随便埋雷 认准杰克 @Gzc_888

25 Jul 2026, 01:50 UTC133 viewsread 9 August 2026
Photo

税务局全业务 一项 特价 ⚡️⚡️⚡️ 卷起来 公司发票 一年记录 无遗漏全出 公司财务报表 无遗漏全出 公司股东 无遗漏全出 公司员工 无遗漏 全出 公司对公 遗漏小全出 个人所得税 报单提供法人 大头 公司名称 信用代码 需要什么备注好 认准杰克 @Gzc_888

Showing the 12 most recent of 14 posts we hold for @jiekechadang. 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 — 1,346,869 of 1,548,671entries 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.

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

“杰克备用频道” (@jiekechadang), 134 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/jiekechadang.

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.