Telegram RegisterThe public register of Telegram
Telegram profile photo for Firefly

Channel

Firefly

@FireflyLeak

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Telegram's recommendations · Cite this entry

14,621subscribers

+512 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-1002039687763
TypeChannel
Username@FireflyLeak
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live2 September 2026
Measurements held26
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/FireflyLeak

Growth

14,10914,62114,3657 August 2026 — 14,109 subscribers7 August 2026 — 14,109 subscribers8 August 2026 — 14,116 subscribers9 August 2026 — 14,137 subscribers10 August 2026 — 14,148 subscribers11 August 2026 — 14,193 subscribers12 August 2026 — 14,224 subscribers13 August 2026 — 14,228 subscribers14 August 2026 — 14,250 subscribers16 August 2026 — 14,259 subscribers17 August 2026 — 14,260 subscribers18 August 2026 — 14,287 subscribers19 August 2026 — 14,298 subscribers20 August 2026 — 14,311 subscribers21 August 2026 — 14,328 subscribers23 August 2026 — 14,345 subscribers25 August 2026 — 14,391 subscribers25 August 2026 — 14,408 subscribers27 August 2026 — 14,468 subscribers27 August 2026 — 14,517 subscribers28 August 2026 — 14,543 subscribers29 August 2026 — 14,575 subscribers30 August 2026 — 14,589 subscribers31 August 2026 — 14,603 subscribers1 September 2026 — 14,620 subscribers2 September 2026 — 14,621 subscribers7 August 20262 September 2026
26 measurements spanning 26 days, net +512. 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,032–14,698 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
2 Sept 2026, 19:4614,621+1
1 Sept 2026, 17:1314,620+17
31 Aug 2026, 19:0914,603+14
30 Aug 2026, 22:1414,589+14
29 Aug 2026, 21:2514,575+32
28 Aug 2026, 21:4514,543+26
27 Aug 2026, 22:1414,517+49
27 Aug 2026, 01:1214,468+60
25 Aug 2026, 21:5614,408+17
25 Aug 2026, 00:2914,391+46
23 Aug 2026, 11:3714,345+17
21 Aug 2026, 20:0614,328+17
20 Aug 2026, 13:1614,311+13
19 Aug 2026, 13:3614,298+11
18 Aug 2026, 17:1214,287+27
17 Aug 2026, 14:3714,260+1
16 Aug 2026, 07:5614,259+9
14 Aug 2026, 18:3414,250+22
13 Aug 2026, 07:3414,228+4
12 Aug 2026, 09:2714,224first reading

Engagement

163 posts held, back to 4 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 50 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
16.9%
avg views ÷ 14,621 subscribers
Avg views / post
2,470
149 posts measured
Reaction rate
0.763%
reactions ÷ views · ER floor
Posts in window
153
of 163 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 100 of 149 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 2 September 2026
Posts held163 (4 August 20262 September 2026)
Views total367,346
Reactions total1,922
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 18:27 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

Video runtime
2m 55s
Average length
44s

Measured directly from 4 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

1,999 reactions across 101 posts, in 18 distinct kinds. The most used accounts for 79.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💩1,59079.5%
custom 51589817351777823251045.20%
884.40%
🤣643.20%
👍442.20%
🤨221.10%
👎211.05%
😱211.05%
🤮160.8%
😁120.6%
🙏30.15%
🤔30.15%
🎉20.1%
👀20.1%
😡20.1%
😢20.1%
🥱20.1%
😍10.05%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.

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

Measured over the 163 most recent posts we hold, published 4 August 2026 to 2 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.

Recent posts

2 Sept 2026, 12:54 UTC932 viewsread 2 September 2026

「HSR Joke」 最新一期忘却之庭里,米哈游直接将 1–4 层的敌人原样复制到 6–9 层,敌人生命值和等级完全没有改动(大家现在进游戏就能验证)。如此一来,前九层中第 5 层的敌人血量反而是最高的。这个明显的漏洞直到几天前才被发现。这是否说明《崩坏:星穹铁道》已经吸引不到新玩家了? In the latest Memory of Chaos, HoYoverse copied the enemies from Floors 1–4 straight to Floors 6–9 without changing their HP or levels at all (you can verify this in‑game right now). As a result, Floor 5 has the highest HP values among the first nine floors. This glaring mi

Signed Cherry

1 Sept 2026, 16:01 UTC≈1,840 views14 reactionsread 2 September 2026

