Telegram RegisterThe public register of Telegram
Telegram profile photo for 灰度出海供應資源♻️

Channel

灰度出海供應資源♻️

@hdgongying

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Domains linked from posts · Cite this entry

30,746subscribers

-28,844 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001763939508
TypeChannel
Username@hdgongying
Description#供应 #付费广告 #官方通知 灰度官网: www.huidu.io 交流社群: @huidu_shequ 资源社群: @hddbdaqun 灰度公群: @hddbgongqun 供需信息: @hddbgongxu 公告频道: @hddbgg 曝光频道: @hddb_bg 担保规则: @hddb_guize 安全防范: @hddbaq 灰度Bot: @huidubot 担保客服: @huiducn 对接联系: @HDdian
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/hdgongying

Topic

Marketing & affiliate — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 55% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 2 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@hdxuqiu/648557 Aug 2026, 02:45 UTC@hdgongying/64969 · this entry7 Aug 2026, 02:45 UTC1.00under a minute
@hdxuqiu/648577 Aug 2026, 03:06 UTC@hdgongying/64971 · this entry7 Aug 2026, 03:06 UTC1.00under a minute
@hdxuqiu/648587 Aug 2026, 03:10 UTC@hdgongying/64972 · this entry7 Aug 2026, 03:10 UTC1.00under a minute
@hdxuqiu/648787 Aug 2026, 07:40 UTC@hdgongying/64992 · this entry7 Aug 2026, 07:40 UTC1.00under a minute
@hdxuqiu/648797 Aug 2026, 07:43 UTC@hdgongying/64993 · this entry7 Aug 2026, 07:43 UTC1.00under a minute
@hdxuqiu/648807 Aug 2026, 08:01 UTC@hdgongying/64994 · this entry7 Aug 2026, 08:01 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@hdxuqiu22 (8/8 hand-verifiable sample passed)1.00under a minute@hdxuqiu (220)
@hddbgongxu22 (8/8 hand-verifiable sample passed)1.00under a minute@hddbgongxu (220)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 44 of the 44 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 52 comparable posts for this entry, running 7 August 2026 to 8 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 3, the earliest publisher we hold is @hddbgongxu. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

30,74659,59045,1687 August 2026 — 59,590 subscribers7 August 2026 — 59,590 subscribers7 August 2026 — 59,571 subscribers8 August 2026 — 59,520 subscribers9 August 2026 — 59,440 subscribers10 August 2026 — 59,364 subscribers11 August 2026 — 59,281 subscribers12 August 2026 — 55,984 subscribers14 August 2026 — 53,459 subscribers15 August 2026 — 53,387 subscribers16 August 2026 — 53,307 subscribers17 August 2026 — 53,219 subscribers18 August 2026 — 53,121 subscribers19 August 2026 — 53,067 subscribers20 August 2026 — 50,267 subscribers22 August 2026 — 31,612 subscribers23 August 2026 — 31,565 subscribers25 August 2026 — 31,511 subscribers26 August 2026 — 31,445 subscribers27 August 2026 — 31,427 subscribers28 August 2026 — 31,421 subscribers29 August 2026 — 31,396 subscribers30 August 2026 — 31,381 subscribers31 August 2026 — 31,298 subscribers1 September 2026 — 31,226 subscribers2 September 2026 — 31,188 subscribers3 September 2026 — 31,169 subscribers5 September 2026 — 31,141 subscribers8 September 2026 — 31,048 subscribers11 September 2026 — 30,960 subscribers13 September 2026 — 30,893 subscribers15 September 2026 — 30,852 subscribers16 September 2026 — 30,803 subscribers19 September 2026 — 30,746 subscribers7 August 202619 September 2026
34 measurements spanning 43 days, net -28,844. 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 26,419–63,917 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
19 Sept 2026, 01:1930,746-57
16 Sept 2026, 19:0130,803-49
15 Sept 2026, 00:0130,852-41
13 Sept 2026, 09:5930,893-67
11 Sept 2026, 11:1630,960-88
8 Sept 2026, 17:0131,048-93
5 Sept 2026, 09:5631,141-28
3 Sept 2026, 14:5831,169-19
2 Sept 2026, 09:2331,188-38
1 Sept 2026, 06:0431,226-72
31 Aug 2026, 03:3631,298-83
30 Aug 2026, 01:2731,381-15
29 Aug 2026, 03:1431,396-25
28 Aug 2026, 03:2531,421-6
27 Aug 2026, 01:5531,427-18
26 Aug 2026, 03:4731,445-66
25 Aug 2026, 00:4631,511-54
23 Aug 2026, 16:1531,565-47
22 Aug 2026, 05:0831,612-18,655
20 Aug 2026, 21:5650,267first reading

