Telegram RegisterThe public register of Telegram
Telegram profile photo for IPTV研究所

Channel

IPTV研究所

@Q_IPTV

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

12,858subscribers

+1,757 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-1002293620365
TypeChannel
Username@Q_IPTV
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live1 November 2026
Measurements held53
Confirmed unchanged1 time, most recently 1 November 2026
On Telegramt.me/Q_IPTV

Topic

Other / unclassifiable — 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 46% 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 the other topics.

Growth

11,10112,94912,0257 August 2026 — 11,101 subscribers8 August 2026 — 11,120 subscribers9 August 2026 — 11,142 subscribers10 August 2026 — 11,145 subscribers11 August 2026 — 11,148 subscribers12 August 2026 — 11,176 subscribers13 August 2026 — 11,198 subscribers14 August 2026 — 11,241 subscribers16 August 2026 — 11,281 subscribers17 August 2026 — 11,300 subscribers18 August 2026 — 11,320 subscribers19 August 2026 — 11,339 subscribers20 August 2026 — 11,362 subscribers21 August 2026 — 11,376 subscribers22 August 2026 — 11,419 subscribers24 August 2026 — 11,424 subscribers25 August 2026 — 11,467 subscribers26 August 2026 — 11,486 subscribers27 August 2026 — 11,531 subscribers28 August 2026 — 11,564 subscribers29 August 2026 — 11,591 subscribers30 August 2026 — 11,600 subscribers31 August 2026 — 11,621 subscribers1 September 2026 — 11,632 subscribers2 September 2026 — 11,654 subscribers3 September 2026 — 11,657 subscribers6 September 2026 — 11,708 subscribers9 September 2026 — 11,754 subscribers11 September 2026 — 11,844 subscribers13 September 2026 — 11,878 subscribers15 September 2026 — 11,951 subscribers17 September 2026 — 12,018 subscribers27 September 2026 — 12,191 subscribers4 October 2026 — 12,375 subscribers9 October 2026 — 12,448 subscribers13 October 2026 — 12,626 subscribers14 October 2026 — 12,651 subscribers15 October 2026 — 12,671 subscribers16 October 2026 — 12,813 subscribers17 October 2026 — 12,822 subscribers19 October 2026 — 12,830 subscribers20 October 2026 — 12,844 subscribers21 October 2026 — 12,881 subscribers22 October 2026 — 12,888 subscribers23 October 2026 — 12,891 subscribers24 October 2026 — 12,905 subscribers25 October 2026 — 12,949 subscribers26 October 2026 — 12,923 subscribers28 October 2026 — 12,914 subscribers28 October 2026 — 12,898 subscribers30 October 2026 — 12,884 subscribers31 October 2026 — 12,866 subscribers1 November 2026 — 12,858 subscribers12,8587 August 20261 November 2026
53 measurements spanning 85 days, net +1,757. 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 10,824–13,226 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 53
Measured (UTC)SubscribersChange
1 Nov 2026, 00:2112,858-8
31 Oct 2026, 03:0712,866-18
30 Oct 2026, 00:1912,884-14
28 Oct 2026, 23:1012,898-16
28 Oct 2026, 00:0812,914-9
26 Oct 2026, 22:0912,923-26
25 Oct 2026, 20:4612,949+44
24 Oct 2026, 18:0012,905+14
23 Oct 2026, 18:1912,891+3
22 Oct 2026, 17:3912,888+7
21 Oct 2026, 14:1512,881+37
20 Oct 2026, 07:2712,844+14
19 Oct 2026, 06:1912,830+8
17 Oct 2026, 10:5112,822+9
16 Oct 2026, 13:1812,813+142
15 Oct 2026, 14:2012,671+20
14 Oct 2026, 17:3812,651+25
13 Oct 2026, 10:1612,626+178
9 Oct 2026, 07:5612,448+73
4 Oct 2026, 18:3512,375first reading

Engagement

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

Reaction mix

165 reactions across 23 posts, in 9 distinct kinds. The most used accounts for 53.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤8953.9%
👍3621.8%
🤡116.67%
🤮84.85%
🍌63.64%
😁63.64%
🎃31.82%
👎31.82%
🥱31.82%

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

Measured over the 26 most recent posts we hold, published 11 June 2025 to 2 September 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

1 Sept 2026, 10:36 UTC≈1,200 views1 reactionsread 3 September 2026

4GTV免梯部署 如果获取不到频道 分流建议:请将 4gtv.passwd.bond 分流到美国策略 Docker Run docker run -d \ --name iptv-4gtv-system \ -p 19950:5050 \ -v /opt/4gtv:/data/cache \ -e SEGMENTS_WINDOW=8 \ -e FETCH_TIMEOUT=4 \ -e ACCESS_TOKEN=你自定义的Token \ instituteiptv/iptv-4gtv-system:latest Docker Compose services: iptv-4gtv-system: image: instituteiptv/iptv-4gtv-system:latest container_name: iptv-4gtv-system ports: …

❤1

1 Sept 2026, 07:52 UTC≈1,250 views1 reactionsread 3 September 2026

👉IPTV推荐👈 - Strng IPTV 8K (🎀46,000+ 🎥180,000+)— 点击购买 - TREX IPTV 推荐(🎀56,000+ 🎥220,000+)— 点击购买

❤1

7 Aug 2026, 21:57 UTC≈4,470 views4 reactionsread 3 September 2026

