Telegram RegisterThe public register of Telegram
Telegram profile photo for ⚜️鑫旺集团 国际通道⚜️

Channel

⚜️鑫旺集团 国际通道⚜️

@xinwang138

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

50subscribers

+2 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-1002303180572
TypeChannel
Username@xinwang138
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live3 October 2026
Measurements held5
Confirmed unchanged2 times, most recently 3 October 2026
On Telegramt.me/xinwang138

Topic

Gambling & betting — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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

4850497 August 2026 — 48 subscribers10 August 2026 — 48 subscribers16 August 2026 — 50 subscribers9 September 2026 — 49 subscribers18 September 2026 — 50 subscribers7 August 202618 September 2026
5 measurements spanning 41 days, net +2. 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 48–50 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 03:3950+1
9 Sept 2026, 13:5749-1
16 Aug 2026, 07:2550+2
10 Aug 2026, 13:0348no change
7 Aug 2026, 18:5148first reading

Engagement

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

Reaction mix

3 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤266.7%
🔥133.3%

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

Measured over the 20 most recent posts we hold, published 24 January 2026 to 23 July 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

23 Jul 2026, 07:03 UTC38 viewsread 10 August 2026
Photo

🎰🎰🎰🎰🎰 🎰🎰 🎰🎰 开车时间:10:00 - 22:00 卡接 紫码 绿码 🎰🎰 🎰🎰 🎰🎰 🎰🎰🎰🎰 ⚠️报备金额请如实说明资金来源和合作要求。 ⚠️若隐瞒或造假将不予结算,并追责赔偿。 📱📱📱📱📱📱📱📱 📲 @Michael13838 📲 @kioskprovider1 😶 官方频道 ➡️ ⚜️鑫旺集团 国际通道⚜️

21 Jul 2026, 10:13 UTC37 viewsread 10 August 2026
Photo

🎰🎰🎰 🎰🎰 🎰🎰 报单注明料子性质+维护期 🎰🎰 🎰🎰 卡接 拖算:3.x% 4.2x 卡接 进算:4.x% 4.2x 🎰🎰 🎰🎰 卡接 拖算:7% 4.2x 卡接 进算:10% 4.2x 🎰🎰🎰🎰 🎰🎰 电子 进算:13% 4.4 卡接 进算:16% 4.4 🎰🎰 电子 拖算:14% 4.4x 电子 进算:17% 4.4x 卡接 拖算:15% 4.5 卡接 进算:18% 4.5 北京时间 10:00 - 23:00 ⚠️请选择实时到账, 避免使用延迟到账方式⚠️ 欢迎各位老板来敲单 📲 @Michael13838 📲 @kioskprovider1 😶 官方频道 ➡️ ⚜️鑫旺集团 国际通道⚜️

15 Jun 2026, 10:55 UTC100 views0 reactionsread 10 August 2026
Photo

⚡️【鑫旺集团】⚡️ 尊敬的客户/合作伙伴: ⚠️此 @kioskprovider 账号已暂停使用⚠️ 由此带来不便,敬请谅解。 📱📱📱📱📱📱📱📱 📲 @Michael13838 📲 @kioskprovider1 😶 官方频道 ➡️ ⚜️鑫旺集团 国际通道⚜️

12 Jun 2026, 06:04 UTC95 viewsread 10 August 2026
Photo

🎰🎰🎰 🎰🎰 🎰🎰 报单注明料子性质+维护期 🎰🎰 🎰🎰 卡接 拖算:3.x% 4.1x 🎰🎰 🎰🎰 电子 拖算:6.x% 4.1x 🎰🎰🎰🎰 🎰🎰 (入款24小时后) 电子 进算:13% 4.3x 卡接 进算:14% 4.3x 北京时间 10:00 - 23:00 ⚠️请选择实时到账, 避免使用延迟到账方式⚠️ 欢迎各位老板来敲单 📲 @Michael13838 📲 @kioskprovider 😶 官方频道 ➡️ ⚜️鑫旺集团 国际通道⚜️

16 May 2026, 07:31 UTC98 viewsread 10 August 2026
Photo

