Telegram RegisterThe public register of Telegram
Telegram profile photo for ADMpay支付官方频道

Channel

ADMpay支付官方频道

@ADMpayBlueSea

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

95subscribers

-6 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001873638065
TypeChannel
Username@ADMpayBlueSea
CreatedBetween 1 October 2022 and 14 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live7 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/ADMpayBlueSea

Topic

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 27 September 2026 and assigned it the closest of 31 fixed categories, at 38% 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 why it has no browse page of its own yet.

Growth

95101987 August 2026 — 101 subscribers9 August 2026 — 101 subscribers6 September 2026 — 99 subscribers14 September 2026 — 98 subscribers27 September 2026 — 96 subscribers7 October 2026 — 95 subscribers7 August 20267 October 2026
6 measurements spanning 61 days, net -6. 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 94–102 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 06:3895-1
27 Sept 2026, 07:2096-2
14 Sept 2026, 12:0098-1
6 Sept 2026, 09:5599-2
9 Aug 2026, 10:17101no change
7 Aug 2026, 12:44101first reading

Engagement

18 posts held, back to 14 September 2023 — 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 16 March 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 32s
Average length
38s

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

Reaction mix

124 reactions across 12 posts, in 8 distinct kinds. The most used accounts for 69.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎8669.4%
👍1512.1%
🤬75.65%
❤64.84%
🤮54.03%
😡32.42%
🔥10.806%
😁10.806%

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 12 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 124 reactions 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 14 September 2023 to 16 March 2024, 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

16 Mar 2024, 11:58 UTC945 views11 reactionsread 9 August 2026

本团队新增印度线下卡接源头一手费率冰点。需要的老板联系(长期收购印度卡) 印度线下 三类规则 👉转账方式:只接受IMPS转账 ❄️冻结说明:冻结后入款一律不予承担,以发布的通知时间为准: ⚠️⚠️⚠️温馨提示⚠️⚠️⚠️ 1、每次入款请先与我司运营确认在进行入款。 2、转账后发付款截图到群,本群机器人会自动识别UTR,自动上分。如果发生机器人无法识别的情况,联系我司运营给予人工上分。 3、不接盗刷,公检法,上下级,电炸,纯炸。 4、最低单笔5000卢比起充值,最高为100万卢比。单笔10万以上入金问测卡. 5、IMPS入款后30分钟内冻户不负责。 6、upI付款1000起,最高10万卢比. 6、非工作时间入金,若发现冻结无法拖出,不保。 7、卡商偷钱,喊停前的进行赔付(会发账户资料以及视频流水) 8、资金涉及到司法客诉 客诉资金全数返还! ❗️❗️卡接只处理当天的入款,隔天来找一律不予处理。❗️❗️ 禁止🚫:电话转账,NEF…

👎4🤬3👍2❤1🤮1

13 Mar 2024, 14:55 UTC860 views8 reactionsread 9 August 2026

国家:欧洲欧元户—-德国、法国、意大利、荷兰、比利时、卢森堡、西班牙、葡萄牙、奥地利、芬兰、斯洛伐克、斯洛文尼亚、希腊 代收:xx% 代收单笔限额:10-5000 回U:1000起 结算周期:D0 支持终端:线下 规则: 1.如有入款金额超5000需要找客服拿新卡。 2.客户付款时需要点击(istantaneo)立即支付。 3.周一到周四转账未点击(istantaneo)立即支付需要等待24小时到账。 4.周五转账未点击(istantaneo)立即支付需要等待周一到账。 5.资金卡1转入归集卡时需保40分钟,如未到40分钟资金冻结或卡死商户自行负责。

👎3🤮3👍1🤬1

13 Mar 2024, 11:52 UTC749 views4 reactionsread 9 August 2026

本团队新增土耳其线下卡接。一手源头。有合作意向的可以咨询。 通道名称:土耳其三类 国家语言:土耳其语 人口:8468 万 人均GDP:9539 美元 支持货币:里拉TL 代收:xx 代收单笔限额:100-100000 下发时间:14:00--02:00(北京时间) 回U:1000起 结算周期:D0 支持终端:线下 通道交易时间:(土耳其时间:10:00 -23.30)-(北京时间: 15:00-04:30) 充值到账时间:FAST实时,注意:EFT 工作日1小时,假日充值工作日到账 查单注意事项: 1.用户拉起订单(须填写转款人真实名字) 2.查单时,要提供付款电子单据,转款人姓名 3.转款成功900秒以后 没有自动回调再进行查单. 4.用户必须在银行转款备注里面填写转款唯一号码 注意事项: 1.大额小额卡分开不可混用 …

👍2👎2

31 Dec 2023, 13:20 UTC≈1,330 views6 reactionsread 9 August 2026

新年即将到来:ADMpay全体员工㊗️您~新年快乐🌓 🌟愿各位新的一年🌟 🎉🔴健康、快乐、平安、幸福🔴🎉 🎉🔴龙飞凤舞 、龙凤呈祥🔴🎉 🎉🔴龙腾虎跃 、龙吟虎啸🔴🎉 🎉🔴龙游天下 、龙盘虎踞🔴🎉 龙年到来,祝各位老板风生水起,一帆风顺

👍3👎3

18 Dec 2023, 04:51 UTC≈1,430 views77 reactionsread 9 August 2026

