Telegram RegisterThe public register of Telegram
Telegram profile photo for ZOXMOLLPAY 印度老板

Channel

ZOXMOLLPAY 印度老板

@ZOXPAY888888

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

140subscribers

-4 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-1002361028400
TypeChannel
Username@ZOXPAY888888
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live5 September 2026
Measurements held4
Confirmed unchanged2 times, most recently 5 September 2026
On Telegramt.me/ZOXPAY888888

Growth

1401441427 August 2026 — 144 subscribers8 August 2026 — 144 subscribers14 August 2026 — 142 subscribers27 August 2026 — 140 subscribers7 August 202627 August 2026
4 measurements spanning 20 days, net -4. 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 139–145 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 15:35140-2
14 Aug 2026, 18:27142-2
8 Aug 2026, 21:30144no change
7 Aug 2026, 18:19144first reading

Engagement

12 posts held, back to 5 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 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 12 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Aug 2026, 11:51 UTC17 viewsread 8 August 2026
Photo

🚀 All Chinese Gateway Integration Available for India 🇮🇳 ✅ QwackPay • LGPay • OKPay • DoPay • WowPay • JikPay • SunPay • XDPay • Safe Pay • WoPay • AK Pay • Plus Pay • WePay • CowPay • HT Pay • HH Pay • YM Pay • NG Pay • HZ Pay • JIKPay • WatchPay & more… 💻 Supported Platforms: Laravel • Java • Node.js • React.js • PHP ⚡ Fast Integration 🔒 Secure & Stable 📈 High Success Rate 🛠️ 24×7 Technical Support 📩 Telegram:

8 Aug 2026, 11:43 UTC11 viewsread 8 August 2026
Forwarded from @CODENEST55Photo

✨New high quality Design ➡️investment website and Script Available 🎁 🌀Demo: DMM ME 🙏 Price: Inbox 💭 No exchange 😎 🤝 Buy For Contact 🙏 ⬇️⬇️⬇️ ➡️ @CODENEST5 ✔️ ➡️ @CODENEST5 ✔️ 🔗 Demo inbox 📴 ✔️Automatic payment gateway 🥇-jikPay 🥈- wopay 🥉- watch pay ✈️ @CODENEST55 ✈️ @CODENEST55

8 Aug 2026, 10:44 UTC27 viewsread 8 August 2026

Aa jao mujhe message karo sabi 5 logo ko admin bana huga channel or kuch bhi post kar skte ho

8 Aug 2026, 10:31 UTC26 viewsread 8 August 2026

🤩 MOLLPAY-支付🤩 1️⃣专业对接各类海外盘口 2️⃣通道稳定,平均成功率高达80% 3️⃣代收代付7×24小时,D0当天结算 4️⃣智能收付系统,API自动回调,秒级到账。 5️⃣目前可对接国家 : 印度🇮🇳,尼日利亚🇳🇬 ,印尼🇮🇩,越南🇻🇳,泰国🇹🇭,巴西🇧🇷,墨西哥🇲🇽,哥伦比亚🇨🇴… 6️⃣MT4/MT5 卡接直通车:美元🇺🇸澳元🇦🇺欧元🇪🇺新币🇸🇬马币🇲🇾日元🇯🇵港币🇭🇰印尼盾🇮🇩越南盾🇻🇳泰铢🇹🇭台币等 @mollpass @mollsspay

6 Aug 2026, 10:44 UTC43 viewsread 8 August 2026

🤩 MOLLPAY-支付🤩 1️⃣专业对接各类海外盘口 2️⃣通道稳定,平均成功率高达80% 3️⃣代收代付7×24小时,D0当天结算 4️⃣智能收付系统,API自动回调,秒级到账。 5️⃣目前可对接国家 : 印度🇮🇳,尼日利亚🇳🇬 ,印尼🇮🇩,越南🇻🇳,泰国🇹🇭,巴西🇧🇷,墨西哥🇲🇽,哥伦比亚🇨🇴… 6️⃣MT4/MT5 卡接直通车:美元🇺🇸澳元🇦🇺欧元🇪🇺新币🇸🇬马币🇲🇾日元🇯🇵港币🇭🇰印尼盾🇮🇩越南盾🇻🇳泰铢🇹🇭台币等 @mollpass @mollsspay

6 Aug 2026, 01:02 UTC46 viewsread 8 August 2026

🌸【🇮🇳moll Pay 开机通知】 ❇️ 代收稳定运行❇️ 区间:100 – 50,000 INR,❣️成功率稳定 ❇️ 代付顺畅出款❇️ 区间:100 – 50,000 INR,❣️通道超流畅 ⚡️ 代付优先处理⚡️ 区间:300 – 20,000 INR,🥰回调速度快 📈 今日参考汇率:106.5 INR 📈 💰欢迎各位老板随时咨询,多多上量💰 多多支持代付订单提交,🟢保障出款速度与稳定性🟢。 🔥 有量我们就接,有单我们就出🔥 ❤️ 如有任何问题,请第一时间联系运营,我们立马处理❤️ ———————————————— 🔈 【moll Pay Channel Live Notice】 ❇️ Pay-in is running stably❇️ Range: 100 – 50,000 INR | ❣️ Stable success rate ❇️ Payout is processing smoothly❇️ Ra

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

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

“ZOXMOLLPAY 印度老板” (@ZOXPAY888888), 140 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/ZOXPAY888888.

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.