带脚本服务功能的新版本苹果不允许上架,这个功能上不了商店了,就在 TF 里玩玩吧

Channel
APTV通知频道
@AptvPlayerChannel
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
36,024subscribers
+3,997 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 |
|---|---|
| Type | Channel |
| Username | @AptvPlayerChannel |
| Description | 该频道通知APTV软件的更新信息 APTV官网:https://aptv.app APTV - M3U播放器&IPTV交流:t.me/AptvPlayer ⚠️如果您无法进群,请联系 @AptvSupportBot 解封 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 October 2026 |
| Measurements held | 42 |
| Confirmed unchanged | 1 time, most recently 19 October 2026 |
| On Telegram | t.me/AptvPlayerChannel |
Topic
Technology — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Oct 2026, 18:31 | 36,024 | +23 |
| 18 Oct 2026, 18:51 | 36,001 | +44 |
| 17 Oct 2026, 18:20 | 35,957 | +57 |
| 16 Oct 2026, 14:49 | 35,900 | +47 |
| 15 Oct 2026, 15:58 | 35,853 | +65 |
| 14 Oct 2026, 17:57 | 35,788 | +90 |
| 13 Oct 2026, 06:01 | 35,698 | +328 |
| 8 Oct 2026, 21:59 | 35,370 | +380 |
| 4 Oct 2026, 11:36 | 34,990 | +1,086 |
| 26 Sept 2026, 03:20 | 33,904 | +964 |
| 19 Sept 2026, 06:58 | 32,940 | +39 |
| 16 Sept 2026, 20:39 | 32,901 | +36 |
| 14 Sept 2026, 21:21 | 32,865 | +23 |
| 13 Sept 2026, 04:37 | 32,842 | +43 |
| 11 Sept 2026, 04:00 | 32,799 | +17 |
| 8 Sept 2026, 07:36 | 32,782 | +75 |
| 5 Sept 2026, 04:00 | 32,707 | +20 |
| 3 Sept 2026, 06:44 | 32,687 | +23 |
| 1 Sept 2026, 22:26 | 32,664 | +23 |
| 30 Aug 2026, 23:35 | 32,641 | first reading |
Engagement
30 posts held, back to 18 May 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 130 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 37.3%
- avg views ÷ 36,024 subscribers
- Avg views / post
- 13,400
- 3 posts measured
- Reaction rate
- 0.273%
- reactions ÷ views · ER floor
- Posts in window
- 3
- of 30 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.
| Window | Rolling 30 days · latest post in window 19 October 2026 |
|---|---|
| Posts held | 30 (18 May 2026 – 19 October 2026) |
| Views total | 40,320 |
| Reactions total | 110 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 20 Oct 2026, 10:47 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
- 381
- Videos
- 32
- Links
- 177
Lifetime counters from Telegram’s own channel header, read 20 October 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
1,517 reactions across 29 posts, in 16 distinct kinds. The most used accounts for 36.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 548 | 36.1% | |
| 🙏 | 451 | 29.7% | |
| ❤ | 426 | 28.1% | |
| 🎉 | 27 | 1.78% | |
| 🔥 | 23 | 1.52% | |
| 😁 | 11 | 0.725% | |
| 🥰 | 11 | 0.725% | |
| 👏 | 6 | 0.396% | |
| 😨 | 4 | 0.264% | |
| ☃ | 2 | 0.132% | |
| 👎 | 2 | 0.132% | |
| 💯 | 2 | 0.132% | |
| 🌭 | 1 | 0.066% | |
| 🤔 | 1 | 0.066% | |
| 🤡 | 1 | 0.066% | |
| 🤷♀ | 1 | 0.066% |
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 30 of the 30 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 1,517 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 30 most recent posts we hold, published 18 May 2026 to 19 October 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
#TF #iOS 9.9.9(540) #tvOS 1.0(411) 【新增】支持添加 Python 脚本服务 【新增】支持添加 PHP 脚本服务 【新增】新增法语和韩语界面翻译 【新增】语言设置改为紧凑双语列表 【修复】修复 Netflix 视频的媒体兼容性问题 现在,不需要Docker也不需要服务器,可以在 APTV 中直接运行 python 脚本服务 可以添加文件也可以添加远程链接(https://garysclub.sharewithyou.dpdns.org/ysp-live/ysp-live-v9.5.py ), 添加完并启动,然后使用订阅配置添加: http://127.0.0.1:8767/all.m3u
👍44❤33🔥2
⚠️ 注意:若需要继续使用当前CarPlay视频功能 请勿更新 iOS 27.2 系统! 请勿更新 iOS 27.2 系统! 请勿更新 iOS 27.2 系统! #AS #iOS 1.5.12 #tvOS 1.5.12 #macOS 1.5.12 【新增】支持俄语、西班牙语、阿拉伯语、葡萄牙语及泰语 【新增】播放中可切换字幕翻译语言 【新增】支持控制频道分组显示 【新增】支持配置仅保存不重新加载 【新增】支持沿用当前请求头更新配置 【新增】支持远程禁用内置台标 【新增】频道卡片支持显示序号 【新增】支持自定义标签栏 【新增】为部分操作增加触觉反馈及开关(iOS) 【新增】增加播放进度记录开关 【新增】支持搜索标签分隔与合并显示(iOS) 【新增】增加字幕选择设置 【新增】支持 iPad 使用键盘换台(iOS) 【新增】支持频道分类拖拽排序(iOS) 【新增】CarPlay 支持九键拼音及手机键盘联动(iOS) 【新增】CarP…
❤29👍2
#AS #iOS 1.5.11 #tvOS 1.5.11 #macOS 1.5.11 【新增】CarPlay 支持浏览网页(入口:快速->浏览器) 【新增】支持中文普通话字幕识别 【新增】支持韩语字幕识别 【新增】支持粤语字幕识别 【新增】支持从相册或文件导入本地台标 【新增】CarPlay 新增“窗口铺满”设置 【新增】支持全屏滑动换台(iOS) 【新增】支持频道分类管理与频道请求头编辑 【新增】支持 ARIB B24 富样式位图字幕 【新增】支持本地视频多选添加 【新增】支持播放页切换字幕翻译服务 【新增】支持自定义全屏侧边栏背景透明度 【新增】支持频道、收藏和配置拖拽框选(macOS) 【新增】支持自定义标签栏(macOS、tvOS) 【优化】优化日语字幕模型 【优化】优化识别 WebVTT 字幕 【优化】降低启动阶段的资源占用峰值 【优化】移除腾讯云翻译内置服务(腾讯云官方下架) 【优化】适配 iPad 横屏播放页左右布…
❤26👍14🔥1
#TF #iOS 9.9.9(5.7) #tvOS 1.0(405) 【新增】支持韩语字幕识别 【新增】支持粤语字幕识别 【新增】CarPlay 支持浏览网页(入口:快速->浏览器)(iOS) 【新增】支持本地视频批量选择与删除(iOS) 【新增】CarPlay 新增"窗口铺满"设置(iOS) 【新增】支持自定义Tab栏(tvOS) 【新增】播放信息卡支持展示网速与解码状态(tvOS) 【新增】支持自定义全屏侧边栏背景透明度(tvOS) 【优化】优化日语字幕模型 【优化】CarPlay 投屏增强模式入口始终可用(iOS) 【修复】修复宽屏下 ARIB 位图字幕多行重叠的问题 【修复】移除腾讯云翻译内置服务(腾讯云官方下架) 【修复】修复 CarPlay 旋钮无法关闭播放侧栏的问题(iOS) 【修复】修复本地配置删除频道时的崩溃问题(iOS) 【修复】修复配置自动刷新失效的问题(iOS) 【修复】修复编辑配置后刷新时间未更新的问题…
❤25
📣 APTV Feedback 反馈渠道已上线! 有新功能建议、使用体验想法,或者遇到了 Bug? 欢迎随时告诉我们,你的每一条反馈都可能让 APTV 变得更好~ 👉 https://aptvplayer.userjot.com/
❤7👍2
#TF #iOS 9.9.9(505) #macOS 1.0(313) 【新增】增加中文普通话实时字幕 【新增】新增支持显示 ARIBB24 字幕 【新增】新增德语界面国际化 【新增】新增可回看当前正直播的节目 【新增】iOS 和 CarPlay 投屏增加本地网络权限提示(iOS) 【优化】完善 B 站投屏弹幕控制与跨屏刷新(iOS) 【优化】完善画面增强设置与频道状态保持 【优化】优化识别 WebVTT 字幕 【优化】优化自动字幕功能 【优化】优化 HLS 起播预选功能 【修复】修复 Xtream 配置的兼容性问题 【修复】修复一些崩溃问题 【修复】修复单频道 M3U 被误判为直链的问题
👍22❤13
I'm back 近期家中有亲人过世,暂停更新几天,没有办法及时回复群消息,有事可以通过 @AptvSupportBot 或者 邮件 联系~🙏
🙏451❤14😨4☃2🌭1👍1
部分安卓商店已出现APTV盗版app,请注意分别诈骗app,APTV是苹果全平台应用,没有任何安卓版本,请大家广而告之~ Apple平台也就是有 APTV 这一个应用,没有开发过其他的应用,如果发现其他界面和功能高度相似的App,大概率也是抄袭的盗版App
😁11❤9🤡1
#TF #iOS 9.9.9(502) #tvOS 1.0(396) 【新增】接收B站投屏时支持同时渲染弹幕,以及设置弹幕的区域、透明度、字体大小和速度 【新增】tvOS新增接收投屏功能
👍20❤4🔥1
#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) 【新增…
❤19👍1🥰1
#TF #iOS 9.9.9(494) 【新增】新增蜂窝网络投屏功能 【新增】新增投屏历史记录 部分视频App(如小红书)无法在无线CarPlay和有线+蜂窝网络下投屏,需要开启增强投屏的方式,才可以投屏
❤5
Showing the 12 most recent of 30 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 4 posts 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
- 18 October 2026
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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@me888888888888 · 52,064#1
@LoonNews · 48,265#2
@rocCHL · 36,870#3
@LUCYChannel_1024 · 7,906#4
@AironBrowser · 4,806#5
@TurnipProject · 1,560#6
@AppleNuts · 37,669#7
@SurgeTestFlightFeed · 12,937#8
@zhetengsha · 52,083#9
@st77eve · 5,748#10
@GitCube · 11,221#11
@cool_scripts · 16,337#12
@Aa28413761 · 26,545#13
@ibeta_channel · 13,574#14
@odysseyplus · 24,801#15
@GetMoeCats · 4,483#16
@HellCellZC123 · 10,841#17
@FileboxOfficial · 8,702#18
@AppDoDo · 40,860#19
@miaorelease · 2,618#20
@Ptfxq · 17,354#21
@scriptableJS · 11,221#22
@jianjiaoPD · 129,650#23
@TestFlightX · 43,883#24
@FutureEcho_Notice · 7,291#25
@NobyDa · 64,051#26
@zaihuapd · 286,320#27
@GodlyNews1 · 70,101#28
@gebaopiCloud · 101,248#29
@NewlearnerChannel · 67,871#30
@testflights · 10,838#31
@xhqcankao · 165,570#32
@tkv_ktv · 2,451#33
@tnews365 · 165,192#34
@RonnieAppsChannel · 870#35
@ApopCloud_Channel · 1,741#36
@yamby_release · 37,177#37
@scriptalking · 28,041#38
Read from Telegram’s recommendation API, most recently 5 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
@rocCHL · 36,870
Telegram ranks this channel #14 of 28 here — alongside 27 others — read 3 September 2026
@ShadowrocketNews · 47,032
Telegram ranks this channel #14 of 60 here — alongside 59 others — read 27 August 2026
@LoonNews · 48,265
Telegram ranks this channel #26 of 49 here — alongside 48 others — read 27 August 2026
@scriptalking · 28,041
Telegram ranks this channel #41 of 41 here — alongside 40 others — read 10 September 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists 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 19 October 2026 — this entry's latest reading, not the date you are reading this.
“APTV通知频道” (@AptvPlayerChannel), 36,024 subscribers as measured 19 October 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.