Channel
@qimingzf
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,108subscribers
+111 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002590424216 |
|---|---|
| Type | Channel |
| Username | @qimingzf |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 August 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/qimingzf |
Hacking & security — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 66% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Nov 2026, 09:36 | 1,108 | +7 |
| 30 Oct 2026, 15:27 | 1,101 | -1 |
| 28 Oct 2026, 00:16 | 1,102 | +4 |
| 25 Oct 2026, 06:09 | 1,098 | +1 |
| 22 Oct 2026, 06:50 | 1,097 | +2 |
| 19 Oct 2026, 02:26 | 1,095 | +6 |
| 15 Oct 2026, 18:19 | 1,089 | +4 |
| 12 Oct 2026, 14:07 | 1,085 | +3 |
| 6 Oct 2026, 03:39 | 1,082 | +10 |
| 29 Sept 2026, 07:01 | 1,072 | +9 |
| 19 Sept 2026, 16:17 | 1,063 | +9 |
| 15 Sept 2026, 12:36 | 1,054 | -15 |
| 11 Sept 2026, 15:02 | 1,069 | +12 |
| 6 Sept 2026, 22:38 | 1,057 | +13 |
| 2 Sept 2026, 19:16 | 1,044 | +10 |
| 30 Aug 2026, 18:24 | 1,034 | +6 |
| 27 Aug 2026, 22:32 | 1,028 | +11 |
| 25 Aug 2026, 04:09 | 1,017 | +20 |
| 16 Aug 2026, 19:30 | 997 | no change |
| 16 Aug 2026, 19:15 | 997 | first reading |
20 posts held, back to 16 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 16 August 2026. An engagement rate over an empty window would be a number about nothing.
2060 支付宝小额纯原生30-50 费率：1️⃣6️⃣❤️3️⃣ 2051 支付宝固额纯原生固额50 费率：1️⃣6️⃣❤️3️⃣ 2061 支付宝固额纯原生固额30 费率：1️⃣6️⃣❤️3️⃣ 【通道名称】：支付宝原生100-500 【通道编码】：2054 【通道金额】：100-200 【通道成率】：70+ 【通道规则】：‼️只接全层纯BC/QP量‼️#允许BC带彩✅ ⚠️🈲三黑/大头照/资金盘/刷单/刮刮乐/色料/常规料等所有不是bc/棋牌量(不管死不死户)抓到1:10➕另赔5万户费+巡查2000u⚠️ 在此声明 出现混料子按规则走 我这里不给打包价 不同意不要进单子 谢谢 ⚠️⚠️⚠️金额：100-200 ⚠️⚠️⚠️金额：100-200 ✔️费率：1️⃣6️⃣❤️3️⃣ ❌❌❌2045支付宝1-9原生。 ❌❌❌ ❌❌❌2045支付宝1-9原生。 ❌❌❌
2060 支付宝小额纯原生30-50 费率：1️⃣6️⃣❤️8️⃣ 2051 支付宝固额纯原生固额50 费率：1️⃣6️⃣❤️8️⃣ 2061 支付宝固额纯原生固额30 费率：1️⃣6️⃣❤️8️⃣ 【通道名称】：支付宝原生100-500 【通道编码】：2054 【通道金额】：100-200 【通道成率】：70+ 【通道规则】：‼️只接全层纯BC/QP量‼️#允许BC带彩✅ ⚠️🈲三黑/大头照/资金盘/刷单/刮刮乐/色料/常规料等所有不是bc/棋牌量(不管死不死户)抓到1:10➕另赔5万户费+巡查2000u⚠️ 在此声明 出现混料子按规则走 我这里不给打包价 不同意不要进单子 谢谢 ⚠️⚠️⚠️金额：100-200 ⚠️⚠️⚠️金额：100-200 ✔️费率：1️⃣6️⃣❤️8️⃣
【通道名称】：支付宝AA 【通道编码】：2089 【通道金额】：300-400 【通道规则】：【通道规则】：全层抗投诉 只要BC，棋牌量！ 必须是bc 棋牌量 提示：禁止资金盘及三黑资金，发现不回调不下发。查单24小时。一旦发现除bc棋牌以外的量，按照当日全部通道跑量1:10赔付。 🈲止三黑 话费点卷 刮刮乐 游戏盲盒 资金盘 彩票抽奖 游戏买卖杀猪盘等 请勿超时支付、修改金额，重复支付。 【重复支付/修改金额/超时支付，收款账户未风控24小时内尽量帮忙找回，如果无法找回导致损失，不退不补】 【如重复支付/修改金额/超时支付账户风控不退不补 。】 引导语：私聊加好友的都是骗子，线下严禁加好友，被骗单与本公司无关，待支付下发显示客服都是冒牌的，请注意，严禁私下转账 查单24小时‼️ 查单24小时‼️ 查单24小时‼️ 规则🈲刷单 电诈 公检法 精聊一切混料 🈲三黑，发现后扣除余额不下发，停止合作 ‼️】 …
2060 支付宝小额纯原生30-50 费率：1️⃣7️⃣❤️2️⃣ 2051 支付宝固额纯原生固额50 费率：1️⃣7️⃣❤️2️⃣ 2061 支付宝固额纯原生固额30 费率：1️⃣7️⃣❤️2️⃣ 【通道名称】：支付宝原生100-500 【通道编码】：2054 【通道金额】：100-200 【通道成率】：70+ 【通道规则】：‼️只接全层纯BC/QP量‼️#允许BC带彩✅ ⚠️🈲三黑/大头照/资金盘/刷单/刮刮乐/色料/常规料等所有不是bc/棋牌量(不管死不死户)抓到1:10➕另赔5万户费+巡查2000u⚠️ 在此声明 出现混料子按规则走 我这里不给打包价 不同意不要进单子 谢谢 ⚠️⚠️⚠️金额：100-200 ⚠️⚠️⚠️金额：100-200 ✔️费率：1️⃣7️⃣❤️2️⃣
2060 支付宝小额纯原生30-50 费率：1️⃣7️⃣❤️5️⃣ 2051 支付宝固额纯原生固额50 费率：1️⃣7️⃣❤️5️⃣ 2061 支付宝固额纯原生固额30 费率：1️⃣7️⃣❤️5️⃣ 【通道名称】：支付宝原生100-500 【通道编码】：2054 【通道金额】：100-200 【通道成率】：70+ 【通道规则】：‼️只接全层纯BC/QP量‼️#允许BC带彩✅ ⚠️🈲三黑/大头照/资金盘/刷单/刮刮乐/色料/常规料等所有不是bc/棋牌量(不管死不死户)抓到1:10➕另赔5万户费+巡查2000u⚠️ 在此声明 出现混料子按规则走 我这里不给打包价 不同意不要进单子 谢谢 ⚠️⚠️⚠️金额：100-200 ⚠️⚠️⚠️金额：100-200 ✔️费率： 1️⃣7️⃣❤️5️⃣
【通道名称】：贵族微信原生 【通道编码】：2031 【通道金额】：100 【通道成率】：70+ 【通道规则】：全层抗投，禁一切除BC QP之外所有量，只接bc，qp。支付时间3分钟，禁止超时支付，修改金额，重复支付，超时支付不退不补，修改金额重复支付尽量帮追。查单24小时‼️🈲三黑/电闸/资金/混料/大头贴/门票等/‼️ ✔️费率：1️⃣2️⃣❤️8️⃣
2030 支付宝原生10-50 费率：2️⃣0️⃣❤️8️⃣
2060 支付宝小额纯原生30-50 费率：1️⃣7️⃣❤️8️⃣ 2051 支付宝固额纯原生固额50 费率：1️⃣7️⃣❤️8️⃣ 2061 支付宝固额纯原生固额30 费率：1️⃣7️⃣❤️8️⃣ 【通道名称】：支付宝原生100-500 【通道编码】：2054 【通道金额】：100-200 【通道成率】：70+ 【通道规则】：‼️只接全层纯BC/QP量‼️#允许BC带彩✅ ⚠️🈲三黑/大头照/资金盘/刷单/刮刮乐/色料/常规料等所有不是bc/棋牌量(不管死不死户)抓到1:10➕另赔5万户费+巡查2000u⚠️ 在此声明 出现混料子按规则走 我这里不给打包价 不同意不要进单子 谢谢 ⚠️⚠️⚠️金额：100-200 ⚠️⚠️⚠️金额：100-200 ✔️费率： 1️⃣7️⃣❤️8️⃣🔼🔼🔼
2060 支付宝小额纯原生30-50 费率：1️⃣0️⃣ 2051 支付宝固额纯原生固额50 费率：1️⃣0️⃣ 2061 支付宝固额纯原生固额30 费率：1️⃣0️⃣ 【通道名称】：支付宝原生100-500 【通道编码】：2054 【通道金额】：100-200 【通道成率】：70+ 【通道规则】：‼️只接全层纯BC/QP量‼️#允许BC带彩✅ ⚠️🈲三黑/大头照/资金盘/刷单/刮刮乐/色料/常规料等所有不是bc/棋牌量(不管死不死户)抓到1:10➕另赔5万户费+巡查2000u⚠️ 在此声明 出现混料子按规则走 我这里不给打包价 不同意不要进单子 谢谢 ⚠️⚠️⚠️金额：100-200 ⚠️⚠️⚠️金额：100-200 ✔️费率： 1️⃣0️⃣🔽🔽🔽
2060 支付宝小额纯原生30-50 费率：1️⃣1️⃣❤️9️⃣ 2051 支付宝固额纯原生固额50 费率：1️⃣1️⃣❤️9️⃣ 2061 支付宝固额纯原生固额30 费率：1️⃣1️⃣❤️9️⃣ 【通道名称】：支付宝原生100-500 【通道编码】：2054 【通道金额】：100-200 【通道成率】：70+ 【通道规则】：‼️只接全层纯BC/QP量‼️#允许BC带彩✅ ⚠️🈲三黑/大头照/资金盘/刷单/刮刮乐/色料/常规料等所有不是bc/棋牌量(不管死不死户)抓到1:10➕另赔5万户费+巡查2000u⚠️ 在此声明 出现混料子按规则走 我这里不给打包价 不同意不要进单子 谢谢 ⚠️⚠️⚠️金额：100-200 ⚠️⚠️⚠️金额：100-200 ✔️费率： 1️⃣1️⃣❤️9️⃣🔽🔽🔽
2060 支付宝小额纯原生30-50 费率：1️⃣8️⃣ 2051 支付宝固额纯原生固额50 费率：1️⃣8️⃣ 2061 支付宝固额纯原生固额30 费率：1️⃣8️⃣ 【通道名称】：支付宝原生100-500 【通道编码】：2054 【通道金额】：100-200 【通道成率】：70+ 【通道规则】：‼️只接全层纯BC/QP量‼️#允许BC带彩✅ ⚠️🈲三黑/大头照/资金盘/刷单/刮刮乐/色料/常规料等所有不是bc/棋牌量(不管死不死户)抓到1:10➕另赔5万户费+巡查2000u⚠️ 在此声明 出现混料子按规则走 我这里不给打包价 不同意不要进单子 谢谢 ⚠️⚠️⚠️金额：100-200 ⚠️⚠️⚠️金额：100-200 ✔️费率： 1️⃣8️⃣🔽🔽🔽
【通道名称】：贵族微信原生 【通道编码】：2031 【通道金额】：100 【通道成率】：70+ 【通道规则】：全层抗投，禁一切除BC QP之外所有量，只接bc，qp。支付时间3分钟，禁止超时支付，修改金额，重复支付，超时支付不退不补，修改金额重复支付尽量帮追。查单24小时‼️🈲三黑/电闸/资金/混料/大头贴/门票等/‼️ ✔️费率：1️⃣2️⃣❤️8️⃣🔼🔼🔼
Showing the 12 most recent of 20 posts we hold for @qimingzf. 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.
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.
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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“启明支付-通知频道（全年无休）” (@qimingzf), 1,108 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/qimingzf.
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.