Telegram RegisterThe public register of Telegram
Telegram profile photo for Fireworks主频道

Channel

Fireworks主频道

@fire88666

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

28,757subscribers

+12,350 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-1002322060968
TypeChannel
Username@fire88666
Created10 February 2025 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live10 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/fire88666

Topic

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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@HeiXuePD/3379630 Oct 2026, 09:02 UTC@fire88666/9367 · this entry30 Oct 2026, 09:02 UTC1.00under a minute
@HeiXuePD/3381530 Oct 2026, 14:14 UTC@fire88666/9369 · this entry30 Oct 2026, 14:14 UTC1.00under a minute
@fire88666/9475 · this entry4 Nov 2026, 11:43 UTC@HeiXuePD/341584 Nov 2026, 11:43 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@HeiXuePD6 (6/6 hand-verifiable sample passed)1.0062 minutesthis entry (4–2)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 219 comparable posts for this entry, running 8 August 2026 to 11 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

16,32328,96522,64428,7577 August 202610 November 2026
65 measurements spanning 95 days, net +12,350. 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 14,427–30,861 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
10 Nov 2026, 10:4628,757-67
8 Nov 2026, 20:3728,824-85
7 Nov 2026, 12:3428,909-13
6 Nov 2026, 09:0528,922-43
5 Nov 2026, 10:3628,965+15
4 Nov 2026, 12:4928,950+29
3 Nov 2026, 16:0128,921-21
2 Nov 2026, 15:4628,942+241
1 Nov 2026, 13:2728,701+203
31 Oct 2026, 14:1728,498+92
30 Oct 2026, 12:5728,406-33
29 Oct 2026, 13:3128,439-18
28 Oct 2026, 14:0128,457+34
27 Oct 2026, 14:3628,423+25
26 Oct 2026, 17:1128,398+1
25 Oct 2026, 14:4028,397-10
24 Oct 2026, 17:4028,407+14
23 Oct 2026, 20:4628,393+17
22 Oct 2026, 21:1628,376-1
21 Oct 2026, 16:1428,377first reading

Engagement

489 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 154 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.118%
avg views ÷ 28,757 subscribers
Avg views / post
34.1
199 posts measured
Reaction rate
65.0%
reactions ÷ views · ER floor
Posts in window
199
of 489 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 12 November 2026
Posts held489 (10 February 2025 – 12 November 2026)
Views total6,779
Reactions total4,409
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 01:51 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
Videos
2
Links
7

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

Video runtime
9m 44s
Average length
32s

Measured directly from 18 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.

Reaction mix

7,343 reactions across 474 posts, in 12 distinct kinds. The most used accounts for 93.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍6,89793.9%
❤2623.57%
🤩660.899%
😍390.531%
😡220.3%
🔥200.272%
👏110.15%
🥰90.123%
🎉80.109%
🙏50.068%
😭30.041%
👌10.014%

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

Measured over the 489 most recent posts we hold, published 10 February 2025 to 12 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: 0 of 199 posts held from the last 30 days (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).

12 Nov 2026, 01:31 UTC1 views19 reactionsread 12 November 2026

此频道已经被官方盯上了.即将停止使用.点击下面蓝色字体进入新频道更新⬇️⬇️ 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道

👍19

Signed 全网收质量频道 @adggku

11 Nov 2026, 20:05 UTC22 views8 reactionsread 12 November 2026

✅频道主推荐 🔍TG最全soso资源搜索群🔍 https://t.me/addlist/szCQddiAA4MxZGI1 🥰点击链接一键加入🥰 😀😀😀😀😀

👍8

Signed TGBot Pro

11 Nov 2026, 18:43 UTC3 views19 reactionsread 12 November 2026

半夜想要看片👀找不到的各种资源群里都可以搜索的到 🔍 相关游戏外挂安装包也可以搜的到 关键词:萝莉 黑丝 御姐 少萝 白丝 老师 洛丽塔 JK 等等 ⬇️⬇️⬇️⬇️⬇️⬇️⬇️ https://t.me/sos73781 https://t.me/sos73781 https://t.me/sos73781

👍19

11 Nov 2026, 17:03 UTC17 views31 reactionsread 12 November 2026

