Telegram RegisterThe public register of Telegram
Telegram profile photo for 飞扬TG云控频道

Channel

飞扬TG云控频道

@FLYTGYK

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

1,506subscribers

-17 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001258082440
TypeChannel
Username@FLYTGYK
Created3 June 2021measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live24 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/FLYTGYK

Growth

1,5061,5231,514.57 August 2026 — 1,523 subscribers7 August 2026 — 1,523 subscribers8 August 2026 — 1,520 subscribers11 August 2026 — 1,518 subscribers18 August 2026 — 1,517 subscribers21 August 2026 — 1,512 subscribers24 August 2026 — 1,506 subscribers7 August 202624 August 2026
7 measurements spanning 17 days, net -17. 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 1,503–1,526 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 20:021,506-6
21 Aug 2026, 05:521,512-5
18 Aug 2026, 04:141,517-1
11 Aug 2026, 12:181,518-2
8 Aug 2026, 05:411,520-3
7 Aug 2026, 21:341,523no change
7 Aug 2026, 18:121,523first reading

Engagement

19 posts held, back to 3 June 2021the 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 19 posts for this entry, the most recent from 29 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
39m 34s
Average length
5m 39s

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

Recent posts

29 Jun 2026, 08:31 UTC≈1,910 viewsread 7 August 2026
Photo

@FLYTG88BOT 上架一点86群发号 开会员2秒一条

4 Jun 2026, 11:52 UTC≈2,510 viewsread 7 August 2026

机器人 @FLYTG88BOT 上架+1美国群发号 开会员可发2秒一条

28 Apr 2026, 05:14 UTC≈3,310 viewsread 7 August 2026

机器人 @FLYTG88BOT 更新一波86群发号库存,建议开会员使用,不开会员很容易永久禁言!!! @FLYTG88

12 Apr 2026, 09:54 UTC≈3,730 viewsread 7 August 2026
Photo

机器人上架5年以上群发86老号,不开会员可8秒一条,开会员可2秒 4秒一条 @FLYTG88BOT

25 Mar 2026, 08:53 UTC≈3,000 viewsread 7 August 2026

老号掉了,业务联系新客服号 @FLYTG88!!!

30 Jan 2026, 15:39 UTC≈4,010 viewsread 7 August 2026

+1专用群发号上新 机器人自助购买 @FLYTG88BOT

23 Jan 2026, 10:37 UTC≈4,430 viewsread 7 August 2026
Photo

自动炒群功能上线,导入消息模板即可自动发送,解放双手

20 Jan 2026, 14:58 UTCviews —

飞扬TG云控频道 pinned «自研 TG 云控运营系统 支持账号管理、数据采集、批量加群、群发私信、拉人建群、群组监听、自动回复、筛活统计等功能。 云端部署,无需电脑 24 小时挂机,多账号多任务稳定运行。 联系 : @FLYTG88 🔹 账号管理 支持 session 批量导入 / 登录 支持 session 转直登、设备参数登录 支持账号分组、储备账号、代理配置 支持批量设置头像、昵称、简介、用户名 支持账号导出、登出、下线其他设备 支持禁言检测、批量解封、换绑记录 🔹 数据采集 支持关键词搜索群组 支持指定群采集成员 支持采集活跃成员和群消息…»

15 Jan 2026, 13:52 UTC≈4,340 viewsread 7 August 2026
Video

飞扬云控群成员采集 群组拉人和用户私信教程

Signed Fly-TG群发云控

14 Jan 2026, 14:54 UTC≈3,850 viewsread 7 August 2026
Video

飞扬云控账号禁言检测和群发配置教程

Signed Fly-TG群发云控

14 Jan 2026, 14:53 UTC≈3,510 viewsread 7 August 2026
Video

飞扬云控账号自动回复和群组监听教程

Signed Fly-TG群发云控

14 Jan 2026, 14:53 UTC≈3,080 viewsread 7 August 2026
Video

飞扬云控群组搜索和批量添加群组和文件夹教程

Signed Fly-TG群发云控

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

Citation-graph rank

Citation-graph rank — 544,666 of 1,620,105entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“飞扬TG云控频道” (@FLYTGYK), 1,506 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/FLYTGYK.

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.