长期合作 来盘口,中介。 我方代付(微信,支付宝) 单笔1000-10000的 @gsdb_1 ------------ 查看发布者[5719471198] 【累计发布广告25次】 ------------
Signed 【宋校长/自助供需】

Channel
@Sxzxt_4
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
34,347subscribers
+5,124 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002247278212 |
|---|---|
| Type | Channel |
| Username | @Sxzxt_4 |
| Description | 主营:支付系统/群发广告/免费供需 群主: @songxiaozhang 双向: @songxiaozhangBOT 宋校长内部: @SXZXT_0 宋校长主群: @SXZXT_1 国内支付交流群: @SXZXT_2 海外支付交流群: @SXZXT_3 宋校长免费供需: @SXZXT_4 宋校长系统演示: @SXZXT_5 |
| Created | Between 1 May 2024 and 31 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 51 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/Sxzxt_4 |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 41% 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 |
|---|---|---|
| 6 Nov 2026, 00:50 | 34,347 | +84 |
| 5 Nov 2026, 00:28 | 34,263 | +151 |
| 3 Nov 2026, 21:39 | 34,112 | +139 |
| 2 Nov 2026, 21:06 | 33,973 | +108 |
| 1 Nov 2026, 23:50 | 33,865 | +102 |
| 1 Nov 2026, 02:30 | 33,763 | +96 |
| 31 Oct 2026, 00:49 | 33,667 | +11 |
| 30 Oct 2026, 04:11 | 33,656 | +26 |
| 29 Oct 2026, 05:40 | 33,630 | +129 |
| 28 Oct 2026, 01:49 | 33,501 | +57 |
| 27 Oct 2026, 01:57 | 33,444 | +69 |
| 26 Oct 2026, 04:47 | 33,375 | -26 |
| 25 Oct 2026, 04:26 | 33,401 | +117 |
| 24 Oct 2026, 04:25 | 33,284 | +91 |
| 23 Oct 2026, 03:07 | 33,193 | +61 |
| 22 Oct 2026, 00:21 | 33,132 | +96 |
| 20 Oct 2026, 21:07 | 33,036 | +116 |
| 19 Oct 2026, 17:29 | 32,920 | +32 |
| 18 Oct 2026, 18:18 | 32,888 | +59 |
| 17 Oct 2026, 21:18 | 32,829 | first reading |
2,384 posts held, back to 17 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 126 pages of 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. It is computed over the 159 of 1,040 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 November 2026 |
|---|---|
| Posts held | 2,384 (17 August 2026 – 6 November 2026) |
| Views total | 82,838 |
| Reactions total | 162 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 06:53 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.
Lifetime counters from Telegram’s own channel header, read 6 November 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.
Measured directly from 114 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.
160 reactions across 149 posts, in 10 distinct kinds. The most used accounts for 21.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 34 | 21.3% | |
| 🍌 | 24 | 15.0% | |
| 👏 | 23 | 14.4% | |
| 💔 | 20 | 12.5% | |
| 👍 | 15 | 9.38% | |
| 🔥 | 13 | 8.13% | |
| ❤🔥 | 11 | 6.88% | |
| 👌 | 11 | 6.88% | |
| 👎 | 8 | 5.00% | |
| 🍓 | 1 | 0.625% |
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 157 of the 1,000 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 160 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 9 October 2026 to 6 November 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.
Telegram’s own ‘edited’ marker: 0 of 1,040 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
长期合作 来盘口,中介。 我方代付(微信,支付宝) 单笔1000-10000的 @gsdb_1 ------------ 查看发布者[5719471198] 【累计发布广告25次】 ------------
Signed 【宋校长/自助供需】
实力商户诚招代收付通道 支付宝原生 支付宝uid 微信原生 银行卡卡卡 ======== 代付通道 支支 支卡 混合 安全发 备付金 商务对接: @DJ0015
Signed 【宋校长支付系统】保卫科/科长
独家卡密 店铺核销一条龙 圆圆卡(独家卡密)成率80+ 开心卡(独家卡密)成率70+ 女神卡(独家卡密)成率70+ 点金卡(独家卡密)成率70+ 无溢价,可溯源,无限吃量,偷卡一赔十24小时稳定开机,另有 固额10综合原生可带彩 固额50纯原生 联系人:@XTuwhite,@XTulanjing
Signed 【宋校长支付系统】保卫科/科长
👍👍👍👍鸿富Pay ⚡️ 自营一手代收 沃尔玛 益享卡 圆圆卡 红豆卡 淳立卡 金远卡 携程卡 美橙卡 家友卡 铂淼卡 苹果卡 开心卡 星源卡 信汇卡 亿娱卡 顺意卡 利贞卡 锦昌卡 百商卡 元亨卡 墨卷卡 中项卡 美杏卡 千金卡 汇顺卡 鸿丰卡 金润通卡 新元卡 万购卡 百达卡 近胡卡 腾兴卡 点金卡 迅捷卡 女神卡 数字人民币大额 数字人民币小额 QQ转账 自营独家卡 丁丁卡(😍淘宝) 自营独家卡 丁丁卡(😍淘宝) 💵💵另收代付产品 备付金 数字代付 微信代付 支付宝代付 另长期收各种自营一手代收渠道 QQ扫码转账 抖音话费 卡密店铺 前来咨询 量大事少 千手别来 日粮100000000万+✔️✔️✔️ 💵💵💵费率冰点,下发快,成率高,欢迎各大三四方包网对接 ‼️‼️‼️通道全部不日切‼️‼️‼️ 负责人 @VIP_998877 开户对接联系:@HFZF88888888 @HF000004 客服:@xbw58 支
Signed 【宋校长支付系统】保卫科/科长
核销 支付内部群 @cchx 每日置顶找各种料
Signed 【宋校长支付系统】保卫科/科长
独家自营云闪付双端原生 10-100金额 全网最低价 来实力大佬 财富热线:@yiwabao ------------ 查看发布者[8949080700] 【累计发布广告16次】 ------------
Signed 【宋校长/自助供需】
环球国际集团:长期寻:银联快捷,直付通,高成率金条,微信扫码,转账单,个码通道 以上通道均需要100起 直盘量(8-12个月长盘),量大无忧,可保量可包养,可上大压!商务联系:@HQPIPI 欢迎各大资金三方来对接 资金前期 速来对接 活动总量1000+ @LLiming8877 @namei667788
Signed 【宋校长支付系统】保卫科/科长
收通道!收通道!联系人:@HUIXU01
Signed 【宋校长支付系统】保卫科/科长
永恒支付,自营一手原生通道,微信h5,微信扫码,长期收量,限额1-1000,户多稳定24小时输出,有需要请联系🥳🥳🥳 商务联系:@Ww898911 @GTJJTR488
Signed 【宋校长支付系统】保卫科/科长
【来福旺旺支付】老牌话费自营三方 公群保障 — 24h欢迎对接 来福旺旺支付:稳定、高效、客服24h在线服务 专注话费支付,长期招募直盘/大四方商户合作! 来福旺旺支付纯话费,提供稳定、快速的支付通道。 优质通道: 支付宝网厅:70+ 支付宝旗舰:60+ 支付宝联通商城:80+ 支付宝抖音话费:60+ 微信联通商城:45+ 支持的金额:50、100、200 秒下发,无拖欠,下发预付不墨迹! 稳定运行,无日切,全天持续稳定24小时不断码 24h专人客服在线~ 一手通道收粮 费率稳定 价格不乱调 您值得拥有!无纠纷~不吃单,不吃卡,如诺违规随时1:100赔付每单! 诚招三网话单核销,不论大小核销,诚招码队,承兑业务 移动-网厅 联通-商城 电信-网厅 三网-旗舰 欢迎大核销 大话单店铺,银行渠道对接消化快成率保障 诚招三网网厅代下单渠道,一手接码商对接 合作保障: 担保支持 脸熟可预付 话费开户联系: @piao22222 @…
Signed 【宋校长支付系统】保卫科/科长
常规色😍量收api对接原声 收通道 寻一手api对接通道直付通 抖音 麦当劳肯德基原生 网易 YY 游戏各种丝滑产品 微信原生,等一切H5跳转丝滑原生通道,日量500W+ 带维护,小额料子柔 自带产品入金金额,自带产品价格上来询问,不要傻逼一样上来就多少点位 商务合作:@YBj518 ------------ 查看发布者[6836429811] 【累计发布广告53次】 ------------
Signed 【宋校长/自助供需】
宋校长群发广告 1.每个月200U 2.24小时群发, 3.平均每分钟1条广告 3.发送支付群约 90个群 4.实时专人关注,掉号秒补 5.你只需要准备文案 即可! 【没有加入标签所以不会被秒踢】 主理人:【宋校长】 (https://t.me/songxiaozhang)
Signed 【宋校长支付系统】保卫科/科长
Showing the 12 most recent of 2,384 posts we hold for @Sxzxt_4. 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.
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.
@Sxzxt_4 named 2 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.
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.
References a handle that is not a live channel — we have no record it ever was one.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“【宋校长/3U 供需】” (@Sxzxt_4), 34,347 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/Sxzxt_4.
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.