本团队新增哈萨克线下卡,一手源头费率冰点,欢迎老板们前来咨询合作。 产品:哈萨克斯坦银行转账 结算周期:D0 点位: 支持币种: 哈萨克斯坦坚戈 支持终端: PC、手机 充值单笔限额:1500-1000000(KZT) 超过另外叫卡 下发回u: 不限制金额 帐户暂存资金最多能多少: 无限制; 交易耗时: 同行秒到,跨行10分钟左右到账,如遇特殊情况,需保承兑时间30分钟,30分钟内属盘口方。30分钟外属卡商方,拉停后一律不许入金。 代收交易时间:北京时间12:00-凌晨00:00 代付交易时间:北京时间12:00-凌晨00:00 下发时间::北京时间12:00-凌晨00:00 投诉情况:投诉冻结,提供冻结视频

👎69👍3😡3❤1🤮1

9 Dec 2023, 16:24 UTC≈1,280 views2 reactionsread 9 August 2026
Video

尼日利亚支付-规则 结算周期:D0 充值模式:VA 下发模式:回U 回U费率:实时 充值单笔限额:100-1000万 代付单笔限额:1000-500万 交易时间:24H 下发时间:24H 回U時間:24H 代付到帐时间:实时 客服时间:24H 投诉情况:投诉单笔1:1冻结,撤诉后归还,司法冻结全冻 投诉说明:截图提供银行相关资讯确认投诉原因 验盘:接通前验盘一次,开盘后随机验盘,需提供单笔充值后台或客服聊天记录

👎2

8 Dec 2023, 13:16 UTC≈1,110 viewsread 9 August 2026

乌克兰源头,欢迎各位直客四方老板来撩、价格冰点 产 品: 乌克兰 结算周期:D0 支持币种: 乌克兰格里夫纳尔(UAH) 支持终端: PC、手机 充值单笔限额:200-50000(UAH) 代付单笔限额:200-50000 (UAH) 下发回u: 不限制金额 帐户暂存资金最多能多少: 无限制 交易耗时: 正常订单10分钟内到账 ,出现延迟卸货后添加。 代收交易时间:下午14:00-凌晨2:00 (北京时间) 代付交易时间:下午14:00-凌晨2:00 (北京时间) 下发时间:下午14:00-凌晨2:00 客服时间:下午14:00-凌晨2:00 投诉情况:投诉冻结,提供冻结视频 客户盘口类型限制: 全行业

11 Nov 2023, 06:20 UTC≈1,420 views7 reactionsread 9 August 2026
Photo

印尼支付规则: 代收单笔限额:10000-50000000印尼盾 代付单笔限额:10000-50000000印尼盾 交易时间:24小时 结算规则: 所有渠道D0秒到 提现时间(回盾回U):24小时 回u 费率,参考印尼最大交易所indodax 实时费率 投诉:一类游戏客户,配合提供相关凭证,用户恶意投诉都可以解决,不需要退款。

👎3🤬3👍1

25 Oct 2023, 03:43 UTC≈1,430 views2 reactionsread 9 August 2026

泰国一类二类 💰1:成功率100%💰 💰2:结算周期:D0 下发不限额下发 💰3:支持PC、手机💰 💰4:限额: 代收3000万泰铢/日 💰 💰代收单笔限额:100-200000(泰铢) 💰 💰代付单笔限额:100-200000(泰铢)代付支持所有银行; 💰代收代付交易时间:24H💰 💰客服时间:24小时 💰投诉情况:投诉冻结按单笔1:3冻结,撤诉后归还💰 💰是否包司法: 不包💰 💰后台对帐: 商户拥有独立后台💰 💰客户盘口类型限制: 20日以内关盘的ZJP不接,前置贷超不接,四方不接一旦发现是四方直接冻结资💰金,其它均可接;💰 💰客户需要最低多少日量能才开户:不限制;

❤1👍1

24 Oct 2023, 07:24 UTC≈1,330 views2 reactionsread 9 August 2026

俄罗斯支付通道线下(卡转卡)(一手源头价格冰点) 支持货币:卢布 代收单笔限额:500-500000 结算周期:D0结算回U,回U 按当天钱庄汇率实时报价 支持终端:移动端 通道交易时间:9:00AM-22:00PM(俄罗斯时间) 客户盘口类型限制:全行业可接 ●投诉违规处理: 1.测卡后30分钟有效,超过30分钟没入金,请通知重新测卡。 2.风控原则:每笔入金需保30分内无风控和司法冻结。若出现风控/冻结,30分钟以内的冻结资金,由客户承担,30分钟以外的冻结资金由车队承担 3. 商户须如实告知产品性质,如发现产品不符,没收账户余额,终止合作。

❤2

23 Oct 2023, 05:50 UTC≈1,230 views1 reactionsread 9 August 2026

ADM支付 產品通道 GCASH原生通道 通道成功率 85% 支持幣種 PESO 結算週期 D0 充值模式 GCASH掃碼 下發模式 API 下發時間 24H 交易時間 24H 客服時間 24H 到帳時間 3~5分 單日限量 無 充值單筆限額 400~50000 代付單筆限額 50~50000 下發規則 1.轉GCASH 下發金額:單筆1000~50000 2.轉銀行卡 單筆手續費 15 PHP 下發金額:單筆1000~50000 3.下發換U免手續費 下發金額:單筆1000~無上限 下發方式 匯率當天水商報價 下發P:商戶後台提交下發後群組告知 下發U:群組確認匯率 後台提交後群組告知 注意事項 渠道日切時間:23:50~00:05 ✅支持後台對帳…

❤1

Showing the 12 most recent of 18 posts we hold for @ADMpayBlueSea. 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 7 October 2026 — this entry's latest reading, not the date you are reading this.

“ADMpay支付官方频道” (@ADMpayBlueSea), 95 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/ADMpayBlueSea.

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.