Firefly 周报 9.1-9.1 一、崩坏:星穹铁道情报汇总 ● 4.7版本前瞻 ○ 欢愉主加强机制 - 新增能力:4.7主线后,每释放两次“啊哈时刻”获得一层强化战技(最多两层)。 - 技能效果:释放强化战技提升自身5%充能效率(1回合)并获得35点【好活当赏】。 - 角色协同:若虚照在场,施放强化战技后虚照立即获得计入40笑点的欢愉技。 ○ 4.7卡池角色 - 包含角色:虚照、朽叶。 ● 角色技能组情报 ○ 朽叶 档案详情 - 属性:火·欢愉。 - 机制概况:普攻造成火伤;战技加暴击率并获得“笑点”;终结技/天赋围绕“花朵”机制,通过攻击累计伤害并在等级达标时引爆。 - 备注:当前开发版本较简陋,尚未添加完整欢愉技能。 ○ Xueyi Flush 档案详情

💩14

Signed Ciallo~Sakura

1 Sept 2026, 16:01 UTCviews —

Firefly pinned «Firefly 周报 9.1-9.1 一、崩坏:星穹铁道情报汇总 ● 4.7版本前瞻 ○ 欢愉主加强机制 - 新增能力:4.7主线后,每释放两次“啊哈时刻”获得一层强化战技(最多两层)。 - 技能效果:释放强化战技提升自身5%充能效率(1回合)并获得35点【好活当赏】。 - 角色协同:若虚照在场,施放强化战技后虚照立即获得计入40笑点的欢愉技。 ○ 4.7卡池角色 - 包含角色:虚照、朽叶。 ● 角色技能组情报 ○…»

1 Sept 2026, 14:15 UTC≈1,910 views2 reactionsread 2 September 2026

「HSR 4.6」 血脑屏障&真实伤害机制解析: 屏障会阻止追踪型真实伤害效果记录自身受到的伤害,但不会阻止真实伤害生效。 真实伤害机制需要预先储存伤害记录,之后再结算百分比伤害;直接击打屏障产生的伤害无法存入该记录。 昔涟与 RMC 的真实伤害对屏障完全无效。 特莉比以及斐恩 6 命的真实伤害会在普通敌人身上完成命中记录,并可能将效果转移至屏障,因此可以正常起效。 知更鸟・夏沫蕾托 1 命无法在屏障上登记伤害,但其真实伤害依旧能够生效。 Blood‑Brain Barrier & true damage breakdown: The barrier stops damage taken by itself from being logged by track‑based true‑damage effects, without blocking true damage application. Some true damag

💩2

Signed Cherry

1 Sept 2026, 12:50 UTC≈1,820 views10 reactionsread 2 September 2026

「HSR 4.6」 新 Boss 机制:血脑屏障。对所有非欢愉伤害获得 75% 减伤。网传的80或者85或者88或者90都是错的。 New boss mechanic: Blood‑Brain Barrier. 75% damage reduction against all non‑Elation damage. The rumored values of 80, 85, 88 and 90 are all incorrect. Source @FireflyLeak 🌸助推 Ciallo~Nahida | DM/私信 | 助手BOT | 投稿

💩6👎3😱1

Signed Cherry

1 Sept 2026, 12:32 UTC≈1,710 views10 reactionsread 2 September 2026

4.7卡池泄密 虚照 朽叶 —— 投稿者: @hsr_sparxielover

💩10

Signed Ciallo~Sakura

1 Sept 2026, 12:32 UTC≈1,830 views20 reactionsread 2 September 2026

4.7卡池泄密 虚照 朽叶 —— 投稿者: @hsr_sparxielover

💩20

Signed Ciallo~Sakura

1 Sept 2026, 12:32 UTC≈1,690 views10 reactionsread 2 September 2026

朽叶技能泄密 [HSR] 角色技能组 接下来的这段时间,我们发布的任何技能组都是为了保存/记录目的。任何备注都会根据需要附在角色上。 Kuchiba | 火属性·欢愉 注意:该角色相比其他角色显得更加基础,甚至尚未添加欢愉技能。 普攻 对指定敌方单体造成等同于Kuchiba攻击力X%的火属性伤害。 战技 对指定敌方单体造成等同于Kuchiba攻击力X%的火属性伤害,然后使全体友方的暴击率提高X%,持续X回合。获得X层“笑点”。 终结技 对指定敌方单体施加“花朵”,持续X回合;若其已有“花朵”,则使该“花朵”等级提升1级。 造成等同于Kuchiba攻击力X%的火属性伤害,然后若“花朵”等级达到3级或以上,立即触发一次天赋的引爆效果。此次引爆不会重置“花朵”等级或计数。 天赋 战斗开始时,在生命值最高的敌方目标身上种下“花朵”,持续X回合。 当敌方目标带有“花朵”时:每当任意友方攻击该目标,该友方恢复等同于造成伤害X

