Telegram RegisterThe public register of Telegram
Telegram profile photo for LogVar弹幕API通知频道

Channel

LogVar弹幕API通知频道

@logvar_danmu_channel

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry

6,620subscribers

+2,797 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003054173430
TypeChannel
Username@logvar_danmu_channel
Description一个人人都能部署的基于 js 的弹幕 API 服务器,支持爱优腾芒哔咪人韩巴狐乐西埋帆红弹幕直接获取,兼容弹弹play接口规范,支持vercel/netlify/edgeone/cloudflare/docker/hf等部署方式,不用提前下载弹幕,没有nas或小鸡也能一键部署。 本频道主要发送更新通知 互助群 @logvar_danmu_group 官方项目:https://github.com/huangxd-/danmu_api.git
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 November 2026
Measurements held28
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/logvar_danmu_channel

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 13 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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

3,8236,6205,221.57 August 2026 — 3,823 subscribers7 August 2026 — 3,823 subscribers7 August 2026 — 3,827 subscribers11 August 2026 — 3,856 subscribers14 August 2026 — 3,883 subscribers17 August 2026 — 3,902 subscribers20 August 2026 — 3,913 subscribers24 August 2026 — 3,968 subscribers27 August 2026 — 4,002 subscribers30 August 2026 — 4,027 subscribers2 September 2026 — 4,036 subscribers7 September 2026 — 4,071 subscribers11 September 2026 — 4,109 subscribers15 September 2026 — 4,233 subscribers28 September 2026 — 4,507 subscribers5 October 2026 — 4,723 subscribers12 October 2026 — 5,022 subscribers15 October 2026 — 5,124 subscribers18 October 2026 — 5,262 subscribers21 October 2026 — 5,382 subscribers24 October 2026 — 5,499 subscribers27 October 2026 — 5,633 subscribers30 October 2026 — 5,788 subscribers2 November 2026 — 5,905 subscribers5 November 2026 — 6,058 subscribers8 November 2026 — 6,239 subscribers12 November 2026 — 6,409 subscribers17 November 2026 — 6,620 subscribers7 August 202617 November 2026
28 measurements spanning 102 days, net +2,797. 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 3,403–7,040 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
17 Nov 2026, 21:076,620+211
12 Nov 2026, 16:566,409+170
8 Nov 2026, 23:106,239+181
5 Nov 2026, 16:506,058+153
2 Nov 2026, 15:085,905+117
30 Oct 2026, 13:285,788+155
27 Oct 2026, 10:065,633+134
24 Oct 2026, 16:355,499+117
21 Oct 2026, 14:485,382+120
18 Oct 2026, 10:485,262+138
15 Oct 2026, 21:275,124+102
12 Oct 2026, 13:545,022+299
5 Oct 2026, 20:364,723+216
28 Sept 2026, 04:004,507+274
15 Sept 2026, 13:414,233+124
11 Sept 2026, 22:174,109+38
7 Sept 2026, 10:154,071+35
2 Sept 2026, 15:274,036+9
30 Aug 2026, 06:274,027+25
27 Aug 2026, 13:134,002first reading

Engagement

39 posts held, back to 30 April 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 9 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
36.2%
avg views ÷ 6,620 subscribers
Avg views / post
2,400
4 posts measured
Reaction rate
0.296%
reactions ÷ views · ER floor
Posts in window
4
of 39 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. It is computed over the 3 of 4 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 November 2026
Posts held39 (30 April 2026 – 14 November 2026)
Views total9,580
Reactions total19
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 20:37 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
1
Links
27

Lifetime counters from Telegram’s own channel header, read 18 November 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.

Reaction mix

245 reactions across 37 posts, in 9 distinct kinds. The most used accounts for 43.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤10743.7%
👍5622.9%
🎉5321.6%
🔥114.49%
🥰104.08%
👏41.63%
💯20.816%
🍌10.408%
🫡10.408%

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

Measured over the 39 most recent posts we hold, published 30 April 2026 to 14 November 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

