Telegram RegisterThe public register of Telegram
Telegram profile photo for 高德集团总部 @gaode

Channel

高德集团总部 @gaode

@gaode

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

13,122subscribers

-2,104 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-1003023624739
TypeChannel
Username@gaode
Created5 October 2025 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live27 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 27 September 2026
On Telegramt.me/gaode

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

13,12215,22614,1747 August 2026 — 15,226 subscribers7 August 2026 — 15,226 subscribers8 August 2026 — 15,059 subscribers9 August 2026 — 15,039 subscribers10 August 2026 — 14,922 subscribers11 August 2026 — 14,720 subscribers12 August 2026 — 14,660 subscribers13 August 2026 — 14,603 subscribers14 August 2026 — 14,494 subscribers16 August 2026 — 14,383 subscribers17 August 2026 — 14,256 subscribers18 August 2026 — 14,179 subscribers19 August 2026 — 14,112 subscribers20 August 2026 — 14,081 subscribers21 August 2026 — 14,068 subscribers23 August 2026 — 14,018 subscribers24 August 2026 — 13,990 subscribers25 August 2026 — 13,957 subscribers26 August 2026 — 13,946 subscribers28 August 2026 — 13,939 subscribers29 August 2026 — 13,926 subscribers30 August 2026 — 13,830 subscribers31 August 2026 — 13,789 subscribers1 September 2026 — 13,756 subscribers2 September 2026 — 13,724 subscribers3 September 2026 — 13,701 subscribers4 September 2026 — 13,674 subscribers6 September 2026 — 13,634 subscribers10 September 2026 — 13,617 subscribers12 September 2026 — 13,565 subscribers14 September 2026 — 13,449 subscribers15 September 2026 — 13,362 subscribers17 September 2026 — 13,317 subscribers27 September 2026 — 13,122 subscribers7 August 202627 September 2026
34 measurements spanning 51 days, net -2,104. 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 12,806–15,542 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
27 Sept 2026, 12:3813,122-195
17 Sept 2026, 17:2013,317-45
15 Sept 2026, 13:2013,362-87
14 Sept 2026, 00:4113,449-116
12 Sept 2026, 09:4113,565-52
10 Sept 2026, 02:5713,617-17
6 Sept 2026, 21:5613,634-40
4 Sept 2026, 12:0113,674-27
3 Sept 2026, 02:3713,701-23
2 Sept 2026, 02:5213,724-32
1 Sept 2026, 03:2513,756-33
31 Aug 2026, 02:5313,789-41
30 Aug 2026, 05:3613,830-96
29 Aug 2026, 04:0813,926-13
28 Aug 2026, 03:3413,939-7
26 Aug 2026, 23:5413,946-11
25 Aug 2026, 21:4313,957-33
24 Aug 2026, 18:4413,990-28
23 Aug 2026, 02:5714,018-50
21 Aug 2026, 11:5514,068first reading

Engagement

7 posts held, back to 5 October 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 53 pages 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 7 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
3s
Average length
2s

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

281 reactions across 3 posts, in 11 distinct kinds. The most used accounts for 17.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4817.1%
❤‍🔥3713.2%
👍3211.4%
🎉3111.0%
💯269.25%
🔥269.25%
🤩269.25%
😍258.90%
🥰258.90%
🦄31.07%
👏20.712%

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

Measured over the 7 most recent posts we hold, published 5 October 2025 to 28 August 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

28 Aug 2026, 09:50 UTC≈1,050 viewsread 2 September 2026

😘全网诚邀真实玩家加入我们! 加入【高德尊贵的VIP群】 👍支持高德担保 / 飞机钱包 @fjqb 1.担保公群老板可进群😄 2.仅限今日,历史流水高于3888的(扫雷大小单双2.0赔率不计入流水)😊 3.本群将会是永久福利群,群里长期只薅红包不参与各个群任意娱乐游戏的,时间过长会清理😊 👍感谢有您!感谢支持与信任!我们将会不断的前行,也祝您越来越好!多多赢钱,暴击狗庄👍 👍联系 @gaou 为了节约时间 流水不够的不要私聊感谢!高德综合盘和极速欧骰子也算;无后门; 此群永久福利👍一起做大做强 再创辉煌! 钱包我们要做最屌的,VIP群也要做最屌的!

