📣春江供需资讯‼️♻️ 供应商品:找一手学位编号源头 一手文字学历源头。层层加码的勿扰,长期合作稳定报单 商品介绍: 商品价格: 是否售后: 是否支持担保: 保费哪方承担: 交易货币支持: 对接联系人:@fengzong9527 频道:【选填/没频道可以不填】 该用户累计发布 1 次 👉 点我查看发布人👈

Channel
春江供需
@cjgx2
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
159,146subscribers
-3,286 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
Register entry
| Telegram ID | -1001060056664 |
|---|---|
| Type | Channel |
| Username | @cjgx2 |
| Created | Between 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/cjgx2 |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 12 August 2026 and assigned it the closest of 31 fixed categories, at 37% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 12:01 | 159,146 | -7,575 |
| 5 Sept 2026, 05:37 | 166,721 | +12,286 |
| 3 Sept 2026, 09:24 | 154,435 | -3,268 |
| 2 Sept 2026, 05:28 | 157,703 | -1,245 |
| 1 Sept 2026, 04:35 | 158,948 | -507 |
| 31 Aug 2026, 04:25 | 159,455 | +13,959 |
| 30 Aug 2026, 06:48 | 145,496 | -2,572 |
| 29 Aug 2026, 07:57 | 148,068 | -10,220 |
| 28 Aug 2026, 04:47 | 158,288 | -1,318 |
| 27 Aug 2026, 03:47 | 159,606 | +2,228 |
| 26 Aug 2026, 02:38 | 157,378 | +3,811 |
| 25 Aug 2026, 01:43 | 153,567 | -5,020 |
| 23 Aug 2026, 14:27 | 158,587 | +9,953 |
| 22 Aug 2026, 03:05 | 148,634 | -3,349 |
| 20 Aug 2026, 21:57 | 151,983 | -2,564 |
| 20 Aug 2026, 00:18 | 154,547 | +6,080 |
| 18 Aug 2026, 20:57 | 148,467 | -1,502 |
| 17 Aug 2026, 19:08 | 149,969 | -1,333 |
| 16 Aug 2026, 16:17 | 151,302 | -5,021 |
| 15 Aug 2026, 03:16 | 156,323 | first reading |
Engagement
535 posts held, back to 12 August 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 58 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.366%
- avg views ÷ 159,146 subscribers
- Avg views / post
- 582
- 535 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 535
- of 535 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.
| Window | Rolling 30 days · latest post in window 9 September 2026 |
|---|---|
| Posts held | 535 (12 August 2026 – 9 September 2026) |
| Views total | 311,354 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Sept 2026, 17:18 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
- Photos
- ≈346
- Videos
- ≈54
- Links
- ≈1,560
Lifetime counters from Telegram’s own channel header, read 9 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
- Video runtime
- 50s
- Average length
- 5s
Measured directly from 10 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.
Recent posts
📣春江供需资讯‼️♻️ 京东地址带单号10U 只出单地址 文字版 特价 特价 特价 随时可能涨价 京东商城购物记录最新一条15U带商品信息不带单号 有订单号 一年内所有购物记录30U 有单发过来现在在秒 京东地址带单号10U 只出单地址 文字版 特价 特价 特价 随时可能涨价 京东商城购物记录最新一条15U带商品信息不带单号 有订单号 一年内所有购物记录30U 有单发过来现在在秒 联系 @cidcd1 该用户累计发布 1 次 👉 点我查看发布人👈
🤩🤩🤩🤩🤩🔥📣 点击下方蓝字进入公群👇👇👇 春江8015 失去源头天眼查 已押1600U 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩
📣春江供需资讯‼️♻️ 供应商品: 联机5U人在就秒 文全慢线8U统一晚上回 文全地址1.5U 脱库机主10U 社保明细15U 微信收款码 反名字身份证40U 微信商家码 反名字身份证50U 当天回 有绑必出 欢迎各种源头技术 律所催收条子合作 对接联系人: @Lxibaby 频道:https://t.me/XiCD666 该用户累计发布 2 次 👉 点我查看发布人👈
📣春江供需资讯‼️♻️ 每日固定菜单 文字全12U/补齐猎魔10U/户籍地址2U 量大来谈 诚招代理! 文字全12U/补齐猎魔10U/户籍地址2U 量大来谈 诚招代理! 单头全户13U/全头全户18U 量大来谈 诚招代理! 单头全户13U/全头全户18U 量大来谈 诚招代理! ————————————————— 支机1U 联通5U 假地址2U真地址4U 高爆机主2U 高爆法人1U 名下号1U 车管所名下车15U 车小档12U 婚姻5U 银行卡卡反5U支付宝码反8U —————————————————— 邮政单地址5U多地址8U(带单号) 美团地址35U七合一地址10U —————————————————— 查档业务均可咨询 春江8004已上压 https://t.me/+tXw6o7YlQDxmNWUx 联系 @xsjty 唯一频道 @TH1111888 该用户累计发布 6 次 👉 点我查看发布人👈
📣春江供需资讯‼️♻️ 山东 四川 河南 安徽 江苏 陕西 贵州 甘肃 云南 陕西 海南 内蒙 广西 新疆 湖南 出地区名下全部房产25u 原图司法230u 带经办人指定流水 支付宝邮箱号反手机号15u 支付宝码反10u 名下卡三合一25u 单头全户10u 全头12u 全国房产无遗漏 首套120u 次套60u 老二网定位120u 三网160u 移动专线定位180u 法院版犯罪记录20u 大数据征信报告模板25u 案件号出案件详情30u 快递七合一15u 网警地址15u 支付宝订单号反20u 带头学籍学历10u 强登交管12123 名下车40u 违章40u 批量价优 报单联系 @tangshi https://t.me/+gdDhGmSE60o4Y2Q8 该用户累计发布 23 次 👉 点我查看发布人👈
📣春江供需资讯‼️♻️ 供应商品: 交管12123强登版名下车35U 35U 35U 交管12123强登版名下车35U 35U 35U 交管12123强登版名下车35U 35U 35U 交管12123强登版名下车35U 35U 35U 交管12123强登版名下车35U 35U 35U 交管12123强登版名下车35U 35U 35U 交管12123强登版名下车35U 35U 35U 交管12123强登版名下车35U 35U 35U 提供身份证,大头,手机号 ———————- 真实强登,回单12123app内容 驾驶证+备案名下车辆+备案他人名下车辆+有违章给违章信息以及车辆违章照片 商品介绍: 商品价格: 是否售后: 是否支持担保: 保费哪方承担: 交易货币支持: 对接联系人: @ft1616 频道: https://t.me/ftcw2026 该用户累计发布 2 次 👉 点我查看发布人👈
📣春江供需资讯‼️♻️ 无盲卡反看名字机器人: @yhmz_bot @5u一次(1积分) 可以查看9个银行 批量卡三核验机器人!!! 1天 7u 7天(一周)35u 30天(一个月)100u 可okpay自助充值 无限制条数 不抽风,部分银行可核验异常 目前能核验:光大银行、广发银行、浦发银行、华夏银行、邮政银行、民生银行、农业银行、建设银行、中信银行、工商银行、平安银行(后续慢慢添加) 机器人用户名: @@bankcheck0703bot 小众银行批量卡三核验!!! 1天授权10u(okpay自动充值即可) 机器人用户名: @@pinshuxhk3_bot 对接联系人: @pptovo @zhuiyi6 频道: https://t.me/pinshu56 公群:https://t.me/+MnmAizbXeq9lMjdh 该用户累计发布 2 次 👉 点我查看发布人👈
📣春江供需资讯‼️♻️ 供应商品:公网版常用号源头,公网版安徽全户源头收单 商品介绍:📣📣📣厅 实时常用号带现住地和户籍地 出率90以上 三要素80以上。日出百万➕,价格0.2r一条,性价比之王。盘口等各种项目质量天花板。 📣📣📣厅 实时安徽全家信息,带户籍地,婚姻,双方全户都可以出,日出10➕,价格4r。找人性价比之王。 商品价格:公网常用号0.2r,安徽公网全户4r 是否售后:是 是否支持担保:支持 保费哪方承担: 交易货币支持:usdt 对接联系人:@shaobing666 频道:https://t.me/shaobing963 该用户累计发布 1 次 👉 点我查看发布人👈
📣春江供需资讯‼️♻️ 民政婚姻源头- @linzhentan 两条线路出单 保证不翻车 真民政婚姻 假一赔十 早上八点秒到晚上八点半 期间一直在秒 5U全天秒 批量来拿优势 不限量 不限量 多少单都吃得下 文字婚姻BOT 24小时响应 @wenzihunyinbot 充值完USDT后不显示充值成功 可以直接输入姓名 身份证查询 无需任何指令 BOT简洁 出现问题反馈找 @linzhentan @hjddzjqr_bot 户籍单地址24小时秒响应 充分联系 @linzhentan 全网上押万U 交易有保障 春江双公群质保 频道: https://t.me/WZQHY 春江公群: https://t.me/+aPEyy0cfxHFhMjI5 唯一客服 @linzhentan 该用户累计发布 50 次 👉 点我查看发布人👈
📣春江供需资讯‼️♻️ 文字全户12u 身份证补齐10u 全国文字猎魔 10u 源头文全户籍地2u秒 户籍地机器人:@hjddzjqr_bot 大头假地址1.5 支机2u 破解支百12u 真民政婚姻5u秒 破解v反25u 联系人:@iGshayu 春江8040已上压交易无风险 公群https://t.me/+rWsjW4G4SMI3NGFh 通知频道 https://t.me/az801019 该用户累计发布 3 次 👉 点我查看发布人👈
📣春江供需资讯‼️♻️ ‼️公网名下卡 25U 三合一版本 ‼️公网名下卡 25U 三合一版本 ‼️公网名下卡 25U 三合一版本 ————————————— ‼️机主在线秒 1U ‼️机主在线秒 1U ‼️机主在线秒 1U ‼️机主在线秒 1U ————————————— ‼️ 真支百12U 非破解 ————————————— ‼️正反加工 1U ‼️正反加工 1U ‼️正反加工 1U 法人 1U 卡反 2U 支机 2U 破解支百5U 剩菜卡反15U 是否支持担保: 春江公群 https://t.me/+mIcyqyt28pQ2ODJh 保费哪方承担: 公群8060 是否支持担保: 保费哪方承担: 交易货币支持: 对接联系人: https://t.me/byg0088 频道:https://t.me/baiyueguangyewu 该用户累计发布 37 次 👉 点我查看发布人👈
Showing the 12 most recent of 535 posts we hold for @cjgx2. 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
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
@WZQHY · 43630 posts法老业务通知频道
@falao112 · 1,03711 posts平价全能查档业务通知
@jgcdpd · 31511 posts洛克王国-通知频道
@luokewangguotzpd01 · 13710 posts猫猫机器人新频道
@maomaonewpindao · 7,86010 posts黑豹通知频道
@heibao2222 · 10,1749 posts太乙真人
@chadang00122 · 558 posts木森德州俱乐部观战
@musendezhoujulebu38 · 10,1097 posts通知频道
@shiqichadang · 1736 posts吴中通知频道
@WZTZPDVIP888 · 2086 posts北派最强的鸭子
@beipaigaga · 1175 posts胖东来源头查档批发
@DLCD001 · 12,3865 posts风吹麦浪
@fengchui66 · 635 posts花果山查档中转站
@hgscdfsl · 285 posts杀神殿 源头批发查档频道
@sscd66 · 96,6905 posts杀神模板频道
@sscd68 · 3,3235 posts肖教主 通知@xiongsheng
@xiongsheng · 5,1245 posts奉先通知频道 @doufan
@doufan · 12,0644 posts大帅免费社工库查档开盒开户交流群
@dscd5555 · 22,0794 posts鸿创源头批发
@hchjt04 · 1564 posts最終兵器
@Ttrcoe · 824 posts德州扑克-木森俱乐部
@musendezhou38 · 159,2123 posts风衣源头查档批发市场
@ttyuiomu · 823 posts钟意优势查档频道
@ZYCD002 · 383 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.
Handles this channel named that no longer answer
- Dead references
- 7
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 3
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 4
- vacant every time we have ever looked
@cjgx2 named 7 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 3 posts, 14 August 2026 – 16 August 2026 · confirmed gone 20 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 2 posts, 16 August 2026 – 22 August 2026 · confirmed gone 28 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 14 August 2026 – 14 August 2026 · confirmed gone 16 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 September 2026 – 8 September 2026
named in 1 post, 24 August 2026 – 24 August 2026
named in 1 post, 24 August 2026 – 24 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“春江供需” (@cjgx2), 159,146 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/cjgx2.
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.