21 Jan 2026, 06:41 UTC≈2,630 viewsread 1 September 2026
1号科技主频道（电报经营5年） 教学视频 https://t.me/FootballGPTch/37 @heimanba365
Channel
GPT足球机器人频道（1号科技）
@FootballGPTch
On this record: Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
1,269subscribers
-1 since we began measuring on 1 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001812098146 |
|---|---|
| Type | Channel |
| Username | @FootballGPTch |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 2 times, most recently 6 September 2026 |
| On Telegram | t.me/FootballGPTch |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 12:24 | 1,269 | -1 |
| 1 Sept 2026, 22:15 | 1,270 | first reading |
Engagement
20 posts held, back to 7 November 2025 — 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 21 January 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
10 Dec 2025, 12:09 UTC≈3,320 viewsread 1 September 2026
Photo
货头: 俄罗斯内幕 日期: 2025-12-10 货版: 土U19联 [滚球] 队伍: 阿里阿加足球俱乐部 U19 VS 马尼沙 U19 盘口: 客赢 -0.75 (0 - 2) 完场: 0 - 5 (红) ⬇️共享货源机器人⬇️ @footballgpt_bot
8 Dec 2025, 15:37 UTC≈2,500 viewsread 1 September 2026
Photo
货头: 三方合作：土耳其 日期: 2025-12-08 货版: 斯亚U19 [赛前] 队伍: 奥林比查 U19 VS 科瑞卡 U19 盘口: 大球 3.5 (0 - 0) 完场: 4 - 0 (红) ⬇️共享货源机器人⬇️ @footballgpt_bot
8 Dec 2025, 15:37 UTC≈1,880 viewsread 1 September 2026
Photo
货头: 三方合作：土耳其 日期: 2025-12-08 货版: 斯亚U19 [赛前] 队伍: 奥林比查 U19 VS 科瑞卡 U19 盘口: 大球 3.5 (0 - 0) 完场: - (走) ⬇️共享货源机器人⬇️ @footballgpt_bot
7 Dec 2025, 11:57 UTC≈1,320 viewsread 1 September 2026
Photo
货头: 三方合作：土耳其 日期: 2025-12-07 货版: 塞尔U19 [滚球] 队伍: 马拉多特 U19 VS TSC巴奇卡托波拉 U19 盘口: 客赢 4 (0 - 1) 完场: 3 - 3 (红) ⬇️共享货源机器人⬇️ @footballgpt_bot
7 Dec 2025, 10:19 UTC957 viewsread 1 September 2026
Photo
货头: 三方合作：土耳其 日期: 2025-12-06 货版: 土乙白 [赛前] 队伍: 凯佩兹士邦 VS 伊拉茲斯堡 盘口: 客赢 -1.75 (0 - 0) 完场: 0 - 6 (红) ⬇️共享货源机器人⬇️ @footballgpt_bot
6 Dec 2025, 06:23 UTC834 viewsread 1 September 2026
Photo
货头: 俄罗斯内幕 日期: 2025-12-05 货版: 塞浦甲 [赛前] 队伍: 帕福斯 VS 阿克里塔斯 盘口: 大球 3 (0 - 0) 完场: 4 - 0 (红) ⬇️共享货源机器人⬇️ @footballgpt_bot
4 Dec 2025, 13:24 UTC770 viewsread 1 September 2026
Photo
货头: 英国鬼 日期: 2025-12-04 货版: 东盟锦标 [赛前] 队伍: 掸联 VS 南定 盘口: 大球 2.5 (0 - 0) 完场: 0 - 3 (红) ⬇️共享货源机器人⬇️ @footballgpt_bot
3 Dec 2025, 08:02 UTC694 viewsread 1 September 2026
Photo
货头: 三方合作：东欧联盟 日期: 2025-12-02 货版: 土杯 [滚球] 队伍: 里泽士邦 VS 佩迪卡斯堡 盘口: 大球 2.75 (0 - 0) 完场: 6 - 1 (红) ⬇️共享货源机器人⬇️ @footballgpt_bot
30 Nov 2025, 11:19 UTC744 viewsread 1 September 2026
Photo
货头: 俄罗斯内幕 日期: 2025-11-30 货版: 格鲁甲 [赛前] 队伍: 克尔赫提 VS 迪拿 盘口: 客赢 -1.5 (0 - 0) 完场: 1 - 4 (红) ⬇️共享货源机器人⬇️ @footballgpt_bot
28 Nov 2025, 10:29 UTC755 viewsread 1 September 2026
Photo
货头: 三方合作：亚洲小牛 日期: 2025-11-27 货版: 印尼超 [滚球] 队伍: PSBS巴克伦佛 VS 杰帕拉 盘口: 大球 3.25 (1 - 0) 完场: 3 - 2 (红) ⬇️共享货源机器人⬇️ @footballgpt_bot
25 Nov 2025, 05:46 UTC733 viewsread 1 September 2026
Photo
货头: 三方合作：亚洲小牛 日期: 2025-11-24 货版: 北马其甲 [滚球] 队伍: 拉博特尼基 VS 斯特魯加 盘口: 客赢 -0.5 (0 - 1) 完场: 1 - 3 (红) ⬇️共享货源机器人⬇️ @footballgpt_bot
Showing the 12 most recent of 20 posts we hold for @FootballGPTch. 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
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
足球❤协议球❤️一手资源🥇包赢
@zuqiu8 · 36,129
Telegram ranks this channel #20 of 61 here — alongside 60 others — read 1 September 2026
@zuqiu8 · 36,129
Telegram ranks this channel #20 of 61 here — alongside 60 others — read 1 September 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“GPT足球机器人频道（1号科技）” (@FootballGPTch), 1,269 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/FootballGPTch.
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.