Engagement

1,297 posts held, back to 7 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 73 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.018%
avg views ÷ 30,746 subscribers
Avg views / post
5.4
576 posts measured
Reaction rate
17.2%
reactions ÷ views · ER floor
Posts in window
606
of 1,297 held

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 15 of 576 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 24 September 2026
Posts held1,297 (7 August 202624 September 2026)
Views total3,127
Reactions total15
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken24 Sept 2026, 09:43 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.

What this channel posts

Photos
33,300
Videos
1,790
Links
46,800

Lifetime counters from Telegram’s own channel header, read 24 September 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.

Video runtime
1h 13m
Average length
1m 32s

Measured directly from 48 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

18 reactions across 18 posts, in 5 distinct kinds. The most used accounts for 72.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1372.2%
😢211.1%
15.56%
👏15.56%
🔥15.56%

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 18 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 18 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 13 August 2026 to 24 September 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.

Recent posts

24 Sept 2026, 09:30 UTC2 viewsread 24 September 2026
Forwarded from @huiduADSPhoto

#付费广告 1️⃣1️⃣1️⃣|亚洲领先游戏供应商 游戏API集成 × 国际包网 × 中国支付方案 👍我们不仅是游戏供应商,更是值得信赖的运营伙伴! 从平台建置、游戏整合、支付串接到运营支持,提供一站式解决方案,助您快速拓展市场,实现业务持续增长。 🩷❤🧡为什么选择 DB Gaming? ✅一站式包网平台,快速打造专属娱乐品牌 ✅体育、真人等热门游戏,一键API接入 ✅智能商户后台,实时数据分析及管理 ✅专业技术团队,7×24小时技术支持 👍立即咨询专属方案,7 天内上线您的娱乐平台! ➡2026开站优惠方案 · 火热开放中 🤥官方咨询:@dbgmBot 📱游戏API集成 🌐国际包网系统 🔡中国支付方案 🌐官网:www.dbgaming.com 📢官方诚聘菁英人才 🔔官方招聘:@dbgaminghr

24 Sept 2026, 08:45 UTC4 viewsread 24 September 2026

⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣#供应 编号:7478 供应商品:✨电销推广引流模式✨ 🥰⚡️人工手拨/群呼:越南电销、印度电销、印尼电销、泰国电销、马来电销、菲律宾电销、西班牙电销、意大利电销、英国电销、比利时电销、荷兰电销、等100多个国家和地区 ⚡️Ai语音包群呼打进线WhatsApp:德国、英国、法国、荷兰、波兰、西班牙、葡萄牙、比利时、加拿大、奥地利、孟加拉、巴基斯坦、罗马尼亚、马来西亚、巴西、秘鲁、智利、伊朗、沙特、伊拉克、阿联酋、巴拉圭、乌拉圭、阿根廷、哥伦比亚、玻利维亚等等国家 🥰用户主动添加WS打粉:语音包自动播报,来电显示改为接粉号,用户主动添加WhatsApp,自动进线,粉质优、回复高,单价低超低,仅需提供数据+WS号,欧洲、南美、中东等,支持全球100+国家!支持少量测试 ☎️AI语音按键采集:录制一段语音

24 Sept 2026, 08:20 UTC11 viewsread 24 September 2026

#供应 #上押公群 【灰度担保公群供需】 📢大量收海外BC量,SEO量,支付BC料,短信卡发 Ws RCS机房一手量!要求数据活跃,渗透数据,三方支付通道数据,otp数据,支持先测后款,有实力💪的来 📢日消耗百万💲! 寻找越南🇻🇳,实力代投! 请带高流水的U地址发来! 📢找越南 一手机房,数据。越南 各种BC资源都可以来联系💻 公群老板: @Apex9 公群链接:https://t.me/+vNwuyjc6mINmYTI0 🔔【灰度公群交易报备规则】

24 Sept 2026, 08:05 UTC9 viewsread 24 September 2026

