Channel
@doubebly003
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
5,011subscribers
-201 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002406654464 |
|---|---|
| Type | Channel |
| Username | @doubebly003 |
| Created | Between 1 September 2024 and 12 February 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/doubebly003 |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 18:10 | 5,011 | -5 |
| 1 Nov 2026, 17:44 | 5,016 | -7 |
| 29 Oct 2026, 14:29 | 5,023 | -8 |
| 26 Oct 2026, 20:51 | 5,031 | -7 |
| 24 Oct 2026, 00:19 | 5,038 | -7 |
| 20 Oct 2026, 20:07 | 5,045 | -8 |
| 18 Oct 2026, 03:37 | 5,053 | -12 |
| 15 Oct 2026, 11:41 | 5,065 | -4 |
| 12 Oct 2026, 15:18 | 5,069 | -20 |
| 6 Oct 2026, 00:57 | 5,089 | -11 |
| 28 Sept 2026, 22:14 | 5,100 | -22 |
| 18 Sept 2026, 20:38 | 5,122 | -9 |
| 14 Sept 2026, 19:20 | 5,131 | -7 |
| 11 Sept 2026, 03:58 | 5,138 | -14 |
| 6 Sept 2026, 09:59 | 5,152 | -7 |
| 2 Sept 2026, 03:43 | 5,159 | -4 |
| 30 Aug 2026, 00:08 | 5,163 | -2 |
| 26 Aug 2026, 19:04 | 5,165 | -4 |
| 24 Aug 2026, 04:46 | 5,169 | -8 |
| 20 Aug 2026, 18:23 | 5,177 | first reading |
20 posts held, back to 12 February 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 7 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 20 posts for this entry, the most recent from 29 March 2026. An engagement rate over an empty window would be a number about nothing.
429 reactions across 19 posts, in 12 distinct kinds. The most used accounts for 58.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 249 | 58.0% | |
| ❤ | 113 | 26.3% | |
| 🍾 | 23 | 5.36% | |
| 🤡 | 16 | 3.73% | |
| 👏 | 11 | 2.56% | |
| 🍌 | 5 | 1.17% | |
| 👻 | 3 | 0.699% | |
| 🔥 | 3 | 0.699% | |
| 👎 | 2 | 0.466% | |
| 😁 | 2 | 0.466% | |
| 🍓 | 1 | 0.233% | |
| 🎉 | 1 | 0.233% |
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 429 reactions 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 12 February 2025 to 29 March 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.
镜像更新 doube-ofiii:1.1.7 增加4gtv频道，移除ofiii的点播，取消sd参数默认选择源的最高画质 docker pull doubebly/doube-ofiii:1.1.7 vps部署： docker run -d --name=doube-ofiii -p 50002:5000 -e MY_OFIII_TOKEN=Doubebly --restart=always doubebly/doube-ofiii:1.1.7 # 直播TXT订阅地址: http://ip:50002/Sub.txt?token=<TOKEN>&proxy=true # 直播M3u订阅地址: http://ip:50002/Sub.m3u?token=<TOKEN>&proxy=true # 订阅链接不加参数默认 proxy=false, 如果需要代理ts修改 proxy=true 交流群：https://t.m…
❤17
镜像更新 doube-ofiii:1.1.5 修正点播列表实时获取最新 修正指定视轨获取异常 docker pull doubebly/doube-ofiii:1.1.5 vps部署： docker run -d --name=doube-ofiii -p 50002:5000 -e MY_OFIII_TOKEN=Doubebly --restart=always doubebly/doube-ofiii:1.1.5 # 为简化部署方式使用设置环境变量 MY_OFIII_TOKEN 作为订阅的token, 部署时修改默认的 Doubebly # 直播TXT订阅地址: http://192.168.31.200:50002/Sub.txt?token=<TOKEN>&sd=1080&proxy=true # 直播M3u订阅地址: http://192.168.31.200:50002/Sub.m3u?token=<…
👍15❤10🔥1
国内配置http代理达到免翻的效果 { "name": "SMT直播(py)", "type": 3, "api": "./SMT.py", "ext": { "proxy": "http://192.168.31.13:10808" } } 国外配置如下 { "name": "SMT直播(py)", "type": 3, "api": "./SMT.py", "ext": {} }
❤4
（已失效！！！） SMT的py修复 #使用http代理的，使用下面的配置 { "name": "SMT直播(python)", "type": 3, "api": "https://json.doube.eu.org/python/live_smt.py", "ext": { "proxy": { "http": "http://127.0.0.1:10809", "https": "http://127.0.0.1:10809" } } } （已失效！！！） #挂梯或者海外用户，使用下面的配置 { "name": "SMT直播(python)", "type": 3, "api": "https://json.doube.eu.org/python/live_smt.py", "ext": {} } 交流群：https://t.me/doubeb…
❤9👏9👍3🤡3😁2
影视直播配置： (大陆网络才能观看) { "name": "快直播(python)", "type": 3, "api": "https://json.doube.eu.org/python/live_kzb.py", "ext": "68747470733A2F2F6A7A623132332E7A68756261696368656E672E636F6D2F70726F642D6170692F697074762F676574497074764C697374" } 交流群：https://t.me/doubebly001 通知群：https://t.me/doubebly003
👍13❤7
{ "name": "BeeSport直播(python)", "type": 3, "api": "https://json.doube.eu.org/python/live_beesport.py", "ext": {}, "header": { "Referer": "https://p.m82xg4z0cdbz7.com/" } }
👍9❤1
镜像更新 doube-ofiii:1.1.3 修复 三立新聞iNEWS,倪珍播新聞,倪珍英語新聞,倪珍越南語新聞 频道异常 理论任意地区vps部署都可以观看 软路由部署的话还是用 1.1.1 版本的方法 docker pull doubebly/doube-ofiii:1.1.3 vps部署： docker run -d --name=doube-ofiii -p 50002:5000 -e MY_OFIII_TOKEN=Doubebly --restart=always doubebly/doube-ofiii:1.1.3 # 为简化部署方式使用设置环境变量 MY_OFIII_TOKEN 作为订阅的token, 部署时修改默认的 Doubebly # 直播TXT订阅地址: http://ip:port/Sub.txt # 直播M3u订阅地址: http://ip:port/Sub.m3u # 点播M3u…
👍17❤10🍓1
镜像更新 doube-ofiii:1.1.2 理论任意地区vps部署都可以观看 docker pull doubebly/doube-ofiii:1.1.2 软路由部署的话还是用上个版本的方法 vps部署： docker run -d --name=doube-ofiii -p 50002:5000 -e MY_OFIII_TOKEN=Doubebly --restart=always --dns=8.8.8.8 doubebly/doube-ofiii:1.1.2 # 先去 https://app.alice.ws 注册账号，然后把你的vps的IP添加到他官网提供的dns解锁中， 添加成功之后会给你一个解锁HK和TW的IP，把上面--dns=8.8.8.8中的8.8.8.8替换成他给你提供的IP，最后你就可以愉快的玩耍了！！ # 为简化部署方式使用设置环境变量 MY_OFIII_TOKEN 作为订阅的token…
❤5🔥1
镜像更新 doube-ofiii:1.1.1 仅限台湾vps部署或者软路由部署给容器台湾节点的代理 # 简化token配置方式，移除ua验证，移除跑路函数， 前端框架由Flask更换为FastAPI docker pull doubebly/doube-ofiii:1.1.1 台湾vps部署： docker run -d --name=doube-ofiii -p 50002:5000 -e MY_OFIII_TOKEN=Doubebly --restart=always doubebly/doube-ofiii:1.1.1 软路由部署，下面运行命令中的"http://192.168.50.50:7890"为你软路由设置的台湾节点http代理： docker run -d --name=doube-ofiii -p 50002:5000 -e MY_OFIII_TOKEN=Doubebly --restart=a…
👍16❤7👎1
这个是可以配置http代理的配置 { "name": "SMT直播(python)", "type": 3, "api": "https://gh-proxy.com/https://raw.githubusercontent.com/doube-ba/Sub/refs/heads/main/live/live_smt_proxy_001.py", "ext": { "proxy": { "http": "http://127.0.0.1:10809", "https": "http://127.0.0.1:10809" } } }
👍10❤2🤡1
SMT影视直播订阅(需翻)： https://gh-proxy.com/https://raw.githubusercontent.com/doube-ba/Sub/refs/heads/main/live/smt.json
影视专用LITV直播配置： # 如果你非台湾用户，用以下json配置，下面的http://127.0.0.1:10809为台湾的http代理： { "lives": [ { "name": "LITV直播(python)", "type": 3, "api": "https://gh-proxy.com/https://raw.githubusercontent.com/doube-ba/Sub/refs/heads/main/live/live_litv.py", "ext": { "proxy": { "http": "http://127.0.0.1:10809", "https": "http://127.0.0.1:10809" } } } ] } # …
👍22❤4
Showing the 12 most recent of 20 posts we hold for @doubebly003. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“点播直播通知群” (@doubebly003), 5,011 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/doubebly003.
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.