Channel
@jcpdclash
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
895subscribers
+30 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002771597267 |
|---|---|
| Type | Channel |
| Username | @jcpdclash |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/jcpdclash |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 17:35 | 895 | +29 |
| 7 Aug 2026, 09:47 | 866 | +1 |
| 6 Aug 2026, 19:51 | 865 | first reading |
10 posts held, back to 8 July 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 26 July 2026 |
|---|---|
| Posts held | 10 (8 July 2026 – 26 July 2026) |
| Views total | — |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 19:51 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.
7 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 100.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 3 of the 10 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 10 most recent posts we hold, published 8 July 2026 to 26 July 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.
使用教程 pinned «📚 客户端使用教程导航 永久官网发布页地址 tg 自助机器人：@ysjcsmbot（跟官网数据同步，建议优先使用） 如果没有节点请更新软件版本 ⚠️ 使用前请确保： ✅ 客户端已更新至最新版 ✅ 重新更新订阅 ✅ 使用最新节点配置 Clash Mi 如果有更新订阅失败的问题请重新导入订阅链接！！！ 🌐 连接失败 / 节点无法使用？（优先查看） 部分网络环境可能需要开启 IPv6： 👉 点击查看教程： 🌐 IPv6 开启教程 ios导入后没有节点解决方案 🍎 iOS 苹果设备（小火箭 Shadowrocket）…»
📚 客户端使用教程导航 永久官网发布页地址 tg 自助机器人：@ysjcsmbot（跟官网数据同步，建议优先使用） 如果没有节点请更新软件版本 ⚠️ 使用前请确保： ✅ 客户端已更新至最新版 ✅ 重新更新订阅 ✅ 使用最新节点配置 Clash Mi 如果有更新订阅失败的问题请重新导入订阅链接！！！ 🌐 连接失败 / 节点无法使用？（优先查看） 部分网络环境可能需要开启 IPv6： 👉 点击查看教程： 🌐 IPv6 开启教程 ios导入后没有节点解决方案 🍎 iOS 苹果设备（小火箭 Shadowrocket） 提供外部免费共享 ID，本站不提供任何售后和保障。切记只能登录 App Store，勿登录设置中的 Apple ID 以免锁机。 👉 点击查看教程： iOS 小火箭使用教程 ios小火箭开启ipv6教程 ios小火箭超时解决方案 ios导入后没有节点解决方案 Clash Mi使用教程 Clash…
❤4
ios小火箭导入没有节点教程 主页右上角 + 点一下，小火箭没有出现这个，那就是没有更新到最新版本，如果是用免费共享id下载的都需要先卸载然后在下载一遍。 提供外部免费共享 ID，本站不提供任何售后和保障。切记只能登录 App Store，勿登录设置中的 Apple ID 以免锁机。 外部小火箭id免费分享 地址1：https://vip.44s4.top/pages/appleid 选择 免费下载Shadowrocket小火箭 ，不是地区。
使用教程 pinned Deleted message
Clash Meta for Android开启ipv6图文教程 先关闭代理
Clash Meta for Android 安卓代理软件
Clash Meta for Android教程 安装 Clash Meta for Android 后打开软件。 首次打开时，请允许相关权限。 ━━━━━━━━━━━━━━ ② 导入订阅 打开 Clash Meta for Android 进入 配置（Profiles） 点击右上角 + 选择 从 URL 导入 粘贴你的订阅链接 点击 下载 等待配置文件加载完成。 ━━━━━━━━━━━━━━ ③ 启用配置 在配置列表中选择刚刚导入的订阅 点击启用 返回首页 ━━━━━━━━━━━━━━ ④ 开启代理 点击 代理（Proxies） 根据需求选择节点 返回首页 打开 系统代理 / VPN 模式 显示连接成功后即可使用。 ━━━━━━━━━━━━━━ ⑤ 日常使用 如遇节点无法连接： 更新订阅 切换其他节点测试 重启 Clash Meta 删除旧配置后重新导入订阅 ━━━━━━━━━━━━━━
❤1
#windows电脑端使用教程 #Windows #V2rayN * 注意：系统要求 Win10及以上 电脑开启ipv6 https://blog.csdn.net/m0_50939789/article/details/127559783 解压文件后右键 v2rayN.exe 启动程序并使用管理员身份运行。 首次使用可能要通过底部任务栏（右下角）的进程位置找到 V2rayN 的图标（可能在小三角里） 双击该图标后会出现一个界面菜单 需要配置的地方如下： 订阅分组 -> 订阅分组设置 -> 添加 别名 -> 随便写 可选地址 -> 你的订阅链接 启用更新 -> 使用 保存后在配置文件找到你刚刚添加的订阅配置 再次点击 订阅分组 更新全部订阅（不通过代理） 更新好后右键任意一个节点栏 全选 -> 测试配置文件真链接（多选） 然后右键设置有效的节点为活动配置 不建议测速（不准确且会真实的消耗流量） 配置界面最下…
❤2
clash mi 导入使用教程
clash mi选择全局不可用解决方案 首先打开代理然后选择全局 根据图片配置即可 PS:不要选择直连，直连的意思是不通过代理直接连接网络的意思！！！ 规则：使用节点时你访问国内网站是不通过代理，不会检测到你的外国ip 全局：使用节点时全部都用节点网络访问，会检测到你的外国ip 直连：直接连接国内网络不通过代理，不要选就对了！！
Showing the 10 most recent of 10 posts we hold for @jcpdclash. 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 — 45,706 of 1,189,255entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“使用教程” (@jcpdclash), 895 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/jcpdclash.
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.