#供应 #包月供需 #付费广告 ✅【灰度会员包月供需】 💲💲💲💲 🚀️KWAI媒体开户+代投(寻求甲方slot产品,可按A首充5u结算) ✅开户返点高 ✅代投可按A计费(首充结算) ✅支持测试-->再放量 主推国家: 巴西 (首充5u) 日跑 2000+ 印尼 (首充5u) 日跑 2000+ ✈️先到先得,立即抢位联系:@MYfeifei1120 @wijaya345 起量快,成本稳,留存好,政策美丽,24小时在线,代投团队成员50+,优质素材助力盘总开盘即巅峰,可提供实时数据查看 🚀️【欢迎甲方和中介对接,返点高,茶水丰富,可谈。】 公群链接:https://t.me/+b80BZNdXopZjN2M0

24 Sept 2026, 08:03 UTC5 viewsread 24 September 2026

#供应 #包月供需 #付费广告 ✅【灰度会员公群包月供需】 💲💲💲💲 🔥 还在跑低质量短信?跑高成本投流? 🔥 BC流量最新推广方式 👉按新增首充结算,留存更好,成本更低 👉 源头机房 1500万FB账号做内容矩阵 + 私域沉淀 🎯 只对接BC项目(新盘优先) ✅ 单地区日量 2000+ 稳定出量 ✅ 成本更稳|转化更高 ✅ 按A计费(首充结算) ✅ 真人流量|无水量 ✅ 支持测试 → 再放量 🔥 主推市场 🇵🇭 菲律宾(日量8000+首充) 🇧🇩 孟加拉 (日量1500+首充) 🇵🇰 巴基斯坦(日量1000+首充) 🇻🇳 越南(日量1000+首充) 🇹🇭 泰国(日量1000+首充) 🇮🇩 印尼 (日量1000+首充) 🇮🇳印度 (日量800+首充) 以上市场大集团的新盘可配合增量 尼日利亚-柬埔寨-马来西亚等其他国家支持配合测试 📲 欢迎实力盘口对接|可包量合作 @CJCH168 @cj518 灰度公群: ht

24 Sept 2026, 08:01 UTC1 viewsread 24 September 2026
Photo

⁣#付费广告 #官方通知 💲💲💲💲 Wynso Fantasy Sports 正式上线! 打造梦幻战队,体验实时竞技与全球排行榜挑战 结合真实赛事数据、策略玩法及丰厚奖励 为平台带来更高玩家活跃度与留存率,助力运营创造更多价值。 馬上安排串接 : @HDJames @HDaries

24 Sept 2026, 07:51 UTC1 viewsread 24 September 2026

#供应 #包月供需 #付费广告 ✅【灰度会员包月供需】 💲💲💲💲 Fb 博彩牌照加白 BC代投+首充a结算 ✅博彩牌照认证加白账户,账户权重高 ✅人均高 留存好 起量快 当天可起量 ✅24小时可远程查看数据,所有素材都是原创素材 ✅测试期过后,可根据产品情况按a结算 可按a结算 可按a结算 可按a结算 主投国家: 巴西🇧🇷 墨西哥🇲🇽 秘鲁🇵🇪 智利🇨🇱 阿根廷🇦🇷 哥伦比亚🇨🇴 美国🇺🇸 🚀️【测试期过后可根据产品实际情况,按a结算】 公群老板:@Laoxu111888 对接助理:@Laoxu11117 对接助理:@Laoxu11113 公群链接:https://t.me/+IFKa_G43RdxjYTYy

24 Sept 2026, 07:45 UTC3 viewsread 24 September 2026

⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣#供应 编号:7477 供应商品:越南BC支付,通道稳定,有量可谈 商品介绍:越南BC支付,Momo Zalo VT QR 供应链接:https://www.huidu.io/zh-CN/business/31898/ 资源联系人:@ShawnNg286 交易方式:支持灰度担保交易 资源提醒:加入灰度嘉宾席会员即可享受供需资源发布及查看权益 ————————————————— 🤖 HUIDU.IO全网首款供需提醒机器人 :@huidubot ⚖️灰度防骗认证请联系:@huiduTom8 🛜灰度官网: huidu.io 🎰🎰🎰🎰🎰🎰🎰🎰🎰🎰🎰🎰🎰🎰

24 Sept 2026, 07:35 UTC6 viewsread 24 September 2026

#需求 #上押公群 【灰度担保公群供需】 需求巴西,菲律宾流量,谷歌seo黑帽白帽技术做站,可包站,ws群发技术,fb,谷歌,kwai,tk,代投,可跑pwa和谷歌上架包,kpi实时更新,可联系 @aaasan55888 咨询,所有首次合作都必须过灰度担保 公群老板 @aaasan55888 灰度公群:https://t.me/+wO3lZCx_O1U3NDZl 🔔【灰度公群交易报备规则】

