「GI」 Redland2026 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,947subscribers
+3,321 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 |
| Description | Nahida, I love you. |
| 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 | 25 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 25 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 |
|---|---|---|
| 25 Sept 2026, 17:57 | 22,947 | +562 |
| 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 | first reading |
Engagement
203 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 66 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 18.2%
- avg views ÷ 22,947 subscribers
- Avg views / post
- 4,170
- 53 posts measured
- Reaction rate
- 0.08%
- reactions ÷ views · ER floor
- Posts in window
- 53
- of 203 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 41 of 53 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 1 October 2026 |
|---|---|
| Posts held | 203 (3 August 2026 – 1 October 2026) |
| Views total | 221,070 |
| Reactions total | 152 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Oct 2026, 02:55 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
- ≈6,410
- Videos
- ≈1,390
- Links
- ≈3,000
Lifetime counters from Telegram’s own channel header, read 2 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
- Video runtime
- 1m 17s
- Average length
- 3s
Measured directly from 23 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
719 reactions across 153 posts, in 13 distinct kinds. The most used accounts for 80.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 582 | 80.9% | |
| 👍 | 36 | 5.01% | |
| 👎 | 23 | 3.20% | |
| 🤣 | 21 | 2.92% | |
| 💩 | 16 | 2.23% | |
| 😍 | 13 | 1.81% | |
| 🤯 | 12 | 1.67% | |
| 😭 | 4 | 0.556% | |
| 😱 | 4 | 0.556% | |
| 😁 | 3 | 0.417% | |
| 🗿 | 2 | 0.278% | |
| 🥰 | 2 | 0.278% | |
| 🤔 | 1 | 0.139% |
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 173 of the 203 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 719 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 203 most recent posts we hold, published 3 August 2026 to 1 October 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
source #92_official 7.2 v2 幽境危战 新增--且下一次豪饮有概率会被替换为小酌:仅积累189「豪胆值」 #幽境危战 Source @Nahida_Leak 🌸助推 Ciallo~Firefly | DM/私信 | 助手BOT | 投稿
❤1
[GI7.2v2] Teyvat world map textures Source @Nahida_Leak 🌸助推 Ciallo~Firefly | DM/私信 | 助手BOT | 投稿
❤5
「GI 7.2」 Source @Nahida_Leak 🌸助推 Ciallo~Firefly | DM/私信 | 助手BOT | 投稿
👍4❤2
「GI 7.1」 6th anniversary KV Source @Nahida_Leak 🌸助推 Ciallo~Firefly | DM/私信 | 助手BOT | 投稿
看完这期离谱周报,哪个最让你怀疑策划在用脚填数值/画饼?
- 7.3幽境危战两间怪血量3000w+(策划:这很合理,建议拿真枪打)44%
- 崩铁疑似实装付费版【额外星魂】(将军:本座终于等来售后续命了?)18%
- 至冬国不仅掏出了枪械武器,甚至连女仆装都批量进货了!9%
- 女皇居然是“薄皮大馅”自带薄护盾的0命辅助大主C29%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Nahida 周报 9.26-9.29 一、原神(Genshin Impact) ● 角色与技能机制 ○ **女皇定位与技能机制** - 具备主C能力,拥有较薄的护盾(类似白术机制)。 - 辅助方面提供0命基础区加成;对星扩散提供减抗与擢升,对星超导提供挂冰、加速叠层与擢升。 ○ **达妮卡技能与命座** - 技能提供基础区减抗、精通与护盾,Q技能可能涉及羽毛机制。 - 1命提供全队回能(适配木偶与米提亚),2命提升大攻击与爆伤。 ○ **角色ID与基础信息更新** - 7.1版本更新角色:女皇(ID: 149 / Anastasya)。 - 7.2版本新增角色:诺伊(ID: 138,男性单手剑)。 ● 版本更新与实机调整 ○ **7.3 幽境危战情报** - 洛恩复刻。 …
❤11
> 1. Paid buff exists — it is NOT "Currency War." > 2. It's already in the game files, but has not been opened for testing. > 3. The test server previously announced that paid buff would NOT be tested in v1, but will be tested during the 4.7 beta. > 4. See you after China's National Day. > 5. Even though it's called "paid buff," the enhancement materials may actually be given out for free through events. But getting …
❤1
At the same time, it remains unclear exactly what form they will take; judging by the name, I am inclined to think they will be items similar to additional Eidolons rather than Light Cones Source @Nahida_Leak 🌸助推 Ciallo~Firefly | DM/私信 | 助手BOT | 投稿
For their effect,there is the stuff in 4651 now 1. Jingyuan — One Quiet Cup of Thunder EN > DMG dealt increases by #1[i]%. When using Skill/Ultimate, additionally adds #2[i]/#3[i] Hits Per Action to "Lightning-Lord." CHS-万钧入盏,风静灯明 > 造成的伤害提高#1[i]%,施放战技/终结技时额外增加#2[i]/#3[i]段【神君】攻击段数。 2. DHIL— Moonset Stills the Deep EN > DMG dealt increases by #1[i]%. CHS- 沧溟间,月落潮平 > 造成的伤害提高#1[i]%。 3. Ac…
❤5👎4
source #jelena 7.2 v1 NPC模型渲染 Snezhnaya maid uniform Source @Nahida_Leak 🌸助推 Ciallo~Firefly | DM/私信 | 助手BOT | 投稿
❤1
[GI7.2v1] Lady Sadunova, Captain of the Domovoy Grand Duke's personal guard one of main npcs in WQ, also our enemy Source @Nahida_Leak 🌸助推 Ciallo~Firefly | DM/私信 | 助手BOT | 投稿
❤2
Showing the 12 most recent of 203 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 3 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.
看完这期离谱周报,哪个最让你怀疑策划在用脚填数值/画饼?
- 7.3幽境危战两间怪血量3000w+(策划:这很合理,建议拿真枪打)44%
- 崩铁疑似实装付费版【额外星魂】(将军:本座终于等来售后续命了?)18%
- 至冬国不仅掏出了枪械武器,甚至连女仆装都批量进货了!9%
- 女皇居然是“薄皮大馅”自带薄护盾的0命辅助大主C29%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
看完这期 7.x 版本的超级大饼,哪条爆料最让你两眼一黑又精神一振?
- 提瓦特真变射击游戏了?原神启动,扛起两把霰弹枪秒了!17%
- 派蒙竟然真是天理初影还暂离队伍?应急食品终于要单飞了!39%
- 圣遗物追加属性必选锁定!刷本坐牢四年终于熬出智能锁?16%
- 冰神自爆开启时间旅行救世……这崩坏味儿已经溢出屏幕了!28%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
看完纳西妲周报,你最想对米哈游说的一句话是?
- 戴因终于要进池了?我钱包已经准备好‘献祭’了!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 203 most recent posts we hold, published 3 August 2026 to 1 October 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 4 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.
@FireflyLeak · 15,145173 postsGenshin Leakflow
@GenshinLeakflow · 45,70499 postsSeele Leaks
@Seele_Leaks · 140,42957 postsJelena's Vault
@jelenas_vault · 8,61118 postshiragara
@hiragara_leaks · 24,0485 postsNahida
@NahidaLeak · 1882 postshoyomusicleak
@hoyomusicleak · 281 postKazusaLeaks
@KazusaLeaks · 17,4311 post
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 · 140,429
Telegram ranks this channel #10 of 56 here — alongside 55 others — read 28 August 2026
@GenshinLeakflow · 45,704
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“Nahida” (@Nahida_Leak), 22,947 subscribers as measured 25 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.