#Special@GenshinLeakflow 7.2 v2 米提亚 配队演示 米提亚 八重神子 奥黛塔 砂糖 全C0 #米提亚
🤣56❤14👎14👍4😭3🥰1😡1
Signed Camgfy

Channel
@GenshinLeakflow
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
45,704subscribers
+4,380 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001723628120 |
|---|---|
| Type | Channel |
| Username | @GenshinLeakflow |
| Description | 讨论群组 Chat https://t.me/+G-xVGAu-6YRlZGI1 不接广告 Not accepting ads |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 30 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 30 September 2026 |
| On Telegram | t.me/GenshinLeakflow |
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 9 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Sept 2026, 02:18 | 45,704 | +1,369 |
| 18 Sept 2026, 00:18 | 44,335 | +77 |
| 15 Sept 2026, 23:40 | 44,258 | +86 |
| 14 Sept 2026, 05:00 | 44,172 | +52 |
| 12 Sept 2026, 15:20 | 44,120 | +126 |
| 10 Sept 2026, 11:39 | 43,994 | +269 |
| 7 Sept 2026, 04:38 | 43,725 | +95 |
| 4 Sept 2026, 13:56 | 43,630 | +79 |
| 3 Sept 2026, 04:17 | 43,551 | +66 |
| 1 Sept 2026, 22:17 | 43,485 | +61 |
| 31 Aug 2026, 20:14 | 43,424 | +62 |
| 30 Aug 2026, 22:05 | 43,362 | +44 |
| 29 Aug 2026, 23:44 | 43,318 | +118 |
| 29 Aug 2026, 02:33 | 43,200 | +69 |
| 28 Aug 2026, 03:37 | 43,131 | +51 |
| 27 Aug 2026, 06:08 | 43,080 | +165 |
| 26 Aug 2026, 06:57 | 42,915 | +104 |
| 25 Aug 2026, 03:43 | 42,811 | +82 |
| 23 Aug 2026, 23:42 | 42,729 | +120 |
| 22 Aug 2026, 04:46 | 42,609 | first reading |
253 posts held, back to 30 July 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 108 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 2 October 2026 |
|---|---|
| Posts held | 253 (30 July 2026 – 2 October 2026) |
| Views total | 1,814,110 |
| Reactions total | 11,696 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Oct 2026, 11:39 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 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.
Measured directly from 30 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.
23,502 reactions across 251 posts, in 57 distinct kinds. The most used accounts for 28.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6,583 | 28.0% | |
| 👎 | 5,341 | 22.7% | |
| 👍 | 1,772 | 7.54% | |
| 🤣 | 1,664 | 7.08% | |
| 😱 | 1,317 | 5.60% | |
| 🤔 | 797 | 3.39% | |
| 🤬 | 769 | 3.27% | |
| 😭 | 716 | 3.05% | |
| 🥰 | 589 | 2.51% | |
| 🤯 | 474 | 2.02% | |
| 😨 | 429 | 1.83% | |
| 🤩 | 389 | 1.66% | |
| 😁 | 335 | 1.43% | |
| 🔥 | 321 | 1.37% | |
| 🎉 | 256 | 1.09% | |
| 🤪 | 252 | 1.07% | |
| 😍 | 237 | 1.01% | |
| 🌭 | 121 | 0.515% | |
| 👏 | 106 | 0.451% | |
| 🤨 | 98 | 0.417% | |
| 37 further kinds | 936 | 3.98% |
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 252 of the 253 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 23,502 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 253 most recent posts we hold, published 30 July 2026 to 2 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.
#Special@GenshinLeakflow 7.2 v2 米提亚 配队演示 米提亚 八重神子 奥黛塔 砂糖 全C0 #米提亚
🤣56❤14👎14👍4😭3🥰1😡1
Signed Camgfy
source #Shirai_Kurokochan #sus 未来可能实装的角色身份 既然我的爆料你们很多人不喜欢那我也准备离开了 以后再没人会编出若娜瓦会死这种假消息骗你们了 作为饯别的礼物留些未来会实装的角色好赖自知吧 来自黄金城时代存在至今的诺伊 来自古璃月诸仙众之一的女仙人 来自烬海涅槃的渡过烈火的贤人 来自璃月的新文殊四星璃月棋圣 来自仙女座星云帝国的嫡次公主 来自圣徒所属的初民文明的K · K 神明视线死角睡觉的戴因斯雷布 上非实装顺序想看更多后续角色 详见之前发过的若娜瓦相关文章 EN
🤣156👎27😱16😢8😭7❤2🤪2😁2
Signed 御坂妹
1 / 2 / 3 #UncleNiceCock #jelena 7.2 v2 魔神任务第六幕相关 图一:天空岛之下的附近位置(赤望台)有一个任务标记,在完成此任务后,可获取最后一个冰主的命座。 图三:与其交互会进入到神座秘境。 Act VI has an Archon Quest marker under Celestia's proximity + last Constellation obtained via this quest Interacting with this, it takes you to the DivineThrone domain This is GodGate #剧情 #地图
❤79👎5👍4🤔4🤩4🆒2🎉1👏1
Signed Camgfy
source #jelena 7.2 v1 一些可能与场景相关的游戏资源 提瓦特世界地图纹理 Indoor_Zd_Prop_Dg_Zhihuishi_01_Diffuse.png raw [GI7.2v1] Teyvat world map textures #地图
❤29🤔6👍3👎1👏1😱1
Signed Camgfy
source #92_official 7.2 v2 幽境危战 新增--且下一次豪饮有概率会被替换为小酌:仅积累189「豪胆值」 #幽境危战
👍37❤15👎5👏4🤬3
Signed Camgfy
1 / 2 / 3 #jelena #Seele_Leaks 7.2 v1 剧情NPC模型渲染 萨杜诺娃,矮灵大公的亲卫队长 世界任务中的主要npc之一,同时也是我们的敌人 Lady Sadunova, Captain of the Domovoy Grand Duke's personal guard one of main npcs in WQ, also our enemy 确认官方译名后的补发 世界任务npc -- 斯露德,矮灵大公阿尔维斯的女儿 [GI7.2v1] WQ npc — Thrud, daughter of the Grand Duke of the Domovoy, Alvis #剧情
❤99👎10🤣4👍3⚡1🤬1
Signed Camgfy
source #jelena 7.2 v1 NPC模型渲染 Snezhnaya maid uniform
❤61🤩9👎7🤬2👍1💊1
Signed Camgfy
source #KazusaLeaks 7.2 v2 瓦列里新版特效演示 GI 7.2 - V2 Valeriy SFX Changes Mitya still has no SFX #瓦列里
😁40👏9❤8👎3💔3💋2🤬2👍1
Signed Camgfy
#GachaBase 7.2 v2 角色与武器改动 角色改动 - 米提亚 - 瓦列里 武器改动 - 秘星典谕 改动细节 #米提亚 #瓦列里 #武器
👎65🤣25❤18🎉13😭9🤓4👍3🤔3
Signed Camgfy
1 / 2 #UncleNiceCock #Sakiko_Leaks 新角色ID补发 7.2v1 138 -- 诺伊 成男 单手剑 7.1pre 149 -- 安娜丝塔夏 (女皇) [ GI - 7.1.50 ] New IDs: 138 - Noy, Male Sword AvatarID 10000149: Anastasya
❤78👍13😱11👎8🥰2😢2🆒2
Signed Camgfy
source #KazusaLeaks 7.2 v1 TPS新增武器演示 GI 7.2 - New guns demonstration #TPS
👎106👍63❤14👏2🤣2🥰2❤🔥1💊1
Signed Camgfy
source #wwwhatever 7.3幽境危战相关情报 堕天 复刻洛恩 7.3幽境危战会大膨胀,猜测可能有两间血量3000w+的星体系四级怪 #幽境危战
👎195🤣41❤16😱12😁10🤯4👏3🤪3
Signed ノリ
Showing the 12 most recent of 253 posts we hold for @GenshinLeakflow. 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.
@GenshinLeakflow edited 18 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 28 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 9 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 30 September 2026 — this entry's latest reading, not the date you are reading this.
“Genshin Leakflow” (@GenshinLeakflow), 45,704 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/GenshinLeakflow.
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.