source #Seele_Leaks 星锋剑幻化效果演示 #武器 Source @Nahida_Leak 🌸助推 Ciallo~Firefly | DM/私信 | 助手BOT | 投稿

Channel
Nahida
@Nahida_Leak
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Telegram's recommendations · Cite this entry
22,385subscribers
+2,759 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 | -1001944394067 |
|---|---|
| Type | Channel |
| Username | @Nahida_Leak |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/Nahida_Leak |
Topic
Gaming — 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 100% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 03:16 | 22,385 | +98 |
| 16 Sept 2026, 19:58 | 22,287 | +96 |
| 14 Sept 2026, 19:37 | 22,191 | +80 |
| 13 Sept 2026, 07:16 | 22,111 | +49 |
| 11 Sept 2026, 06:55 | 22,062 | +172 |
| 8 Sept 2026, 09:56 | 21,890 | +170 |
| 5 Sept 2026, 04:39 | 21,720 | +76 |
| 3 Sept 2026, 10:56 | 21,644 | +55 |
| 2 Sept 2026, 02:44 | 21,589 | +22 |
| 1 Sept 2026, 04:48 | 21,567 | +59 |
| 31 Aug 2026, 04:28 | 21,508 | +58 |
| 30 Aug 2026, 04:34 | 21,450 | +70 |
| 29 Aug 2026, 06:27 | 21,380 | +65 |
| 28 Aug 2026, 04:06 | 21,315 | +70 |
| 27 Aug 2026, 03:32 | 21,245 | +79 |
| 26 Aug 2026, 07:02 | 21,166 | +55 |
| 25 Aug 2026, 08:38 | 21,111 | +81 |
| 24 Aug 2026, 07:16 | 21,030 | +150 |
| 22 Aug 2026, 14:57 | 20,880 | +71 |
| 21 Aug 2026, 08:54 | 20,809 | first reading |
Engagement
162 posts held, back to 3 August 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 56 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 17.3%
- avg views ÷ 22,385 subscribers
- Avg views / post
- 3,870
- 65 posts measured
- Reaction rate
- 0.095%
- reactions ÷ views · ER floor
- Posts in window
- 65
- of 162 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 54 of 65 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 162 (3 August 2026 – 3 September 2026) |
| Views total | 251,540 |
| Reactions total | 216 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 13:38 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
- 1m 14s
- Average length
- 4s
Measured directly from 17 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
570 reactions across 121 posts, in 11 distinct kinds. The most used accounts for 81.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 465 | 81.6% | |
| 👍 | 26 | 4.56% | |
| 🤣 | 21 | 3.68% | |
| 👎 | 15 | 2.63% | |
| 😍 | 13 | 2.28% | |
| 🤯 | 12 | 2.11% | |
| 💩 | 8 | 1.40% | |
| 😭 | 4 | 0.702% | |
| 🗿 | 2 | 0.351% | |
| 😁 | 2 | 0.351% | |
| 🥰 | 2 | 0.351% |
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 137 of the 162 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 570 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 162 most recent posts we hold, published 3 August 2026 to 3 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
Posted without readable text
#GachaBase 7.1 v5 角色与武器改动 角色文本改动 - 奥黛塔 被动 回响中的冬梦 在小地图上显示周围的至冬区域特产的位置,在影域中亦能提供相同的佑助。 - 阿罗夏 被动 树梢察伺 在小地图上显示周围的至冬区域特产的位置,在影域中亦能提供相同的佑助。 - 沃雅妮莎 元素战技 宣叙·晨声纷流 受到上述两种伤害的敌人的上述两种攻击命中时将会使敌人的水水元素抗性与冰元素抗性降低。 6命 永不落幕的盛歌 「穿彻风雪的余响」的效果获得强化:「黑与白的双音」改为对附近队伍中的所有角色生效。的效果获得强化:「黑与白的双音」改为对队伍中附近的所有角色生效。 武器文本改动 - 凝雪沉心 造成的星烁反应伤害提升6% #沃雅妮莎 #武器 Source @Nahida_Leak 🌸助推 Ciallo~Firefly | DM/私信 | 助手BOT | 投稿
Posted without readable text
「GI 7.1」 Source @Nahida_Leak 🌸助推 Ciallo~Firefly | DM/私信 | 助手BOT | 投稿
「GI 7.1」 Source @Nahida_Leak 🌸助推 Ciallo~Firefly | DM/私信 | 助手BOT | 投稿
👍1
source #Seele_Leaks 皮耶罗技能演示 #剧情 Source @Nahida_Leak 🌸助推 Ciallo~Firefly | DM/私信 | 助手BOT | 投稿
对上了:上一条 King Lesnik 说的 Lord of Leshy,多半就藏在这批新武器故事里——《新枝》(Neuer Zweig) 光名字就很“森林之主”,凝雪沉心待验证。 另一个细节:漩流婉歌这版把旧文本结尾的「海才是驃歌曲的家鄉」改成了「花嫁」。从家乡改成新娘,措辞党可以开工了。
source #gen 7.1 v5 新增武器故事文本 - 凝雪沉心 - 新枝 Source @Nahida_Leak 🌸助推 Ciallo~Firefly | DM/私信 | 助手BOT | 投稿
[GI7.1v5] Lord of Leshy — King Lesnik from weapon story Source @Nahida_Leak 🌸助推 Ciallo~Firefly | DM/私信 | 助手BOT | 投稿
❤1
Posted without readable text
今晚GIv5更新。沃会赢吗? Source @Nahida_Leak 🌸助推 Ciallo~Firefly | DM/私信 | 助手BOT | 投稿
❤1
Showing the 12 most recent of 162 posts we hold for @Nahida_Leak. 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.
看完纳西妲周报,你最想对米哈游说的一句话是?
- 戴因终于要进池了?我钱包已经准备好‘献祭’了!27%
- 至冬是最后一站?那枫丹、纳塔的坑还没填完呢!25%
- 若娜瓦到底死没死?编剧你过来,我保证不打死你!40%
- 星扩散能跳高高?这怕不是原神版‘起飞’系统!8%
Shares as published. 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 162 most recent posts we hold, published 3 August 2026 to 3 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.
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.
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.
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.
@Seele_Leaks · 139,342
Telegram ranks this channel #10 of 56 here — alongside 55 others — read 28 August 2026
@GenshinLeakflow · 44,335
Telegram ranks this channel #10 of 51 here — alongside 50 others — read 28 August 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Nahida” (@Nahida_Leak), 22,385 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Nahida_Leak.
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.