Signed 高德·游侠 @gaode

26 Aug 2026, 18:45 UTC≈1,290 views1 reactionsread 2 September 2026

https://t.me/+fsnYj7GBox02Yzk1

❤1

Signed 高德·游侠 @gaode

21 Aug 2026, 17:55 UTC661 viewsread 26 August 2026
Photo

Photo, posted without a caption

Signed 高德·游侠 @gaode

21 Aug 2026, 17:55 UTC655 views0 reactionsread 26 August 2026
Video

😘全新玩法 公平公正 哈希埋雷 😘五个数字 完全随机 哈希开奖 😂哈希值最后的五个数字开奖,只要中一个数字就翻倍,比扫雷的概率大了5倍!!!赔率超高,最高60倍!!! ❤️❤️❤️❤️❤️❤️ 😂玩家发送指令,可以不停连发,比电子过瘾一万倍!!!一枪一炮都可能是超高回报!!! 😂玩法巨简单!发送指令 没一枪都是精髓!复制粘贴,连射暴击狗庄,爽过打鱼,爽过转转!!! 😂下注指令:五包玩法 hxml 100 5 3 😂解析:哈希埋雷(首拼)➕金额➕包数➕你要埋的雷号; 😂极速开奖!!庄家躺着挨打!!复制粘贴不停连发,狗庄噩梦!! 😘进群体验【澳博极速哈希埋雷】

Signed 高德·游侠 @gaode

7 Aug 2026, 19:16 UTC≈2,920 views2 reactionsread 2 September 2026

😘😘😘钱包 @fjqb 使用指南: 😂进入【官方客服群】😂群内管理员请仔细核对 没有头衔的都是骗子 主动私聊都是骗子😘请勿被假账号诈骗 群内可处理钱包相关所有问题!大群内处理飞机钱包以及高德担保的一切事务,认准官方群以及群内管理员,谨防上当受骗; ❤️群内小游戏板块: 【群内单挑扫雷】【群内红包接龙】 【群内埋雷红包】 😂庄家玩家必读板块: 【如何开群当庄】【玩家下注必读】 😂如何群内发红包: 【发送手气红包】【多人抽奖红包】 【固定单包红包】【本群流水红包】 【今日流水红包】【历史流水红包】 😂如何私聊/群内 发起转账: 【如何私聊转账】【群内批量转账】 【群内转账某人】 😘如何参与发布 拍卖 对赌 以及交易: 【如何发布拍卖】【如何发布对赌】 【发布参与交易】

❤2

Signed 高德·游侠 @gaode

7 Oct 2025, 13:40 UTC≈416,000 views278 reactionsread 2 September 2026
Video

👍👍 资源入口点击这里 😄飞机用高德不迷路;玩飞机您只需要记住高德 @gaode 一个ID,您的一大资源窗口;永不失联!我们能解决您99.99%的问题! 飞机钱包 @fjqb 【使用指南】 TG生态最强金融工具,批量转账、发起拍卖、对赌协议、发起交易、预测市场、娱乐开群、竞技平台,互动等一体综合型产品;新增拍卖频道 @aipai 😄😄😄😄😄😄 高德总部 @gaode 【担保开群福利】 高德担保 @gddb 公群导航 @gddh 供需发布 @ditu 【开群负责 @gaou】 【24小时客服群】【高德顶级VIP群】 【博彩交流总群】【德州牌桌通知群】 高德博彩总频道每日红包雨 @xidu 😂【高德综合盘电子/捕鱼/视讯】 😂【高德德州俱乐部】【日返红包】 👍【高德极速骰子扫雷/快三】 😂 综合盘客服 @nvwu 【全国高端外围】【全球高端包养】 【同城搜索包养】【选妃客服一号】 【选妃客…

❤45❤‍🔥37👍32🎉31💯26🔥26🤩26🥰25

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

Named by 14 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.

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

“高德集团总部 @gaode” (@gaode), 13,122 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/gaode.

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.