Telegram’s own ‘edited’ marker: 3 of 4 posts held from the last 30 days (75.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

14 Nov 2026, 01:28 UTC≈1,130 views5 reactionsread 18 November 2026

v1.21.10 - feat: 支持特别篇 S00 映射并优化剧名年份后缀匹配 - fix(danmu): 多源时点去重按一个百分位的容差合并同一条弹幕,彻底消除多源合并时的重复弹幕( 感谢 @鸽子 🚀 ) - fix(dandan-api): 总集数按过滤后的可用集数上报( 感谢@鸽子 🎉 )

❤3🎉2

7 Nov 2026, 01:42 UTC≈2,360 views7 reactionsread 18 November 2026

v1.21.9 - feat(ai-util): 增加 AI 请求参数自适应重试机制,提升不同模型与接口参数的兼容性 - fix(ai): 识别空的 AI 响应,并在匹配提示词为空白时恢复默认值( 感谢 @YnSen 🎉 ) - feat: 支持远程季集转换表( 感谢 @xlmc 👍🏻 ) - fix(hongguo): 修复开启全集合并后无法获取弹幕的问题( 感谢 @syks0121 🚀 )

🥰5🎉1👍1

1 Nov 2026, 04:24 UTC≈2,920 views7 reactionsread 18 November 2026

v1.21.8 - fix(hongguo): 添加浏览器请求头,修复搜索接口被拒的问题 - feat: 支持远程剧名映射表( 感谢 @xlmc 🎉 ) - fix(match): 同集号去重时保留目标平台的条目( 感谢 @YnSen 👍 ) - refactor(logs): 规范化日志首标签为已归属分类( 感谢 @鸽子 ) - fix(merge): 修复类型比对未按预期生效导致的误合并,并为合并结果重新计算总集数( 感谢 @鸽子 ) - fix(tmdb): 中文标题转换按原名匹配作品,并从别名获取中文名,修复个别美剧转换错误( 感谢 @鸽子 ) - fix(tencent): 搜索补充相关分区中的多季作品,修复《一念永恒》季结果不全( 感谢 @鸽子 ) - fix(renren): 识别未上线资源,并修正封面域名与搜索日志( 感谢 @鸽子 ) - fix(offset): 偏移规则支持按完整片名匹配,并…

❤7

25 Oct 2026, 04:06 UTC≈3,170 viewsread 18 November 2026

v1.21.7 - fix(hongguo): 修复红果源 - feat: 新增腾讯与爱奇艺弹幕分片请求并发数配置 - fix: 系统管理接口强制要求 ADMIN_TOKEN - fix(hanjutv): 为韩小圈和极速版身份增加 12 小时轮换,避免常驻进程持续复用同一身份,并支持并发共享与失败重试( 感谢 @Wo254992 🎉 ) - fix(animeko): 迁移 Bangumi 镜像域名,并接入发布页备用域名回退,提升镜像失效时的可用性( 感谢 @鸽子 ) - fix(danmu): 多源合并未开启去重时仍按时间点去重,避免不同源之间的重复弹幕( 感谢 @鸽子 ) - feat(ui): 补充跟随系统切换明暗时的动效,并调整预览页总览按钮的宽度表现( 感谢 @鸽子 👍 ) - fix(vod): 移除已关停的内置采集站,将 VOD_SERVERS 默认值设为空,未配置时不再发送采集请求( 感谢 @l…

18 Oct 2026, 02:18 UTC≈3,310 views14 reactionsread 18 November 2026

v1.21.6 - feat(aiyifan): 支持普通代理、万能反代和爱壹帆专用反代,并修复本地中转未转发 POST 请求体的问题( 感谢 @Celestials316 🎉 ) - fix(danmu): 未开启去重时也按时间排序弹幕,修复弹幕乱序问题( 感谢 @鸽子 🚀 ) - fix(bilibili): 修复弹幕 proto 解析的字段标签读取,避免正文错位与弹幕丢失( 感谢 @鸽子 ) - fix(iqiyi): 统一分集标题的集数位置,修复个别作品分集标题缺少集数的问题( 感谢 @鸽子 ) - feat(ui): 明暗切换改为悬浮滑块开关,并修复主题、弹幕与合并样式的若干问题( 感谢 @鸽子 ) - fix(tencent): 补全分集标题并修复视频时长错误,普通弹幕请求不再额外获取时长( 感谢 @Desmond9527 🎉 ) - docs(edgeone): 更新 EdgeOne Maker…

❤8👍3🎉2🥰1

11 Oct 2026, 01:11 UTC≈3,390 views4 reactionsread 18 November 2026

v1.21.5 - 测试文件拆分 - fix(cache): 备份成功日志改为 info 并每进程仅提示一次( 感谢 @Wo254992 🎉 ) - fix(merge): 合并映射表规则对两侧标题一致剥离季度与类型噪声,修复特定规则匹配不上( 感谢 @鸽子 🚀 ) - feat(dandan): 详情集缺失时支持 NipaPlay 中转弹弹play服务端兜底与 Bangumi Data 补全( 感谢 @鸽子 ) - fix(hanjutv): 修复首次搜索偶发无结果并区分正常空结果日志( 感谢 @lilixu3 🚀 ) - fix(tmdb-util): 日语原名检索词剥离季与分部标记并修正副标题分隔判定( 感谢 @鸽子 ) - feat(aiyifan): 切换到 App 接口链路,年份用旧网页搜索接口补齐( 感谢 @Celestials316 🎉 ) - fix(merge): 优化合并工具年份与配音版判断…

❤3🎉1

2 Oct 2026, 15:13 UTC≈3,710 views8 reactionsread 18 November 2026

v1.21.4 - feat(dandan): 弹弹302关联链接仅分发给已在 SOURCE_ORDER 开启的源( 感谢 @鸽子 🚀 ) - refactor(ui): GitHub 标识与请求参数标题改用图标库图形( 感谢 @鸽子 ) - fix(cache): 隔离缓存后端并优先恢复 Local Redis 查询数据( 感谢 @Wo254992 🎉 ) - fix(dandan): 优化外文检索词处理,避免误杀正确命中并调整 TMDB 结果预过滤逻辑( 感谢 @Backsoon0 🚀 ) - fix(mango): 正确排序综艺标题末尾的上中下分部( 感谢 @YnSen 🎉 ) - fix(forward): 构建独立 widget 时隔离服务端本地弹幕存储 ( 感谢 @YnSen ) 大家国庆快乐~🇨🇳

❤7💯1

26 Sept 2026, 08:23 UTC≈4,040 views16 reactionsread 18 November 2026

v1.21.3 - fix(sources): 为 custom 源适配器传递 isolatedDetailStore,修复CUSTOM_SOURCE_API_URL 返回的结果无法用于自动匹配的问题 - feat(dandan): 弹弹play弹幕替代机制改用 NipaPlay 中转弹弹play服务端获取弹幕与弹弹302关联链接(需登录,通过配置 DANDANPLAY_ACCOUNT / DANDANPLAY_PASSWORD环境变量) ( 感谢 @鸽子 🚀 ) 大家中秋快乐~🌝

🎉10❤3👍3

20 Sept 2026, 14:48 UTC≈4,230 views1 reactionsread 18 November 2026
Poll

大家觉得远程剧名映射表是有必要的吗?

  1. 有必要41%
  2. 没必要15%
  3. 观望🧐47%

The shares total 103%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

❤1

20 Sept 2026, 14:40 UTC≈3,620 views0 reactionsread 18 November 2026

v1.21.2 - perf(local-danmu): 列表改用元数据索引,避免每次整份解析(感谢 @lilixu3 🚀) - fix(local-danmu): 修复 ASS 控制标签残留、样式丢失和正文误删( 感谢 @KarasuShin 🎉) - fix(animeko): 迁移镜像域名 ( 感谢 @鸽子 ) - fix: 标题比对统一繁简归一,修复开启 Bangumi Data 后无职转生第三季匹配错误 ( 感谢 @鸽子 🎉)

13 Sept 2026, 05:15 UTC≈3,940 views5 reactionsread 18 November 2026

v1.21.1 - feat(local-danmu): 新增标题搜索过滤并默认折叠分组卡片;重新上传与整组删除;新增 PATCH 接口支持编辑本地弹幕元数据;支持电视剧本地弹幕文件批量导入 - fix(ui): 让原生 select 下拉菜单跟随明暗主题配色 - fix(youku): cna 获取失败时本地生成兜底,避免 500 ( 感谢 @lilixu3 🚀 ) - fix(local-danmu): 修正 B 站 XML 弹幕颜色解析 ( 感谢 @lilixu3 ) - refactor(ui): 前端图标统一为自绘线性 SVG 图标,替换原有 emoji 图标 ( 感谢 @鸽子 🎉 )

❤3🎉1🔥1

11 Sept 2026, 23:51 UTC≈3,360 views7 reactionsread 18 November 2026

v1.21.0 - feat(local-danmu): 新增本地弹幕上传、解析与管理功能;新增 LOCAL_DANMU_NOT_REQUIRE_ADMIN 环境变量控制上传/删除权限,默认仅管理员可操作,设为 true 时普通 TOKEN 用户也可执行;Node/Docker 部署将资源保存至 .cache/local-danmu,云端部署使用 Redis 持久化 - fix: update fork sync actions for Node.js 24 ( 感谢 @sugarbliss ) - fix: fongmi 接口自动匹配增加季数比对,修复跨季同号集错配 ( 感谢 @mz289 🚀) - refactor(ui): 前端图标统一为自绘线性 SVG 图标,替换原有 emoji 图标 ( 感谢 @鸽子 🎉)

👍6🎉1

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

20 Sept 2026, 14:48 UTCAnonymous Poll272 voters

大家觉得远程剧名映射表是有必要的吗?

  1. 有必要41%
  2. 没必要15%
  3. 观望🧐47%

The shares total 103%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 39 most recent posts we hold, published 30 April 2026 to 14 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“LogVar弹幕API通知频道” (@logvar_danmu_channel), 6,620 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/logvar_danmu_channel.

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.