Channel
@lanxunxitong
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
516subscribers
+3 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003526303849 |
|---|---|
| Type | Channel |
| Username | @lanxunxitong |
| Created | 23 January 2026 — measured — dated from the channel’s first post |
| First recorded | 16 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/lanxunxitong |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 17:06 | 516 | +3 |
| 16 Aug 2026, 19:30 | 513 | no change |
| 16 Aug 2026, 19:15 | 513 | first reading |
18 posts held, back to 23 January 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 pageof 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 13 August 2026 |
|---|---|
| Posts held | 18 (23 January 2026 – 13 August 2026) |
| Views total | 616 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Aug 2026, 19:30 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.
6 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 100.0% |
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 6 of the 18 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 6reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 23 January 2026 to 13 August 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.
# 0812更新内容 - 优化机器人预付调额指令，调额备注中自动追加计算公式如6.82*1000 - 新增机器人预付记录查询，执行+0自动回执今日预付记录； - 优化机器人预付调额通知，今日预付计算拆分为 今日净预付 与 结算核销； - 新增机器人/uj指令参数，/uj 1000查询U价时附带换算参考； - 新增供应商带图查单（供应商发送单号+退款截图时），自动推送至对应商户群，并同步发送至管理群，自带群消息链接，点击可跳转至对应群消息 - 新增供应商退款自动预付开关，开启后供应商触发带图查单退款时，自动为供应商与商户各增加订单金额的预付；功能默认开关，需管理员手动为供应商开启； - 优化通道路由时上游通道接单但响应报文中无支付链接的判断，按下单失败算触发预警与轮询；
澜讯四方系统-专注于系统与支付的系统商 （前30名客户 永久收费万3 后续正常万5收费）无任何隐形消费！
# 代收演示系统-0717 演示后台地址：https://demo-admin-0717.pmgwmanager.top/ 后台账户demo0717 后台密码c7dh9nkp # 演示商户信息 商户登录地址：https://demo-portal.pmqwzuivviiu.xyz 登录用户名：MCH1785496974 登录密码：联系运营获取
# 0716更新内容 机器人实现转单查询功能（对外叫 带图查单 ），商户带图发送单号后自动判断订单是否为支付成功状态（成功则直接返回订单摘要信息），若等待支付状态则将订单号转换为系统单号后发送至供应商群并建立临时会话转发机制供供应商核查订单实际支付状态； - 供应商快捷回复，传话消息发送至供应商群后可以通过按钮快捷回复商户订单情况； - 建立临时对话窗口，触发带图查单后1小时内有效，商户、供应商双方可在隔离状态下通过机器人进行传话沟通； - 群机器人监测订单回调，对订单进行持续监测若订单收到支付成功回调或补单操作自动在商户群进行提醒； - 自动催单加急机制，若转发的查单消息供应商群中超过5分钟无人响应，机器人自动发送加急催促通知，提醒供应商尽快处理；
澜讯四方系统-专注于系统与支付的系统商 收取费用 跑量万3 每月200U服务器费用（独立服务器） 可选择包月服务 更优惠 无任何隐形消费 【四方代收付系统 - 全面扶持】 - 全自动查单对账｜赠送高效机器人助力 - 高并发架构设计｜全面免费对接通道 - 立体化风控管理｜实时交易状态监控 - 简便易用｜功能全面｜全天候技术支持 🌟 自主研发·实力体现 - 采用独家自主研发技术，提供源码级别的安全保障，杜绝一切漏洞隐患。 - 提供四方和三方系统的个性化定制与搭建，满足客户的各种业务需求。 -我们不只是给你带来系统上的便利 也能为你获取你所需的支付资源！ 开户&咨询： @hunkoufan9 官方频道: @lanxunxitong 官方交流群 : @oiitt
谨防上当受骗 本人飞机号+8880471 9065 @hunkoufan9 @oiodb 其他均为假冒
澜讯代收付系统：引领支付新时代 【卓越代付系统 - 专注极致】 - API无缝对接｜即时群聊贴单｜强大后台提单 - 多通道智能调度｜精确失败拦截 ｜订单自动转派 - 秒速到账｜7×24小时不间断稳定运行 【四方代收系统 - 全面扶持】 - 全自动查单对账｜赠送高效机器人助力 - 高并发架构设计｜全面免费对接通道 - 立体化风控管理｜实时交易状态监控 - 简便易用｜功能全面｜全天候技术支持 🌟 自主研发·实力体现 - 采用独家自主研发技术，提供源码级别的安全保障，杜绝一切漏洞隐患。 - 提供四方和三方系统的个性化定制与搭建，满足客户的各种业务需求。 不仅为您提供技术支持，通过全方位的资源通道扶持，从入门到精通的一条龙指导，让每位客户无忧起步，轻松运营，实现业务的稳定增长与成功！ 联系 @hunkoufan9
❤1
澜讯集团㊗️各位合作伙伴 晨有清逸，暮有闲悠 节临福至，岁阔夏安 端午临中夏，时清日复长 愿君常安康，喜乐满庭芳 美好恰逢其时，人间又至端阳 愿衣襟带花，岁月风平，万般随喜。 祝大家端午安康，幸福接“粽”而至❤️ 也祝新老团队伙伴们节日安康，事业高“粽”
上浮2分无限收企业原声bc款 @admibo @oidext @hunkoufan9
澜讯四方系统——收费标准： 1. 每个月支付服务器费用200U 正常万3收费！ 2. 每个月支付3000元人民币，免除服务器费用，同时赠送1000万元的跑量额度。超出1000万元额度的部分，将按每万元交易收取3元的标准收费。 3.包月1.88万元 （无限跑量 无任何其他消费）
❤2
尊敬的合作伙伴： 在这充满希望和活力的马年，我们怀着感恩的心情，向您致以最诚挚的新年祝福！感谢您一路以来的支持与信任。愿新的一年中，您的事业如骏马奔腾，业务蒸蒸日上。 我们承诺继续为您提供优质的支付服务，助力您的商业成功。期待未来携手共进，共创辉煌！ 祝您和家人马年吉祥，身体健康，万事如意！ [澜讯集团] 敬上！
当前代付系统是抛弃了传统的商户网页后台，将以往商户后台的功能全部集成到了tg中，为了资金安全与便捷性。
❤3
Showing the 12 most recent of 18 posts we hold for @lanxunxitong. 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.
Citation-graph rank — 1,499,851 of 1,549,376entries 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.
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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“澜讯支付系统” (@lanxunxitong), 516 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/lanxunxitong.
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.