24 Sept 2026, 07:31 UTC3 viewsread 24 September 2026
Forwarded from @huiduADSPhoto

#付费广告 🏏9月板球激战,在 Wynso 让你的梦幻阵容更有机会脱颖而出! 9月精彩板球赛事接连不断! 2026亚运会、西印度群岛印度巡回赛、加勒比海超级联赛等热门赛事陆续上演 对于梦幻体育玩家来说,选出一套高分阵容很重要,但在哪里竞争,同样重要! 🌟在参赛人数庞大的平台,即使你的阵容表现非常出色,也可能面临巨大的排名压力。而在 Wynso有着更小的排名竞争——相同的阵容、相同的积分,有机会获得更高的排名! 🏏 组建你的梦幻阵容 📊 根据真实比赛表现获得积分 🚀 冲击更高排行榜名次,赢取更多奖金 好阵容,值得更好的排名机会 👉 联系我们立即体验Wynso:@WynsoAPI

24 Sept 2026, 07:19 UTC4 viewsread 24 September 2026

⁣#供应 #上押公群 【灰度担保公群供需】 Sampanpay |印度专业一类支付通道 灰度公群已上压26000U 深耕印度市场四年,印度实力支付商,出海首选! 我们专注于一类资金处理,提供全方位的支付渠道: ✅纯公户原生通道,代付回调堪比闪电! ✅唤醒公户支付通道,支持最高单笔5w! ✅ 代收代付通道,24小时稳定运营! 🏦本土跑分平台,十个阿三里有八个我们的人! 卓越稳定的成功率 ,常年70+! 极具竞争力且极具吸引力的价格! D0结算 ,资金安全有保障! 公群业务员:@SampanpayYIL 灰度公群:https://t.me/+9NZAr71xgAE3NTk0 🔔【灰度公群交易报备规则】 ————————————————— 🤖 HUIDU.IO全网首款供需提醒机器人 :@huidubot ⚖️灰度防骗认证请联系:@huiduTom8 🛜灰度官网: huidu.io 🎰🎰🎰🎰🎰🎰🎰🎰🎰🎰🎰🎰🎰🎰

24 Sept 2026, 07:15 UTC4 viewsread 24 September 2026

⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣#供应 编号:7476 供应商品:中东、巴基斯坦、泰国、印度、菲律宾、南非...等支付渠道 商品介绍:海外本地支付|多国充值通道 覆盖 中东|南亚|东南亚|非洲 为海外项目提供本地化充值支付解决方案。 支持市场 UAE / KSA 阿联酋、沙特 巴基斯坦 EasyPaisa / JazzCash 本地原生双通道直连 泰国 RQ 扫码 / 卡卡 印度 原生 / 唤醒 / 扫码 菲律宾 GCash 原生 / 唤醒 / 扫码 南非 USDT / 兰特(银行转账) 孟加拉 bKash / Nagad / bKash Personal / Rocket 越南 网关直连 / 扫码 多国资源|本地化支付|项目对接 有海外项目、充值需求或正在拓展新市场,欢迎私聊咨询,可根据项目情况匹配对应通道。 以上市场之

Showing the 12 most recent of 1,297 posts we hold for @hdgongying. 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.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 5 registered channels — 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.

Domains linked from posts

13 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

photo.chelpbot.meregistrable domain: chelpbot.me6 posts · 7 August 2026 – 7 August 2026 · example post
www.huidu.ioregistrable domain: huidu.io6 posts · 7 August 2026 – 7 August 2026 · example post
huidu.io5 posts · 7 August 2026 – 7 August 2026 · example post
50.com3 posts · 7 August 2026 – 7 August 2026 · example post
717kk.game1 post · 7 August 2026 – 7 August 2026 · example post
darphastudios.com1 post · 7 August 2026 – 7 August 2026 · example post
demo.dmg1001.comregistrable domain: dmg1001.com1 post · 7 August 2026 – 7 August 2026 · example post
esasia.games1 post · 7 August 2026 – 7 August 2026 · example post
www.ggcgame.comregistrable domain: ggcgame.com1 post · 7 August 2026 – 7 August 2026 · example post
hh.vip1 post · 7 August 2026 – 7 August 2026 · example post
newgaming.com1 post · 7 August 2026 – 7 August 2026 · example post
ng-demo.com1 post · 7 August 2026 – 7 August 2026 · example post
no.com1 post · 7 August 2026 – 7 August 2026 · example post

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

“灰度出海供應資源♻️” (@hdgongying), 30,746 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/hdgongying.

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.