Telegram RegisterThe public register of Telegram

Channel

APTV通知频道

@AptvPlayerChannel

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

32,160subscribers

+133 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001730938936
TypeChannel
Username@AptvPlayerChannel
Description该频道通知APTV软件的更新信息 APTV官网:https://aptv.app APTV - M3U播放器&IPTV交流:t.me/AptvPlayer ⚠️如果您无法进群,请联系 @AptvSupportBot 解封
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/AptvPlayerChannel

Growth

32,02732,16032,093.57 August 2026 — 32,027 subscribers7 August 2026 — 32,050 subscribers8 August 2026 — 32,071 subscribers9 August 2026 — 32,096 subscribers10 August 2026 — 32,114 subscribers11 August 2026 — 32,126 subscribers12 August 2026 — 32,160 subscribers7 August 202612 August 2026
7 measurements spanning 6 days, net +133. 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 32,007–32,180 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 18:4732,160+34
11 Aug 2026, 17:1432,126+12
10 Aug 2026, 19:3432,114+18
9 Aug 2026, 19:1132,096+25
8 Aug 2026, 18:4032,071+21
7 Aug 2026, 16:2332,050+23
7 Aug 2026, 00:0232,027first reading

Engagement

20 posts held, back to 18 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
29.4%
avg views ÷ 32,160 subscribers
Avg views / post
9,450
9 posts measured
Reaction rate
0.208%
reactions ÷ views · ER floor
Posts in window
9
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held20 (18 May 202612 August 2026)
Views total85,070
Reactions total177
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 21:17 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
368
Videos
32
Links
173

Lifetime counters from Telegram’s own channel header, read 12 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
1m 16s
Average length
25s

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

741 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 58.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍43658.8%
23732.0%
🎉273.64%
🔥192.56%
🥰101.35%
👏60.81%
👎20.27%
💯20.27%
🤔10.135%
🤷‍♀10.135%

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 20 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 741reactions 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 18 May 2026 to 12 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

12 Aug 2026, 05:03 UTC≈2,730 views1 reactionsread 12 August 2026
Photo

#AS #iOS 1.5.9 #tvOS 1.5.9 #macOS 1.5.9 【新增】「画质增强」「帧率增强」 【新增】CarPlay 支持第三方 App 投屏 【新增】CarPlay 支持旋钮、触控板等非触屏车机 (iOS) 【新增】实验室新增增强版系统播放器 【新增】快速播放支持本地视频 【新增】支持 Xtream Codes 识别与配置转换 【新增】单频道/快速播放支持 HTTP、SOCKS5 代理 【新增】支持 WebVTT 字幕 【新增】配置支持置顶、右滑刷新 【新增】聚合配置支持搜索 【新增】快速播放历史支持导出 M3U、加入空白配置 【新增】增强投屏模式 (iOS) 【新增】CarPlay 支持旋钮、触控板车机 (iOS) 【新增】纵横比新增「铺满屏幕」 (iOS) 【新增】快速播放历史支持复制地址 (iOS) 【新增】实验室新增 PLTV 转 TVOD (iOS) 【新增】收藏频道支持排序 (tvOS) 【新增

1

7 Aug 2026, 01:05 UTC≈6,000 views2 reactionsread 12 August 2026
Photo

#TF #iOS 9.9.9(494) 【新增】新增蜂窝网络投屏功能 【新增】新增投屏历史记录 部分视频App(如小红书)无法在无线CarPlay和有线+蜂窝网络下投屏,需要开启增强投屏的方式,才可以投屏

2

6 Aug 2026, 01:14 UTC≈6,630 views35 reactionsread 12 August 2026
Photo

#TF #iOS 9.9.9(493) 【新增】CarPlay 新增 DLNA 投屏功能 又一重磅功能登录APTV,现在任何支持投屏的 App 都可以将视频内容投送到车机上 APTV的 TF测试版 申请条件从【购买需大于三个月】降低为【购买需大于一个月】

👍259🤷‍♀1

3 Aug 2026, 02:16 UTC≈7,940 views13 reactionsread 12 August 2026
Photo

#TF #iOS 9.9.9(489) #tvOS 1.0(393) #macOS 1.0(309) 【新增】CarPlay视频支持 旋钮 车机 【新增】支持识别 WebVTT 字幕 【新增】新增 帧率增强 功能 【新增】优化反交错功能,支持双倍帧率输出 【新增】单频道与快速播放支持 HTTP/SOCKS5 每频道代理,并兼容 sk5 别名 【新增】聚合配置候选列表支持搜索 【新增】普通投屏放开地址格式限制,非 HTTP/HTTPS 地址改为风险提示后继续投屏 【优化】重整播放器控制层布局与交互 【修复】修复使用 rtp2httpd 将 rtsp 转成 http 时的回看无法拖拽进度条的问题 【修复】修复部分频道开启帧率增强后会出现绿屏闪烁的问题 【修复】修复内置台标崩溃、不可达台标及匹配不一致的问题 【修复】修复 系统播放器 动态帧率展示异常

👍76

29 Jul 2026, 01:13 UTC≈9,970 views16 reactionsread 12 August 2026
Photo

#TF #iOS 9.9.9(484) 【新增】新增 画质增强 功能 【新增】快速播放新增支持播放本地视频 【新增】CarPlay 支持播放本地视频 【新增】新增增强投屏模式 【优化】优化组播 FCC 播放参数 【修复】修复分类名称过长导致导航栏分类按钮与工具栏按钮丢失的问题 【修复】修复部分 DLNA 投屏失败及无法搜索到设备的问题

🔥103🥰2👍1

26 Jul 2026, 11:21 UTC≈9,860 views15 reactionsread 12 August 2026
Photo

