Telegram RegisterThe public register of Telegram

Channel

TeleBox Channel

@teleboxdev

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

928subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002536393541
TypeChannel
Username@teleboxdev
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/teleboxdev

Growth

9287 Aug 2026, 08:33 — 928 subscribers7 Aug 2026, 10:46 — 928 subscribers7 Aug 2026, 08:337 Aug 2026, 10:46
2 measurements taken within a single day. 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 927–929 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 10:46928no change
7 Aug 2026, 08:33928first reading

Engagement

20 posts held, back to 23 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
20.2%
avg views ÷ 928 subscribers
Avg views / post
187
7 posts measured
Reaction rate
0.427%
reactions ÷ views · ER floor
Posts in window
7
of 20 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 1 of 7 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 3 August 2026
Posts held20 (23 May 20263 August 2026)
Views total1,312
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 08:33 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

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😇150.0%
🤔150.0%

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 2 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 2reactions 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 23 May 2026 to 3 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

3 Aug 2026, 17:04 UTC85 viewsread 7 August 2026

📅 TeleBox 日报 - 2026-08-04 📊 今日提交统计 • 总提交数: 1 • TeleBox: 1 次提交 • TeleBox-Plugins: 0 次提交 🏗️ 本体更新 • versionSwitchPaths — PM2 max-memory-restart 按版本区分(mtcute=768M, teleproto=512M)

2 Aug 2026, 15:55 UTC97 viewsread 7 August 2026

📅 TeleBox 日报 - 2026-08-02 📊 今日提交统计 • 总提交数: 50 • TeleBox: 8 次提交 • TeleBox-Plugins: 42 次提交 🔌 插件更新 • acron: improve panel settings UX with descriptions • ai: improve panel settings UX with descriptions • autochangename: improve panel settings UX with descriptions • autodelcmd: improve panel settings UX with descriptions • banana: improve panel settings UX with descriptions • checkapi: improve panel settings UX with de

1 Aug 2026, 15:55 UTC132 viewsread 7 August 2026

📅 TeleBox 日报 - 2026-08-01 📊 今日提交统计 • 总提交数: 4 • TeleBox: 3 次提交 • TeleBox-Plugins: 1 次提交 🔌 插件更新 • checkapi: sync: checkapi add lowdb import; theme fix document type handling • theme: sync: checkapi add lowdb import; theme fix document type handling 🏗️ 本体更新 • runtimeManager: improve error handling during reload • pluginManager: fix cleanup binding and add listener fallback • generationContext: add FinalizationRegistr

19 Jul 2026, 15:51 UTC313 viewsread 7 August 2026

📅 TeleBox 日报 - 2026-07-19 📊 今日提交统计 • 总提交数: 18 • TeleBox: 1 次提交 • TeleBox-Plugins: 17 次提交 🔌 插件更新 • checkapi: - v6 文案优化 — 简洁但不生硬 - v6 文案全面精简 - v6 — 智能输入解析 + API端点探测 - v5 全面升级 — 2个新Provider + 6项Bug修复 + 并行化 - v4 全面升级 — 修复关键bug + 新增3个Provider + 模型更新 - v3 同步 Next — 18+ Provider / 智能输入 / 速度基准 / 多Key对比 - v2 同步 Next — URL+Key 传入、分类模型折叠、对话实测 - API Key 检测插件 — 7 家 provider 智能识别 • parsehub: 进度消息原地编辑成结果时不再漏转 • qu

18 Jul 2026, 15:48 UTC234 views1 reactionsread 7 August 2026

📅 TeleBox 日报 - 2026-07-18 📊 今日提交统计 • 总提交数: 41 • TeleBox: 2 次提交 • TeleBox-Plugins: 39 次提交 🔌 插件更新 • duckduckgo: duckduckgo — 多策略安装 curl_cffi 失败回退 • quote: - no newline between blockquote tag and content - full helptext in description with expandable sections - yvlu-style helptext + full parseArgs • subinfo: add collapsible node name list to subinfo/cha output • theme: - teleproto 全量迁移(Next→Classic) - parall

😇1

17 Jul 2026, 16:08 UTC207 viewsread 7 August 2026

📅 TeleBox 日报 - 2026-07-18 📊 今日提交统计 • 总提交数: 1 • TeleBox: 0 次提交 • TeleBox-Plugins: 1 次提交 🔌 插件更新 • yvlu: upgrade to full quote-api field support

