Channel
@lixiangkejitongzhi
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,447subscribers
+505 since we began measuring on 18 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001548799059 |
|---|---|
| Type | Channel |
| Username | @lixiangkejitongzhi |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 29 September 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 29 September 2026 |
| On Telegram | t.me/lixiangkejitongzhi |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Sept 2026, 11:14 | 1,447 | +505 |
| 18 Sept 2026, 00:22 | 942 | first reading |
16 posts held, back to 26 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 page 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.
| Window | Rolling 30 days · latest post in window 17 September 2026 |
|---|---|
| Posts held | 16 (26 July 2026 – 17 September 2026) |
| Views total | 985 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Sept 2026, 00:22 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.
#优化体验 9/17 更新内容 后台管理员驳回状态为处理中订单时 可通过 填写关键信息驳回 选择驳回原因 都在一个页面 代付优化 代付 回收 驳回 打款 在一个页面 代付优化 待接单背色为红色 处理中背色为绿色 机器人查银行卡归属地 优化群组加减余额操作。图片和 +1000*6.66 一起的话 也生效 商户 码商代收通道 调整框里 也要显示 通道编码 转账限制 押金不参与转账 管理员可以操作
#优化体验 9/16 23.40 更新内容 须知 1 码商自己在群里绑定TG号不能用 码商在群里自己绑定账号后 然后自动绑定群组 2 码商端个人中心加一个自己可以绑定TG号 3 团队长的下级 给下级改改不了一致的费率 4 新增 收款码 复制到其他通道 5 新增 代付权限 配置 可以配置 新增码商是否开启 默认为开启 6 自动驳回的单子。驳回原因 支付中断 7 机器人查单 查状态 为 待接单时 反馈为 已提交 8 码商端 通道提示 和 转账金额 排序互换 做适配 拉窄时 格式变窄 9 代付可以查询归属地 10 代付 在确认按钮内 可以有复制按钮 11 代付抢单界面 抢到单子后 可以直接跳出打款页面 并上传凭证 12 商户代收通道 支付通道那里显示通道编码 码商代收通道 支付通道也显示通道编码 13 代付打开订单后。通道提示 显示 代付提示的内容
#优化体验 9/10 23.40 更新内容 须知 各位老板把控好时间 1 新增收款码 导出按钮 可根据需要导出 权限 营运端 码商端 2 批量上传解析收款地址时 预览时 地址后面加一个 查看二维码 3 新增 bc原生代收 标签
#新增功能 系统新增星级通道！星级级别根据并发量判定！ 大哥们可以根据星级选择挂码～星星越多 进单越猛！
#新增功能 上码时可自行选择码是否开启状态！不需要上传后在去关闭或者开启
#新增功能 1 机器人新增查询跑量的功能 输入命令后下方可选择查询的日期 分天统计展示 2 机器人新增查询账单的功能 输入命令后下方可选择查询的日期 分天统计展示 3 新增QQ群贴代付识别功能 客户按照格式发送 机器人可自动识别提交后台（需管理员确认） 4 供应商新增可单独选择某一家商户去做定位拉测试单 5 商户费率可设置为负费率 6 优化了代收进单限制逻辑 7 代付订单自动驳回逻辑优化 8 代付群贴提交时间优化
QQ转账高成率 自动回调👍👍👍
欢迎各界朋友带成功率高的通道来找我 ，拉测试单可换钱。能带金额和备注的最好
#新增功能 1. 收银台优化。需要填名字的 不填名字 不展示二维码。 2. 增加 排序浮动 ： 通道 为顺序浮动，设定0.1时 则0.99-0.90顺序浮动 3. 新增绑定码商或解绑码商 ： 增加后在平台配置 可为不同码商和商户进行精细化绑定 #优化体验 1. 批量修改商户费率 。如果出现重复 编码 则不生效此次修改费率。 并播报失败 失败原因 2. 代付 处理中状态 可以分配给 其他码商 有效使卡代付的码商无法判定是否打款进行精准分配
跟大家说明一下，咱们产品的防拉空技术和市面上的不同，外面的群发通知大家不用管。如果后续有客户单独反馈防拉空异常，随时联系我来跟进处理。另外，针对今天部分客户提到“商户要求关闭防拉空”的情况，统一回复大家：咱们的系统不需要关闭，和商户没有冲突和关系，正常运行即可。正常输出！！！
#新增通道 QQ转账（手动，自动回调）可扫码 可支持输入QQ号付款 需要查看演示联系 @lucky_66666 @LX_Liming
#新增功能 后台可自行配置查单按钮 码商可自行选项 点击后自动转发查单状态
Showing the 12 most recent of 16 posts we hold for @lixiangkejitongzhi. 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.
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 29 September 2026 — this entry's latest reading, not the date you are reading this.
“理想系统/定制/搭建/代收/代付/3+4一体/国内外支付通道” (@lixiangkejitongzhi), 1,447 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/lixiangkejitongzhi.
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.