29 Sept 2025, 17:04 UTC≈114,000 views57 reactionsread 12 August 2026
操作地区： A. 安徽 B.北京 C.重庆 F. 福建 G. 广东 / 贵州 / 广西 H. 湖北 / 湖南 / 河北 / 河南 / 黑龙江 J. 江苏 / 江西 / 吉林 L.辽宁 S. 上海 / 四川 / 山西 / 山东 / 陕西 T.天津 X.新疆 Y.云南 Z.浙江 其他地区
❤55😁2
Channel
@kashang 卡商分类频道
@kashang
On this record: Previous handles · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
43,379subscribers
-146 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1002010437352 |
|---|---|
| Type | Channel |
| Username | @kashang222 |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/kashang |
Previous handles
@kashang was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
@kashang
held 7 August 2026 – 7 August 2026
held 7 August 2026 – 7 August 2026
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 20:38 | 43,379 | -8 |
| 11 Aug 2026, 19:04 | 43,387 | +24 |
| 11 Aug 2026, 09:46 | 43,363 | -96 |
| 10 Aug 2026, 16:22 | 43,459 | +14 |
| 10 Aug 2026, 08:12 | 43,445 | -61 |
| 9 Aug 2026, 16:01 | 43,506 | -8 |
| 9 Aug 2026, 09:11 | 43,514 | -26 |
| 8 Aug 2026, 15:06 | 43,540 | +21 |
| 8 Aug 2026, 07:04 | 43,519 | -6 |
| 7 Aug 2026, 10:32 | 43,525 | first reading |
Engagement
20 posts held, back to 15 May 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 pagesof 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 29 September 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
291 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 93.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 272 | 93.5% | |
| 🥰 | 7 | 2.41% | |
| 👍 | 6 | 2.06% | |
| 👏 | 2 | 0.687% | |
| 😁 | 2 | 0.687% | |
| 😭 | 2 | 0.687% |
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 20 of the 20 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 291reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 15 May 2025 to 29 September 2025, 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
29 Sept 2025, 17:02 UTC≈112,000 views30 reactionsread 12 August 2026
操作模式： ①.卡卡/POS/信用卡/NFC ②.盾卡/公户 ③.取现/无卡 ④.综合卡商 ⑤.邮寄卡商 👉卡商交易规则及模版👈 频道编辑建议请联系：@hhhh
❤26🥰4
29 Sept 2025, 17:02 UTC≈102,000 views42 reactionsread 12 August 2026
其他地区： （注意：不在此导航里面的群都是假公群，必须在公群内报备交易，我们只担保公群内的交易，不担保群老板个人信誉，私聊或其他地方交易后果自负，不是在公群内交易发生的纠纷一律不受理，报备时涉及个人隐私的可以部分以星号**代替，并私聊发完整的报备信息给担保确认。）交易前必须找公群老板或业务员双方确认报备信息后 得到相对应的担保号（ @gggg @hhhh @ffff @iiii @kkkk @nnnn @tttt ）确认才能进行交易，没有报备私下作业，出现纠纷概不处理！ 操作模式： ①.卡卡/POS/信用卡/NFC ②.盾卡/公户 ③.取现/无卡 ④.综合卡商 ⑤.邮寄卡商 G： 707 供押17388U熊猫集团卡商小公群 G： 6868 供押15000U聚财集团卡商小公群 G ： 3777 供押15000U运驰仁头卡商小公群 H： 2777 供押15000U瑞盈仁头微信卡商小公群 F： 101 供押15000U…
❤41👍1
29 Sept 2025, 17:02 UTC≈53,900 views24 reactionsread 12 August 2026
其他地区： （注意：不在此导航里面的群都是假公群，必须在公群内报备交易，我们只担保公群内的交易，不担保群老板个人信誉，私聊或其他地方交易后果自负，不是在公群内交易发生的纠纷一律不受理，报备时涉及个人隐私的可以部分以星号**代替，并私聊发完整的报备信息给担保确认。）交易前必须找公群老板或业务员双方确认报备信息后 得到相对应的担保号（ @gggg @hhhh @ffff @iiii @kkkk @nnnn @tttt ）确认才能进行交易，没有报备私下作业，出现纠纷概不处理！ 操作模式： ①.卡卡/POS/信用卡/NFC ②.盾卡/公户 ③.取现/无卡 ④.综合卡商 ⑤.邮寄卡商 i: 777 供押15000U——Audi卡商小公群 暂停作业 G ： 2234 供押5760U汇三支付卡商小公群 i: 1511 供押15000U向晚集团仁头卡商小公群 i: 2025 供押15000U小米支付卡商小公群 H： 1080 供押15…
❤22😭2
29 Sept 2025, 17:01 UTC≈31,600 views7 reactionsread 12 August 2026
其他地区： （注意：不在此导航里面的群都是假公群，必须在公群内报备交易，我们只担保公群内的交易，不担保群老板个人信誉，私聊或其他地方交易后果自负，不是在公群内交易发生的纠纷一律不受理，报备时涉及个人隐私的可以部分以星号**代替，并私聊发完整的报备信息给担保确认。）交易前必须找公群老板或业务员双方确认报备信息后 得到相对应的担保号（ @gggg @hhhh @ffff @iiii @kkkk @nnnn @tttt ）确认才能进行交易，没有报备私下作业，出现纠纷概不处理！ 操作模式： ①.卡卡/POS/信用卡/NFC ②.盾卡/公户 ③.取现/无卡 ④.综合卡商 ⑤.邮寄卡商 i: 111 供押15250U云上支付仁头小公群 i： 1317 供押15888U老总风骚仁头卡商小公群 K： 2913 供押15132U荣森支付卡商小公群 K： 9995 供押15088U北约支付仁头卡商小公群 ⚡ 第5页
❤7
29 Sept 2025, 17:01 UTC≈22,900 views7 reactionsread 12 August 2026
其他地区： （注意：不在此导航里面的群都是假公群，必须在公群内报备交易，我们只担保公群内的交易，不担保群老板个人信誉，私聊或其他地方交易后果自负，不是在公群内交易发生的纠纷一律不受理，报备时涉及个人隐私的可以部分以星号**代替，并私聊发完整的报备信息给担保确认。）交易前必须找公群老板或业务员双方确认报备信息后 得到相对应的担保号（ @gggg @hhhh @ffff @iiii @kkkk @nnnn @tttt ）确认才能进行交易，没有报备私下作业，出现纠纷概不处理！ 操作模式： ①.卡卡/POS/信用卡/NFC ②.盾卡/公户 ③.取现/无卡 ④.综合卡商 ⑤.邮寄卡商 K： 570 供押28888U星辰支付人头卡商小公群 i： 2028 供押18888U恒信支付卡商小公群 i： 1110 供押18888U鸿海仁头卡商小公群 F： 1100 供押17588U中元支付收支付宝牛户仁头/公户小公群 第4页
❤7
29 Sept 2025, 17:01 UTC≈18,100 views7 reactionsread 12 August 2026
其他地区： （注意：不在此导航里面的群都是假公群，必须在公群内报备交易，我们只担保公群内的交易，不担保群老板个人信誉，私聊或其他地方交易后果自负，不是在公群内交易发生的纠纷一律不受理，报备时涉及个人隐私的可以部分以星号**代替，并私聊发完整的报备信息给担保确认。）交易前必须找公群老板或业务员双方确认报备信息后 得到相对应的担保号（ @gggg @hhhh @ffff @iiii @kkkk @nnnn @tttt ）确认才能进行交易，没有报备私下作业，出现纠纷概不处理！ 操作模式： ①.卡卡/POS/信用卡/NFC ②.盾卡/公户 ③.取现/无卡 ④.综合卡商 ⑤.邮寄卡商 暂停作业G： 88088 供押500U运驰ren头卡商公群 i： 1158 供押25888U正心天下集团卡商小公群 ⚡ i： 1072 供押20000U地球集团-收pos机pos卡-卡商公群 H： 1180 供押15588U富桥支付卡商小公群 H：…
❤7
29 Sept 2025, 17:01 UTC≈18,000 views4 reactionsread 12 August 2026
其他地区： （注意：不在此导航里面的群都是假公群，必须在公群内报备交易，我们只担保公群内的交易，不担保群老板个人信誉，私聊或其他地方交易后果自负，不是在公群内交易发生的纠纷一律不受理，报备时涉及个人隐私的可以部分以星号**代替，并私聊发完整的报备信息给担保确认。）交易前必须找公群老板或业务员双方确认报备信息后 得到相对应的担保号（ @gggg @hhhh @ffff @iiii @kkkk @nnnn @tttt ）确认才能进行交易，没有报备私下作业，出现纠纷概不处理！ 操作模式： ①.卡卡/POS/信用卡/NFC ②.盾卡/公户 ③.取现/无卡 ④.综合卡商 ⑤.邮寄卡商 K： 1314 供押66666U聚福星高价收卡商公群 H： 26868 供押20000U小小迷人头卡商小公群 i: 6666 供押49000u合盛集团人头卡商公群 G： 222 供押30888U聚鼎卡商公群⚡ H： 1099 供押21888U金糯米…
❤4
29 Sept 2025, 17:01 UTC≈16,600 views11 reactionsread 12 August 2026
其他地区： （注意：不在此导航里面的群都是假公群，必须在公群内报备交易，我们只担保公群内的交易，不担保群老板个人信誉，私聊或其他地方交易后果自负，不是在公群内交易发生的纠纷一律不受理，报备时涉及个人隐私的可以部分以星号**代替，并私聊发完整的报备信息给担保确认。）交易前必须找公群老板或业务员双方确认报备信息后 得到相对应的担保号（ @gggg @hhhh @ffff @iiii @kkkk @nnnn @tttt ）确认才能进行交易，没有报备私下作业，出现纠纷概不处理！ 操作模式： ①.卡卡/POS/信用卡/NFC ②.盾卡/公户 ③.取现/无卡 ④.综合卡商 ⑤.邮寄卡商 i：7778 供押249600U微信支付宝牛户诚拓集团Ren头卡商公群 N： 55555 供押20万U小满ren头卡商公群 F： 5555 供押10万U奔驰集团(公户/私户)卡商直收公群 G： 810 供押60000U桃喜公户卡商公群 G： 288…
❤11
29 Sept 2025, 17:00 UTC≈15,100 views12 reactionsread 12 August 2026
操作地：重庆 （注意：不在此导航里面的群都是假公群，必须在公群内报备交易，我们只担保公群内的交易，不担保群老板个人信誉，私聊或其他地方交易后果自负，不是在公群内交易发生的纠纷一律不受理，报备时涉及个人隐私的可以部分以星号**代替，并私聊发完整的报备信息给担保确认。）交易前必须找公群老板或业务员双方确认报备信息后 得到相对应的担保号（ @gggg @hhhh @ffff @iiii @kkkk @nnnn @tttt ）确认才能进行交易，没有报备私下作业，出现纠纷概不处理！ 操作模式： ①.卡卡/POS/信用卡/NFC ②.盾卡/公户 ③.取现/无卡 ④.综合卡商 ⑤.邮寄卡商 F： 1288 供押65001U福盈集团人头卡商公群 i： 1177 供押17388U霸星专业收卡商工作室小公群 i: 3302 供押20016U泡芙邮寄卡商小公群 i： 1122 供押15000U天盛支付信用卡直收卡商小公群 G： 128 供…
❤11👏1
29 Sept 2025, 17:00 UTC≈20,900 views1 reactionsread 12 August 2026
操作地：浙江 （注意：不在此导航里面的群都是假公群，必须在公群内报备交易，我们只担保公群内的交易，不担保群老板个人信誉，私聊或其他地方交易后果自负，不是在公群内交易发生的纠纷一律不受理，报备时涉及个人隐私的可以部分以星号**代替，并私聊发完整的报备信息给担保确认。）交易前必须找公群老板或业务员双方确认报备信息后 得到相对应的担保号（ @gggg @hhhh @ffff @iiii @kkkk @nnnn @tttt ）确认才能进行交易，没有报备私下作业，出现纠纷概不处理！ 操作模式： ①.卡卡/POS/信用卡/NFC ②.盾卡/公户 ③.取现/无卡 ④.综合卡商 ⑤.邮寄卡商 第1页
❤1
29 Sept 2025, 17:00 UTC≈17,700 views3 reactionsread 12 August 2026
操作地：天津 （注意：不在此导航里面的群都是假公群，必须在公群内报备交易，我们只担保公群内的交易，不担保群老板个人信誉，私聊或其他地方交易后果自负，不是在公群内交易发生的纠纷一律不受理，报备时涉及个人隐私的可以部分以星号**代替，并私聊发完整的报备信息给担保确认。）交易前必须找公群老板或业务员双方确认报备信息后 得到相对应的担保号（ @gggg @hhhh @ffff @iiii @kkkk @nnnn @tttt ）确认才能进行交易，没有报备私下作业，出现纠纷概不处理！ 操作模式： ①.卡卡/POS/信用卡/NFC ②.盾卡/公户 ③.取现/无卡 ④.综合卡商 ⑤.邮寄卡商 H： 1345 供押15000U卡总人tou卡商小公群 ⚡ 第1页
❤3
Showing the 12 most recent of 20 posts we hold for @kashang. 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.
Posts edited after publishing
@kashang edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 9 August 2026
- Most recent edit
- 11 August 2026
Citation-graph rank
Citation-graph rank — 1,092,213 of 1,160,990entries 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“@kashang 卡商分类频道” (@kashang), 43,379 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/kashang.
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.