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

Channel

IPTV研究所

@Q_IPTV

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

11,600subscribers

+499 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 live30 August 2026
Measurements held22
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/Q_IPTV

Growth

11,10111,60011,350.57 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 subscribers7 August 202630 August 2026
22 measurements spanning 23 days, net +499. 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 11,026–11,675 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 22
Measured (UTC)SubscribersChange
30 Aug 2026, 13:3311,600+9
29 Aug 2026, 10:0811,591+27
28 Aug 2026, 13:1911,564+33
27 Aug 2026, 14:2711,531+45
26 Aug 2026, 16:2311,486+19
25 Aug 2026, 17:0711,467+43
24 Aug 2026, 14:3911,424+5
22 Aug 2026, 21:1711,419+43
21 Aug 2026, 10:0711,376+14
20 Aug 2026, 10:5211,362+23
19 Aug 2026, 11:3511,339+19
18 Aug 2026, 11:2811,320+20
17 Aug 2026, 14:3311,300+19
16 Aug 2026, 04:3411,281+40
14 Aug 2026, 11:2811,241+43
13 Aug 2026, 02:5811,198+22
12 Aug 2026, 02:3211,176+28
11 Aug 2026, 03:1111,148+3
10 Aug 2026, 06:1511,145+3
9 Aug 2026, 03:5411,142first reading

Engagement

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

ERR · 30 days
27.8%
avg views ÷ 11,600 subscribers
Avg views / post
3,220
1 post measured
Reaction rate
0.124%
reactions ÷ views · ER floor
Posts in window
1
of 18 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 7 August 2026
Posts held18 (17 September 20257 August 2026)
Views total3,220
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 23:07 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.

Reaction mix

107 reactions across 15 posts, in 6 distinct kinds. The most used accounts for 47.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5147.7%
👍3330.8%
🤮87.48%
😁65.61%
🤡65.61%
🎃32.80%

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

Measured over the 18 most recent posts we hold, published 17 September 2025 to 7 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

7 Aug 2026, 21:57 UTC≈3,220 views4 reactionsread 29 August 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,760 views7 reactionsread 29 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] 三架构后台

😁52

16 Jul 2026, 12:34 UTC≈6,060 views4 reactionsread 29 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,290 views0 reactionsread 29 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,930 views3 reactionsread 29 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≈6,790 views5 reactionsread 29 August 2026
Photo

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

5

13 Jun 2026, 18:20 UTC≈6,940 views20 reactionsread 29 August 2026

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

👍155

13 Jun 2026, 13:00 UTC≈6,490 views8 reactionsread 29 August 2026

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

8

28 May 2026, 05:14 UTC≈8,570 views0 reactionsread 29 August 2026

MPD-HLS 全新体验 V0.0.3 1.新增功能:分组多选批量删除 位置:面板 → 频道列表 → 打开「分组管理」模态框 → 顶部「分组排序 / 重命名 / 批量删除」区域 用法: 勾选每行左侧的复选框(也支持顶部"全选") 点击「批量删除选中分组(含频道)」按钮 两次 confirm 防误操作:第一次显示总数,第二次再次确认频道数 删除会连同组内所有频道一起清理:停止运行任务 → 删 HLS 输出目录 → 删 channels.json 数据 → 写审计日志

25 May 2026, 17:28 UTC≈7,430 views5 reactionsread 29 August 2026
Photo

https://github.com/judy-gotv/Rust-SOCKS5-HTTP

5

23 May 2026, 12:46 UTC≈6,700 views11 reactionsread 29 August 2026

在发布一个玩具 MPD-HLS 全新体验 重要提示 重要提示 重要提示 如果你以前安装过上个发布的版本 请备份(全新构架) /opt/mpd2hls/channels.json 然后从新全新安装, 完整完毕覆盖备份 然后在重启 即可 详情请看仓库 https://github.com/judy-gotv/MPD-HLS

9👍2

23 May 2026, 07:25 UTC≈6,250 views1 reactionsread 29 August 2026

EPG 系统 (Rust + SQLite + Redis) 仓库地址 https://github.com/judy-gotv/Rust-EPG 已更新 v0.0.8 ✨ 三大改造 1.下载阶段 — 流式落盘 新增 fetch_to_file():用 bytes_stream() 边下载边写到 /tmp/epg-fetch-xxx.tmp 不再把 84MB 一次性读进 Vec + 转 String 内存占用从 ~400MB → ~几 MB 2.解析阶段 — 流式 XML 新增 parse_xmltv_streaming():边解析边回调 on_channel / on_programme 不再把 270821 条 ProgramInput 全部存进 Vec 内存占用从 ~500MB → ~几 MB(仅当前批 1000 条) 3.入库阶段 — 分批事务 每 1000 条 一个事务批量 INSERT SQLite 不再

1

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

“IPTV研究所” (@Q_IPTV), 11,600 subscribers as measured 30 August 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.