🎮库洛米 v42.0.0 11.12最新更新内容 🤩库洛米公益雷达点我查看 更新内容如下 更新算法解密一(内置几千行高级分析算法分析,适配全部机型) 更新算法解密二 更新算法解密三 更新算法解密四 下载地址: https://drive.uc.cn/s/316265f7583f4?public=1 公益卡密: 联系机器人获取 @bbblajibot 🎮工艺暗区版本点我查看 ❗️❗️➡️点我加入官方频道 ❗️❗️➡️点我加入官方群组 库洛米承诺,不论什么设备什么账号,绝对有一个解密以上有效果!!!不会和其他辅助一样,更新七八九十个解密,一个都没效果

👍31

11 Nov 2026, 13:30 UTC1 views28 reactionsread 11 November 2026

你们好 很抱歉 我的频道被人骗走了 今天正式回归,我将在今天晚上12点更新最强公益 注:只有加入频道才能获得 我的新频道: https://t.me/+RHS1HkYv-qU4YjY1

👍28

Signed 全网收质量频道 @adggku

11 Nov 2026, 11:08 UTC12 views34 reactionsread 12 November 2026

半夜想要看片👀找不到的各种资源群里都可以搜索的到 🔍 相关游戏外挂安装包也可以搜的到 关键词:萝莉 黑丝 御姐 少萝 白丝 老师 洛丽塔 JK 等等 ⬇️⬇️⬇️⬇️⬇️⬇️⬇️ https://t.me/sos73781 https://t.me/sos73781 https://t.me/sos73781

👍34

11 Nov 2026, 08:05 UTC30 views25 reactionsread 11 November 2026

✅频道主推荐 🔍TG最全soso资源搜索群🔍 https://t.me/addlist/szCQddiAA4MxZGI1 🥰点击链接一键加入🥰 😀😀😀😀😀

👍25

Signed TGBot Pro

11 Nov 2026, 07:27 UTC37 views23 reactionsread 12 November 2026
Video

三角洲大肥鱼爬梯飞天裸奔1.3版本 更新内容 新增物资功能 新增陀螺小子 新增第三人称 优化卡屏/掉后台问题 下载地址 https://drive.uc.cn/s/316265f7583f4?public=1 公益卡密:联系机器人获取 @bbblajibot 请加入下面官方频道后使用 @BIGFATFISH6 @BIGFATFISH6 本频道所有文件皆由ChatGPT制作,仅供个人学习研究;使用者的任何行为与应用作者无关,请在下载后24小时内删除,下载即代表同意本协议,若有侵权违法行为请联系我删除内容

👍23

11 Nov 2026, 05:45 UTC35 views26 reactionsread 12 November 2026
Video

旋转小陀螺+第三人称+飞天🎉🎉 都可以裸奔哦 安装包频道内获取 公益卡密联系机器人 @bbblajibot https://t.me/BIGFATFISH6 https://t.me/BIGFATFISH6

👍26

11 Nov 2026, 03:05 UTC46 views19 reactionsread 12 November 2026
File

大肥鱼飞天更新1.2版本 飞天如果只上下爬梯那就加大一下爬梯速度就行了 使用方法直接执行即可无需驱动 下个版本更新增加第三人称 可以搭配其他辅助使用 不吃举报即可 更新:注入裸奔(切勿吃举报) 如若和谐后请不要再使用 公益卡密: 联系机器人获取大肥鱼卡密 @bbblajibot 官方频道 @BIGFATFISH6 官方频道 @BIGFATFISH6 频道记得关注一下😡 😙温馨提示小号娱乐即可可搭配别的辅助一起使用

👍19

11 Nov 2026, 01:28 UTC2 views17 reactionsread 11 November 2026

此频道已经被官方盯上了.即将停止使用.点击下面蓝色字体进入新频道更新⬇️⬇️ 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道

👍17

Signed 全网收质量频道 @adggku

11 Nov 2026, 00:46 UTC28 views11 reactionsread 11 November 2026
File

大肥鱼2.3三角洲公益算法解密 已适配三角洲新赛季 大肥鱼飞天裸奔爬楼点我获取 11.11最新更新解密 更新日志 适配三角洲最新加密 更新解密 优化漏人问题 ✈️大肥鱼新手/老手不会使用的点我查看视频和文字教程 公益卡密: 联系机器人获取 @bbblajibot ❗️❗️➡️ @BIGFATFISH6 ❗️❗️➡️ @dfy998

👍11

Showing the 12 most recent of 489 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.

Posts recorded as deleted after publishing

We recorded 4 posts on @fire88666 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
8 August 2026
Most recent seen missing
19 August 2026
Median time before seen missing
19 hours
Seen missing in the last 30 days
0

Forward network

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.

Mentions

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.

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

“Fireworks主频道” (@fire88666), 28,757 subscribers as measured 10 November 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.