Telegram RegisterThe public register of Telegram
Telegram profile photo for 三方跑分 支付宝代收付 网关商户

Channel

三方跑分 支付宝代收付 网关商户

@xiaobao_8882

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

59subscribers

+0 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002112495070
TypeChannel
Username@xiaobao_8882
CreatedBetween 1 November 2023 and 27 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live11 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/xiaobao_8882

Growth

576058.58 August 2026 — 59 subscribers8 August 2026 — 57 subscribers10 August 2026 — 57 subscribers25 August 2026 — 58 subscribers1 September 2026 — 60 subscribers11 September 2026 — 59 subscribers598 August 202611 September 2026
6 measurements spanning 34 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 57–60 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 09:0159-1
1 Sept 2026, 22:4560+2
25 Aug 2026, 05:2458+1
10 Aug 2026, 07:1657no change
8 Aug 2026, 22:2057-2
8 Aug 2026, 00:1759first reading

Engagement

16 posts held, back to 27 May 2024the 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 16 posts for this entry, the most recent from 18 December 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
17s
Average length
17s

Measured directly from 1 video 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.

Reaction mix

336 reactions across 11 posts, in 8 distinct kinds. The most used accounts for 16.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5516.4%
🔥5115.2%
👍4814.3%
😁4714.0%
🥰4513.4%
🎉4413.1%
👏4312.8%
🤩30.893%

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 11 of the 16 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 336 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 27 May 2024 to 18 December 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

18 Dec 2025, 04:06 UTC219 viewsread 10 August 2026
Photo

— 让搜索更高效 · 让信息更有价值 — 🔍帮你找到有趣的群组、频道、视频、音乐、电影、新闻 📢: @CJYQNEWS | 🤖: @CJYQ 👇点击下方按钮,进行搜索👇

15 Dec 2025, 04:19 UTC205 viewsread 10 August 2026
Photo

— 让搜索更高效 · 让信息更有价值 — 🔍帮你找到有趣的群组、频道、视频、音乐、电影、新闻 📢: @CJYQNEWS | 🤖: @CJYQ 👇点击下方按钮,进行搜索👇

25 Oct 2025, 02:25 UTC248 viewsread 10 August 2026
Photo

— 让搜索更高效 · 让信息更有价值 — 🔍帮你找到有趣的群组、频道、视频、音乐、电影、新闻 📢: @CJYQNEWS | 🤖: @CJYQ 👇点击下方按钮,进行搜索👇

4 Oct 2025, 00:38 UTC243 viewsread 10 August 2026
Photo

— 让搜索更高效 · 让信息更有价值 — 🔍帮你找到有趣的群组、频道、视频、音乐、电影、新闻 📢: @CJYQNEWS | 🤖: @CJYQ 👇点击下方按钮,进行搜索👇

10 Sept 2025, 00:12 UTC235 viewsread 10 August 2026
Photo

— 让搜索更高效 · 让信息更有价值 — 🔍帮你找到有趣的群组、频道、视频、音乐、电影、新闻 📢: @CJYQNEWS | 🤖: @CJYQ 👇点击下方按钮,进行搜索👇

7 Aug 2024, 10:43 UTC≈3,870 views23 reactionsread 10 August 2026
Photo

余额宝白资,包永久司法,有需要联系。大额单笔过。 ❤️❤️联系: @LLll6886

12👍3🔥3🤩3👏1🥰1

25 Jun 2024, 10:44 UTC≈4,170 views18 reactionsread 10 August 2026
Photo

兄弟们2024年过了6个月了 努力搞钱吧 兄弟 没有妹子一直永远18岁,但永远一直有18岁的妹子 跑分,捞钱,不上班,不纳税 底层唯一出路,兄弟们把握机会吧 弄不到真正的大钱 至少可以让你有点喘息的空间 普通人,认真做,每天几千,足够解决一些问题了

5🎉5👍3😁2👏1🔥1🥰1

15 Jun 2024, 14:02 UTC≈3,970 views86 reactionsread 10 August 2026
Photo

mo宝 进件视频请提前拍好 您好~法人手持身份证视频宣读内容有所更新。:法人展示身份证信息,手持身份证正面、宣读以下内容: (1)、本单位XXXXX公司在Mo宝支付开立单位支付账户为我单位真实意愿; (2)、本单位XXXXX公司向Mo宝支付提交的所有证明材料(包括但不限于开户证明材料)真实有效,且我单位与证明材料所属人一致。 必须法人本人录制;视频要求清晰,可看清意身份证的内容 ❤️❤️联系: @LLll6886

👍16🔥16😁14👏1211🎉9🥰8

2 Jun 2024, 23:49 UTC≈2,950 views22 reactionsread 10 August 2026
Photo

小额度的来,可定额!小额料不多,先到先得,慢了拍大腿! ❤️❤️联系: @LLll6886

4🎉4👏4😁4👍2🔥2🥰2

30 May 2024, 16:22 UTC≈2,610 views38 reactionsread 10 August 2026
Photo

通知:三方网关进件可以开始整理资料了。进件默认手银网银支付,需要其他的提前说明,不说就是默认,别开下来又说这样那样的问题。用汇付宝新户的老板注意,因是新户未有使用记录,账户只默认开通B2C模式(ACS可手银),有交易日起连续、连续连续7天交易后开通B2B企业网银充值模式。看准、看准、看准 三方现户汇付宝500万额度 汇付天下小户都有户,杉德acs可以预定。 特此通知,请知悉 ❤️❤️联系: @LLll6886

😁10🥰7🔥65👍5🎉3👏2

29 May 2024, 16:44 UTC≈2,240 views24 reactionsread 10 August 2026
Photo

感谢新客户信任,你的支持就是我前进的动力,6小户已出一个。要的手快有手慢无啊,宝子 ❤️❤️联系: @LLll6886

🎉6🔥43👍3👏3🥰3😁2

29 May 2024, 07:18 UTC≈2,780 views29 reactionsread 10 August 2026
Photo

收银呗:包装的连锁店模式;一个主体10个子商户,子商户风控可以不断重制更换子商户·跑量;而且子商户不影响主体商户,收的钱直接到主体商户。 (简单的资料,就能进件一个主体和10个子商户轮训使用。) 注:适合跑纯视频会员料、棋牌内层料、色播料等; 旗舰及以下版:微信、支付宝扫码+h5收单+非法人卡结算(也可以定点结算,每天设置24次定点·到账) API接口版:微信、支付宝h5收单+d0分账任意卡 (接口版-有权限自主添加材料审核,开主商户拖子商户。1拖10是固定的,可以10拖100个·无限轮训) ❤️❤️联系: @LLll6886

🎉7🥰6👏54🔥3😁3👍1

Showing the 12 most recent of 16 posts we hold for @xiaobao_8882. 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.

Mentions

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 11 September 2026 — this entry's latest reading, not the date you are reading this.

“三方跑分 支付宝代收付 网关商户” (@xiaobao_8882), 59 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/xiaobao_8882.

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.