💩10

Signed Ciallo~Sakura

1 Sept 2026, 12:27 UTC≈1,560 views12 reactionsread 2 September 2026

fate第三期联动情报爆料 在2027夏季崩铁:星穹铁道将联动fate衍生系列动画魔法少女★伊莉雅,联动角色为伊莉雅和美游,且两人有特殊的羁绊连携技动画,两位新角色将不会赠送,往期的红a与吉尔伽美什将会再次进行二选一赠送活动 —— 投稿者: @yunyun_mutuallove_Q

💩12

Signed Ciallo~Sakura

1 Sept 2026, 12:27 UTC≈1,490 views15 reactionsread 2 September 2026

4.7欢愉主加强泄密 4.7主线后欢愉主将获得额外能力 【HSR】 注意: 该角色目前仍处于开发阶段,以下内容很可能会发生改动。 4.7主线过后欢愉主将获得额外能力:每当我方释放两次啊哈时刻,欢愉主将获得一次强化战技(最多持有两层),使自身充能效率提高5%一回合,释放战技获得35点【好活当赏】。 若虚照在场,开拓者·欢愉施放强化战技后,虚照立即获得一个计入40笑点的欢愉技。 —— 投稿者: @hsr_sparxielover

💩15

Signed Ciallo~Sakura

1 Sept 2026, 12:27 UTC≈1,520 views9 reactionsread 2 September 2026

4.7欢愉主加强泄密 4.7主线后欢愉主将获得额外能力 【HSR】 注意: 该角色目前仍处于开发阶段,以下内容很可能会发生改动。 4.7主线过后欢愉主将获得额外能力:每当我方释放两次啊哈时刻,欢愉主将获得一次强化战技(最多持有两层),使自身充能效率提高5%一回合,释放战技获得35点【好活当赏】。 若虚照在场,开拓者·欢愉施放强化战技后,虚照立即获得一个计入40笑点的欢愉技。 —— 投稿者: @hsr_sparxielover

💩9

Signed Ciallo~Sakura

1 Sept 2026, 12:16 UTC≈1,470 viewsread 2 September 2026

[HSR] Character Kit For the next little while any kits posted by us are being posted for preservation/record keeping purposes. Any notes will be attached to the characters as we deem necessary. Kuchiba | Fire Elation Note: This Character seems much more barebones compared to others, with no Elation Skill even being added yet Basic Deals Fire DMG equal to X% of Kuchiba's ATK to one designated enemy. Skill Deals F

Signed Cherry

Showing the 12 most recent of 163 posts we hold for @FireflyLeak. 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 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

4 Aug 2026, 16:00 UTCAnonymous Poll130 voters

看完这期《Firefly周报》,你的第一反应是?

  1. 周年庆主推竟不是卡芙卡SP?策划你睡得着吗?反正我睡不着!48%
  2. 本土角色不配当周年主推?懂了,这就去给米哈游寄刀片(不是)30%
  3. GLM又双叒叕429?五个小时限额,Firefly的AI怕不是被榨干了11%
  4. 重置时间2026年?好家伙,这周报怕不是从未来穿越回来的12%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

4 Aug 2026, 08:48 UTCAnonymous Poll153 voters

周报信息量爆炸,你最想穿越到哪个版本去搞事情?

  1. 4.6金灵商店:翡翠+灵砂上架,钱包你准备好了吗?16%
  2. 5.2元帅华卡池:周年庆主推,这不得抽爆?24%
  3. 4.5复刻:阿格莱雅和不死途来了,但风堇鸽了,策划你没有心!9%
  4. 5.x SP角色:星期日、瓦尔特、流萤、卡夫卡、希儿——等等,希儿你怎么混进来的?52%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is 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 163 most recent posts we hold, published 4 August 2026 to 2 September 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.

Forward network

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.

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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Genshin Leakflow
@GenshinLeakflow · 43,551
Telegram ranks this channel #16 of 51 here — alongside 50 others — read 28 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Firefly” (@FireflyLeak), 14,621 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/FireflyLeak.

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.