14 Jul 2026, 16:09 UTC244 viewsread 7 August 2026

📅 TeleBox 日报 - 2026-07-15 📊 今日提交统计 • 总提交数: 8 • TeleBox: 7 次提交 • TeleBox-Plugins: 1 次提交 🔌 插件更新 • ping: - tcping 走 config.json / PM2 代理 - TCP 优先,系统 ping 仅作 fallback • reload: 添加 restart 作为 exit 的别名 • tpm: 群绑定适配 + 成功静默✅ + 失败才提示 • update: - 自动更新匹配 new commits 复数 - 群绑定适配 + 成功静默✅ + 失败才提示 🏗️ 本体更新 • 成功后提示未迁移插件与双版本目录 • ci: push 后立刻通知 TeleBoxLabs fork 同步

13 Jul 2026, 17:08 UTC206 viewsread 7 August 2026

📅 TeleBox 日报 - 2026-07-14 📊 今日提交统计 • 总提交数: 14 • TeleBox: 10 次提交 • TeleBox_Plugins: 4 次提交 🔌 插件更新 • aban: use shared @utils/htmlEscape in all runtime plugins • admin_board: use shared @utils/htmlEscape in all runtime plugins • aff: use shared @utils/htmlEscape in all runtime plugins • ai: use shared @utils/htmlEscape in all runtime plugins • aitc: use shared @utils/htmlEscape in all runtime plugins • annualreport: us

12 Jul 2026, 15:52 UTC154 viewsread 7 August 2026

📅 TeleBox 日报 - 2026-07-12 📊 今日提交统计 • 总提交数: 31 • TeleBox: 10 次提交 • TeleBox_Plugins: 21 次提交 🔌 插件更新 • aban: 移除 ban/sb 的预检查管理员权限——避免误判,由 Telegram API 实际返回错误 • audio_to_voice: audio_to_voice / eatgif / music — exec 改用 execFile 防止命令注入 • bf: 提取公共 htmlEscape 函数,修复 help.ts Api 命名空间/sure.ts mainPrefix 缺失/bf.ts 重复 import • eatgif: - eatgif.ts — 绕过头像下载超时重试链 - audio_to_voice / eatgif / music — exec 改用 execFile 防止命令注入 • fbi:

11 Jul 2026, 15:47 UTC151 views1 reactionsread 7 August 2026

📅 TeleBox 日报 - 2026-07-11 📊 今日提交统计 • 总提交数: 59 • TeleBox: 34 次提交 • TeleBox_Plugins: 25 次提交 🔌 插件更新 • aban: @utils/globalClient → @utils/runtimeManager(同步主仓库架构清理) • acron: @utils/globalClient → @utils/runtimeManager(同步主仓库架构清理) • admin_board: @utils/globalClient → @utils/runtimeManager(同步主仓库架构清理) • agent: - agent.ts 拆分为共享业务层 + 薄平台上适配层 - agent.ts 中 axios import 改用 ESM 语法 - 清理架构冗余——删除 listen.ts 死代码、移除 globalClient

🤔1

10 Jul 2026, 16:50 UTC161 viewsread 7 August 2026

📅 TeleBox 日报 - 2026-07-11 📊 今日提交统计 • 总提交数: 2 • TeleBox: 1 次提交 • TeleBox_Plugins: 1 次提交 🔌 插件更新 • agent: 用真实类型替换 :any(AIProvider/ChatMessage/ToolCall/AgentConfig 等),tsc --noEmit 归零 • fbi: Feat/fbi plugin (#251)

4 Jul 2026, 15:56 UTC300 viewsread 7 August 2026

📅 TeleBox 日报 - 2026-07-04 📊 今日提交统计 • 总提交数: 4 • TeleBox: 1 次提交 • TeleBox_Plugins: 3 次提交 🔌 插件更新 • checkin: 每天重新生成随机时间以避免连续多天使用同一时间 (#245) • fbi: Feat/fbi plugin (#248) • leech: add Leech V1 plugin - Telegram message leech with SQLite & structured logging (#90) • netease: 新增消息已读,修改消息格式 (#249) • pmcaptcha: 新增消息已读,修改消息格式 (#249)

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

Citation-graph rank

Citation-graph rank — 924,679 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 3 registered channels — 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.

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

“TeleBox Channel” (@teleboxdev), 928 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/teleboxdev.

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.