Telegram RegisterThe public register of Telegram

Channel

狗推营

@GTY01

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

20subscribers

+0 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-1001661589331
TypeChannel
Username@GTY01
Descriptionhttps://telegra.ph/汇旺官方担保-03-31 简单快捷 随时随地 安全靠谱 资产保障 全天自助 匿名交易
CreatedBetween 1 December 2021 and 10 July 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/GTY01

Growth

207 August 2026 — 20 subscribers11 August 2026 — 20 subscribers7 August 202611 August 2026
2 measurements spanning 4 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 19–21 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 15:4620no change
7 Aug 2026, 06:5920first reading

Engagement

20 posts held, back to 10 July 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 11 August 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
6
Videos
2
Links
31

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
7s
Average length
7s

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.

Recent posts

11 Aug 2023, 16:15 UTC127 viewsread 11 August 2026

🌐 汇旺担保供应需求信息广告 - 发布频道 🌐 汇旺担保仲裁纠纷处理规-骗子曝光频道 🌐 汇旺担保流程及费率佣金点位收费介绍 🌐 汇旺国际支付HuionePay 费率通知频道 🌐 防骗宝典•新手必看: 真假验证-导航指南 【HUIONE 🌐 汇旺担保官方频道】

31 Mar 2023, 15:19 UTC≈2,140 viewsread 11 August 2026

🌐 如何验证分辨真假汇旺 🌐 🌐 HUIONEPAY官方频道 🌐

18 Mar 2023, 10:52 UTC≈2,090 viewsread 11 August 2026

如何验证分辨真假汇旺: 汇旺担保交易客服 @hwjybot (首拼hwjy=汇旺交易+bot=🤖️) 汇旺担保交易二组 @hwkfbot((首拼hwkf=汇旺客服+bot=🤖️) 汇旺游戏自动提现 @hwgfbot (首拼hwgf=汇旺官方+bot=🤖️) 汇旺纠纷投诉仲裁 @huionebot (首拼huione=汇旺+bot=🤖️) 汇旺担保在线客服 @huionekefu (首拼huione=汇旺+kefu=客服💁) 汇旺官方支付频道 @huioneapp (首拼huione=汇旺+app=汇旺支付APP📲) 汇旺担保表情 🌐 公群注意事项 担保交易说明 担保收费标准 汇旺担保流程 供应需求频道 国际支付频道 真假群/真假汇旺工作人员验证联系 @hwjybot @hwkfbot 🔝建议把以上官方人员聊天页面置顶🔝 🌐详情可关注HUIONE PAY官方总频道🌐

14 Mar 2023, 08:26 UTC≈1,990 viewsread 11 August 2026

🌐 如何验证分辨真假汇旺 🌐 🌐 HUIONEPAY官方频道 🌐

25 Jan 2023, 23:06 UTC≈2,050 viewsread 11 August 2026

🌐 如何验证分辨真假汇旺 🌐 🌐 HUIONEPAY官方频道 🌐

24 Jan 2023, 07:55 UTC≈1,970 viewsread 11 August 2026
Photo

🌐 如何验证分辨真假汇旺 🌐 🌐 HUIONEPAY官方频道 🌐

24 Jan 2023, 07:55 UTC≈2,010 viewsread 11 August 2026
Photo

⁣🧧 汇旺钱包·2023兔年贺岁 🔥新春活动 一倍流水🔥 1️⃣首存1000u送188u 2️⃣首存3000u送588u 3️⃣首存5000u送888u 4️⃣首存10000u送1888u 5️⃣首存100000u以上 送18888u 游戏充值请勿相信任何私聊,本游戏充值提现全部在机器人里自动操作,没有任何客服。 ✅自动上下分流程: 💰U上分:点击钱包 @hwqbbot→充值→ 充值成功到帐后到游戏投注群打指令:上分+金额(如转账100后 投注群/上下分群 发送“上分100”)

22 Jan 2023, 00:34 UTC≈1,940 viewsread 11 August 2026
Photo

⁣🧧 汇旺钱包·2023兔年贺岁 🔥新春活动 一倍流水🔥 1️⃣首存1000u送188u 2️⃣首存3000u送588u 3️⃣首存5000u送888u 4️⃣首存10000u送1888u 5️⃣首存100000u以上 送18888u 游戏充值请勿相信任何私聊,本游戏充值提现全部在机器人里自动操作,没有任何客服。 ✅自动上下分流程: 💰U上分:点击钱包 @hwqbbot→充值→ 充值成功到帐后到游戏投注群打指令:上分+金额(如转账100后 投注群/上下分群 发送“上分100”)

21 Jan 2023, 09:46 UTC≈1,940 viewsread 11 August 2026

https://telegra.ph/TeleGames游戏平台-01-19 👩🏻‍💻在线咨询:@telehashgame 🎰开始游戏:@TeleGames123Bot

15 Sept 2022, 01:58 UTC≈3,320 viewsread 11 August 2026

‼️ 不符合广告推广规则的已经全部下架,请各广告主自查! 👇🏻 https://t.me/hao1234ban/117

15 Sept 2022, 01:57 UTC≈1,440 viewsread 11 August 2026

1⃣️三网dpi 联通dpi 2⃣️三网SDK MD5 3⃣️短信标签/验证码/关键词/短信内容 4⃣️百度关键词 信息流埋点 5⃣️指定网站/app渗透提取-微信QQ好友提取-海外各种数据 6⃣️德州扑克透视辅助/外挂辅助/微扑克(Wepoker)/扑克时间(PokerTime)/德扑圈(HHPoker)

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

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

“狗推营” (@GTY01), 20 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/GTY01.

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.