#TF #iOS 9.9.9(480) #tvOS 1.0(389) #macOS 1.0(304) 【新增】订阅链接可识别 Xtream Codes,并支持一键转换 【新增】实验室新增回看 PLTV 转 TVOD 设置项 【新增】默认纵横比增加「铺满屏幕」选项 【新增】配置列表支持右滑刷新单个配置(iOS) 【新增】配置中心支持搜索配置(tvOS) 【新增】收藏频道支持排序(tvOS) 【优化】重构配置中心的UI 【优化】优化 MMT 解码 【优化】配置中心自动定位当前使用的配置 【优化】优化全部刷新配置的处理性能(macOS) 【优化】Tab 栏选中项图标和标题跟随主题色(tvOS) 【修复】修复 iPad 屏幕镜像黑屏问题(iOS) 【修复】修复配置列表编辑状态与勾选状态未及时刷新的问题(iOS、macOS) 【修复】修复删除配置后全部刷新异常、配置导出无响应等问题(iOS) 【修复】修复搜索配置无结果时提示错误的问题(i

10🥰5

24 Jul 2026, 09:05 UTC≈9,740 views11 reactionsread 12 August 2026

#TF #iOS 9.9.9(476) #tvOS 1.0(388) #macOS 1.0(303) 【优化】升级 FFmepeg 版本至8.1.2,解决多个解码问题,同时永久保留 av3a 解码能力 若该版本无法播放某些频道,请及时向开发者(@AptvSupportBot)联系~

6👍5

19 Jul 2026, 16:22 UTC≈16,900 views32 reactionsread 12 August 2026
Photo

为庆祝世界杯结束,也为了大家有一个更好的观看决赛的体验,现开放 tvOS 和 macOS 的 Testflight 测试版本,直接点击链接即可加入测试~ tvOS: https://testflight.apple.com/join/UQfNnr7D macOS: https://testflight.apple.com/join/kU61nXPD iOS的测试名额已经满了,被 CarPlay 用户冲爆了,所以没办法开放了~ 注意:以上均为短期TF测试,如需申请长期TF测试,请在APTV群内回复:如何申请TF 如果需要使用频道融合,建议音频使用 CCTV5 的菁彩声频道 📢 APTV通知频道 👥 APTV交流群组

👍1510👏4🥰3

15 Jul 2026, 06:05 UTC≈15,300 views52 reactionsread 12 August 2026
Photo

iOS的新版本还在骑马来的路上…… 正式版本已更新 #AS #tvOS 1.5.8 #macOS 1.5.8 【新增】支持 HTTP / SOCKS5 代理 【新增】支持解码 MMT/TLV 【新增】新增快速播放单频道功能 【新增】暂停后支持通过进度条滑动快进、快退(tvOS) 【新增】自动字幕支持浮动显示,并可手动调整字幕位置 【新增】自动字幕背景支持设置透明度 【新增】字幕背景支持毛玻璃模糊效果 【新增】双语字幕支持互换主字幕和副字幕内容 【新增】个性化设置支持选择主题色(tvOS) 【新增】设置页支持恢复所有设置 【新增】添加订阅地址时支持重复确认 【新增】实验室新增多码率 HLS 优化功能 【优化】优化加载超大配置时的性能表现 【优化】翻译服务不可用时显示具体原因 【优化】完善订阅配置的单频道检测 【优化】优化系统播放器 【优化】优化分屏播放时自动字幕的显示大小(tvOS) 【优化】优化 HomePod 模式(tvOS

👍3017🎉3💯2

11 Jul 2026, 09:37 UTC≈15,100 views44 reactionsread 12 August 2026
Video

#TF #iOS 9.9.9(465) 【新增】CarPlay支持播放视频(该功能只支持 iOS26.4+ 系统) 任何可以在iPhone上播放的频道都可以在 CarPlay 上播放 该版本专属测试地址,测试结束后会移除所有的测试人员,所以已经有TF测试请勿重复添加: https://testflight.apple.com/join/cpBEcUSq 测试名额已满 ⚠️ 注意,该版本允许在驾驶时播放视频,不知道是不是苹果的bug,请大家测试时务必注意行车安全!!!

👍2913👏2

10 Jul 2026, 01:11 UTC≈14,500 views216 reactionsread 12 August 2026
Photo

APTV已得到Apple授权,将支持在 CarPlay 上播放视频🫡

👍177🎉249🔥6

4 Jul 2026, 09:19 UTC≈17,000 views22 reactionsread 12 August 2026

#TF #iOS 9.9.9(462) #tvOS 1.0(376) #macOS 1.0(293) 【新增】支持 HTTP / SOCKS5 代理 【新增】自动字幕背景支持设置透明度 【新增】字幕背景支持毛玻璃模糊效果 【新增】双语字幕支持主字幕和副字幕内容互换 【新增】设置页支持恢复所有设置 【新增】配置添加页支持快捷填写 User-Agent 和 Referer 请求头 【优化】双语字幕合并主副字幕背景,避免背景分成两块显示 【优化】统一字幕背景的圆角和内边距样式 【修复】修复播放时切换音频输出声音会丢失的问题 HTTP / SOCKS5 代理功能介绍: 现在你可以通过公开可用的 HTTP 或 SOCKS5 代理,播放部分因网络环境限制而无法直接访问的直播源。 支持三种代理设置方式: ① 全局代理 路径:设置 → 高级设置 → 代理 ② 配置级代理 路径:新增配置 → 高级 → 代理 ③ 频道级代理 可为单独频道

22

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

Posts edited after publishing

@AptvPlayerChannel edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
8 August 2026
Most recent edit
9 August 2026

Citation-graph rank

Citation-graph rank — 172,808 of 1,160,990entries 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.

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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.

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

“APTV通知频道” (@AptvPlayerChannel), 32,160 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/AptvPlayerChannel.

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.