庆祝频道人数27K 给大家发一个红包
👍1

Channel
@fire88666
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
27,668subscribers
+11,261 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002322060968 |
|---|---|
| Type | Channel |
| Username | @fire88666 |
| Created | 10 February 2025 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/fire88666 |
Marketing & affiliate — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 18:20 | 27,668 | +475 |
| 19 Sept 2026, 15:41 | 27,193 | +309 |
| 17 Sept 2026, 04:21 | 26,884 | +291 |
| 15 Sept 2026, 03:58 | 26,593 | +316 |
| 13 Sept 2026, 11:02 | 26,277 | +267 |
| 11 Sept 2026, 11:22 | 26,010 | +462 |
| 8 Sept 2026, 15:57 | 25,548 | +841 |
| 5 Sept 2026, 06:16 | 24,707 | +404 |
| 3 Sept 2026, 09:07 | 24,303 | +220 |
| 2 Sept 2026, 01:26 | 24,083 | +218 |
| 1 Sept 2026, 04:29 | 23,865 | +170 |
| 31 Aug 2026, 07:53 | 23,695 | +332 |
| 30 Aug 2026, 07:26 | 23,363 | +280 |
| 29 Aug 2026, 05:28 | 23,083 | +185 |
| 28 Aug 2026, 03:43 | 22,898 | +107 |
| 27 Aug 2026, 02:43 | 22,791 | +139 |
| 26 Aug 2026, 02:12 | 22,652 | +87 |
| 25 Aug 2026, 04:29 | 22,565 | +91 |
| 24 Aug 2026, 04:15 | 22,474 | +395 |
| 22 Aug 2026, 11:33 | 22,079 | first reading |
202 posts held, back to 10 February 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 67 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 27 September 2026 |
|---|---|
| Posts held | 202 (10 February 2025 – 27 September 2026) |
| Views total | 9,816 |
| Reactions total | 450 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 20:17 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.
Lifetime counters from Telegram’s own channel header, read 27 September 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.
Measured directly from 13 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
1,642 reactions across 190 posts, in 11 distinct kinds. The most used accounts for 79.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,305 | 79.5% | |
| ❤ | 182 | 11.1% | |
| 🤩 | 66 | 4.02% | |
| 😍 | 23 | 1.40% | |
| 😡 | 21 | 1.28% | |
| 👏 | 11 | 0.67% | |
| 🔥 | 9 | 0.548% | |
| 🥰 | 9 | 0.548% | |
| 🎉 | 8 | 0.487% | |
| 🙏 | 5 | 0.305% | |
| 😭 | 3 | 0.183% |
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 190 of the 202 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 1,642 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 202 most recent posts we hold, published 10 February 2025 to 27 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.
庆祝频道人数27K 给大家发一个红包
👍1
💰 转账给你 23.89 U 请在24小时内领取
👍1
对了,很多人找不到我,这个是正常的,我基本上不上线,我上线了,基本上也是要更新的时候,有新功能,有新的解密,我要更新的时候上线一下,或者是我要找东西的时候上线一下,其他时候基本不上线,不上线的原因是我每次上线都很麻烦,VPN很慢,受不了一点🙃🙃🙃
👍20
不要问我能不能用,要自己测试,你问我,那我只能给你说不知道,不要问我,我啥也不知道
👍20
Fireworks公益 功能: 绘制+物资+无模块陀螺仪自瞄+漏打自瞄随意裸奔+掩体变色 没更新啥东西就更新了两个子追,一个视角子追,一个断点子追,断点子追好不好追10年自己测试反正我能做的都做了,我自己测试,不会追10年,那个解密里面的那个解密不确定和没和谐,还更新了一下帧率问题,现在是能多高就多高,能120就120,能144就144 还有绘制那些反正大概的都有,文案不知道怎么写,随便写的 还有啥要的可以找 ➡️ @sj0127 🌟🙃🌟➡️ @fire88666
👍21
❤️库洛米三角洲 V30.0.0 更新内容: 以拷打三角洲千人千面加密,适配最新版本加密 1.新增算法解密 a3 接口(偶尔偏框,但一定时间校正) 2.新增算法解密 a4 接口(仅支持驱动一和 TWT 驱动) 3.新增漏人刷新按钮☑️ 4.新增天玑脱框问题修复按钮 5.修复部分物资不显示问题 6.修复部分设备不能刷驱动问题 7.所有解密接口以及无解密下适配大小地图雷达和辅助投影 8.修复若干问题和 bug 9.优化驱动和 app 可提升稳定性 A1 接口和 A2 接口在内测中,不久也会同步更新 如遇到 A3 接口、A4 接口的问题,以及发现漏物资,请点击悬浮窗上面的诊断日志,在文件管理器找到/data/local/tmp/kuromi_interface_diagnostic.txt,发给 @xiaoluo004 发文件说具体问题以及内核版本,不然不会回 公益解密卡密:@kuluomi886 (进频道才能使用)
👍7
✔️绿色暴利稳赚撸口子1000~5000 项目优势:纯绿色,无风险,不用押金! ✅此项目新人都是包赚 😀最稳项目 🟢每天🉑1️⃣0️⃣0️⃣0️⃣~5️⃣0️⃣0️⃣0️⃣ 🟢不违法 不按头 不擦边❗️ 🟢最稳项目 有手就行 ✅ 🟢先赚钱后分钱👍 👍 👍😀 🔴想挣钱进群看教程⬇️⬇️ https://t.me/+S46CyXoEyF5iYWU1 不会做的联系: @saimin 双向私信不了的联系 @xxjdjqrbot 也可以看群置顶🔝详细教程
👍6
⭐️ 恭喜您获得红包资格 ⭐️ 💸已发放 ¥81,652 🔺今日剩余 168 份 ⚙️最新领取 用户***王杰 领取488.66 RMB🪙 用户***李婷 领取358.80 RMB🪙 用户***陈豪 领取999.66 RMB🪙 ⏰红包30分钟后失效💤
👍6
File, posted without a caption
👍19😡9🥰4👏2
Fireworks公益测试新赛季 功能: 绘制+物资+无模块陀螺仪自瞄+漏打自瞄随意裸奔+掩体变色 掩体漏打,暂时没更新好,后面更新 还有绘制那些反正大概的都有,文案不知道怎么写,随便写的 还有啥要的可以找 ➡️ @sj0127 有问题说清楚直接说不经常在线 问题说明白,说完整,后面可能更新子弹追踪,网页雷达,找的人多就加,没人用就不加了 哦,对了,忘了说了,那个自瞄是根据智能判断的狙击枪,它自动切换开镜自瞄,除了M14,也是漏打哦,漏手打手,有问题请给我反馈 🌟🙃🌟➡️ @fire88666
👍34❤16
没有风险🎆非黑灰产💝绿色项目 合法合规,只需要一个手机!✨ 不打电话,只发短信,不封卡 无任何风险,无需本金,无需押金,合法合规 发财链接 https://t.me/u321o 赚钱联系 @paidaxingnb 无发私信就私信 @paidaxingsxbot
👍10
没有风险🎆非黑灰产💝绿色项目 合法合规,只需要一个手机!✨ 不打电话,只发短信,不封卡 无任何风险,无需本金,无需押金,合法合规 发财链接 https://t.me/u321o 赚钱联系 @paidaxingnb 无发私信就私信 @paidaxingsxbot
👍4
Showing the 12 most recent of 202 posts we hold for @fire88666. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“Fireworks主频道” (@fire88666), 27,668 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/fire88666.
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.