instituteiptv/iptv-4gtv:0.0.39 1.优化线路切换 2.修正BUG 3.优化iiifo点播获取逻辑 4.优化缓存性能 5.iiifo播放地址加入缓存 6.加入302转向 instituteiptv/ofiii-plus:0.0.6 1.修復完整流媒体代理 2.修復远端数据源建立播放清单错误 3.优化频道获取逻辑

❤4

16 Jul 2026, 14:53 UTC≈5,860 views7 reactionsread 31 August 2026

MPD-HLS 全新体验 V0.0.29 0.0.29 更新任务列表 ## 已完成 - [x] 修复发布包入口错误:systemd 使用的 `mpd2hls` 现在由后台 `panel` 目标构建,不再错误打包 CLI 转换器。 - [x] 后台进程不需要 `--mpd-url`,频道 URL 继续由后台频道配置传给内部转换任务。 - [x] 新增 `--binary-role`,后台二进制固定输出 `panel`。 - [x] 新增后台 `--version` / `-V` 输出,便于安装和发布校验。 - [x] 安装脚本下载二进制后校验角色;不是 `panel` 时拒绝安装,避免 systemd 无限重启。 - [x] 将发布安装脚本同步到 `scripts/install_release.sh`,确保角色校验进入源码备份。 - [x] 版本从 `0.0.28` 更新为 `0.0.29`。 - [x] 三架构后台…

😁5❤2

16 Jul 2026, 12:34 UTC≈6,130 views4 reactionsread 31 August 2026

MPD-HLS 全新体验 V0.0.28 新增: 1.修复内容 修复“设置 8 个,列表显示 12 个” 播放列表现在严格最多显示配置数量。 运行中修改数量会立即同步到转换管线。 DASH、HLS、MPEGTS、FLV、MMT 都使用动态列表数量。 “播放列表数量”和“磁盘保留数量”已分开。 设置 8 时,播放列表是 8;磁盘可能保留 8+3=11 个作为直播边缘缓冲,这是正常保留策略。 2.修复 MMT 丢包后的连续丢帧 检测到损坏 NAL 后,会在下一个有效首分片立即恢复。 真实样本输出从 198 个视频访问单元恢复到 370 个。 3.修复 NTP 包误判 普通 IPv6 UDP 123 NTP 时钟包不再被当成 MPU 媒体解析。 真实样本错误计数从 301 降到 8,剩余 8 个来自样本开头不完整的 NAL。 4.修复历…

❤3😁1

15 Jul 2026, 22:44 UTC≈4,340 views0 reactionsread 31 August 2026
Photo

新玩具: SMRE(StreamManagerRust Enterprise)是使用 Rust 开发的直播流管理与转推系统,应用程序不会调用 FFmpeg、ffprobe、Shell 或其他外部媒体进程。流媒体解析、封装与 RTMP 发布由程序原生完成。 主要功能 HTTP-FLV、HTTP-TS、HLS 直播源转推至 RTMP/RTMPS HLS TS、CMAF/fMP4、AES-128、字节范围和外部音频支持 H.264/AVC、H.265/HEVC、AAC 原样转推 MPEG Layer I/II/III 原生转换为 AAC-LC 常驻运行和按需启停模式 频道新增、编辑、启动、停止、重启、删除和批量操作 自动重连、备用推流主机切换和推流密钥轮换 主机 CPU、内存、磁盘、网络和进程状态监控 深色终端式频道日志 在线用户近似统计 管理员用户名和密码修改 SQLite WAL 数据库、备份、恢复和升级迁移 IPv4 与 I…

7 Jul 2026, 09:03 UTC≈4,970 views3 reactionsread 31 August 2026

MPD-HLS 全新体验 V0.0.26 主要修复: 1. DASH/fMP4 的 #EXTINF 改为优先用 fMP4 样本解析出来的真实时长,不再只靠 MPD fallback。 2. 备用音频分片也改成使用解析后的真实样本时长。 3.TS 实时流时长判断:优先 PCR,其次 PES PTS,最后才用墙钟时间,并补了 33-bit 时间戳回绕处理。 4. HLS 播放列表加入默认 #EXT-X-START:TIME-OFFSET=-16.000,PRECISE=NO,让 PotPlayer 起播默认后退一点,减少贴最右边追直播边缘 导致的卡顿/跳帧。可用环境变量 MPD2HLS_HLS_START_OFFSET_SEC=0 关闭。 5. 面板重写 playlist 的路径也补了 #EXT-X-START,不会被二次处理洗掉。

🎃3

19 Jun 2026, 23:41 UTC≈7,440 views5 reactionsread 3 September 2026
Photo

注册地址: 点击注册 🍎 AppleID 共享站 免费共享 Apple ID,仅限 App Store 下载 shadowrocket小火箭 使用 点击使用

❤5

13 Jun 2026, 18:20 UTC≈6,970 views20 reactionsread 31 August 2026

MPD-HLS 全新体验 v0.0.8 更新了一批功能~! 都是你们需要的,最喜欢的功能~! 喜欢的兄弟麻烦点个 Star

👍15❤5

13 Jun 2026, 13:00 UTC≈6,520 views8 reactionsread 31 August 2026

MPD-HLS 全新体验 v0.0.6 更新了一批功能~! 都是你们需要的~! 喜欢的兄弟麻烦点个 Star

❤8

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

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

“IPTV研究所” (@Q_IPTV), 12,858 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/Q_IPTV.

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.