🎰🎰🎰 🎰🎰 🎰🎰 报单注明料子性质+维护期 🎰🎰 🎰🎰 卡接 拖算:3.x% 4.0x 🎰🎰 🎰🎰 电子 拖算:6.x% 4.0x 🎰🎰🎰🎰 🎰🎰 (入款24小时后) 电子 进算:13% 4.3x 卡接 进算:14% 4.3x 北京时间 10:00 - 23:00 ⚠️请选择实时到账, 避免使用延迟到账方式⚠️ 欢迎各位老板来敲单 📲 @Michael13838 📲 @kioskprovider 😶 官方频道 ➡️ ⚜️鑫旺集团 国际通道⚜️

14 May 2026, 08:01 UTC81 viewsread 10 August 2026
Photo

😄😃😄😄😃 立陶宛🇱🇹公户开启 🎰🎰🎰 1000起 🎰🎰 5000起 🎰🎰 1万起 🎰🎰 2万起 🎰🎰5万起 全网唯一保当天公户入款 欢迎各位老板来敲单 📲 @Michael13838 📲 @kioskprovider 😶 官方频道 ➡️ ⚜️鑫旺集团 国际通道⚜

12 May 2026, 10:39 UTC82 viewsread 10 August 2026
Photo

😃😄😃😄😃 开车时间:12:00-23:00 三类 纯汇率 快杀 无维护 大额 小额 RTGS柜台 印度精料🎰🎰 🎰🎰 😄😃 印度大额公户🎰🎰🎰🎰🎰🎰 😄😃 印度代付 欢迎各位老板来敲单 📲 @Michael13838 📲 @kioskprovider 😶 官方频道 ➡️ ⚜️鑫旺集团 国际通道⚜️

11 May 2026, 10:03 UTC88 viewsread 10 August 2026
Photo

😃😄😃😄😃😄😃 报单注明料子性质+维护期 🎰🎰 🎰🎰 🎰🎰 🎰🎰 🎰🎰🎰🎰 北京时间 10:00 - 23:00 ⚠️请选择实时到账, 避免使用延迟到账方式⚠️ 欢迎各位老板来敲单 📲 @Michael13838 📲 @kioskprovider 😶 官方频道 ➡️ ⚜️鑫旺集团 国际通道⚜

11 May 2026, 09:44 UTC79 viewsread 10 August 2026
Photo

独家0冻结进算通道 (不是2D/3D链接)💱 可支付方式:信用卡/储蓄卡/当地三方电子钱包 💳 可承接国家:支持全球50+国家地区( 欧美首选 ) 优势在我:价格实惠 / 入金丝滑 / 到帐就回 无忌/ 可靠安全 上课时间:10:00 - 05:00 北京时间 单笔金额:2 ~ 8亿 各种货币 可承接盘口类型:除了盗刷不接,其他都可以来 欢迎各位老板来敲单 📲 @Michael13838 📲 @kioskprovider 😶 官方频道 ➡️ ⚜️鑫旺集团 国际通道⚜️

28 Apr 2026, 09:26 UTC86 views0 reactionsread 10 August 2026
Photo

🇱🇺卢森堡公户,明天可以开跑了 😃😃+ 单笔3000起 😃+ 5000起 😃+ 1万起 😃+ 2万起 单笔最大 10万,大额提前沟通 支持 实时进算 / 飘账拖算 欢迎各位老板来敲单 📲 @Michael13838 📲 @kioskprovider 😶 官方频道 ➡️ ⚜️鑫旺集团 国际通道

27 Apr 2026, 08:06 UTC103 views1 reactionsread 10 August 2026
Photo

😄😃😄😄😃 🇱🇺卢森堡公户星期5开始启用 汇率(0.90-0.92) 😃😃+ 单笔5000起 😃+ 1万起 😃+ 2万起 单笔最大 10万,大额提前沟通 支持 实时进算 / 飘账拖算 欢迎各位老板来敲单 📲 @Michael13838 📲 @kioskprovider 😶 官方频道 ➡️ ⚜️鑫旺集团 国际通道⚜

🔥1

16 Apr 2026, 13:47 UTC193 viewsread 10 August 2026
Photo

😃😄😃😃😀😃😀 开车时间:12:00-23:00 🎰🎰🎰🎰 🎰🎰 大额转账/RTGS柜台 20w - 1千万 大额提前报备也行 卸货嘎嘎快🔥 欢迎各位老板来敲单 📲 @Michael13838 📲 @kioskprovider 😶 官方频道 ➡️ ⚜️鑫旺集团 国际通道⚜️

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

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

“⚜️鑫旺集团 国际通道⚜️” (@xinwang138), 50 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/xinwang138.

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.