Telegram RegisterThe public register of Telegram
Telegram profile photo for Genshin Leakflow

Channel

Genshin Leakflow

@GenshinLeakflow

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

50,200subscribers

+8,876 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001723628120
TypeChannel
Username@GenshinLeakflow
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/GenshinLeakflow

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 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 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 3 other registered channels. 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@GenshinLeakflow/19489 · this entry21 Oct 2026, 16:47 UTC@Seele_Leaks/3808421 Oct 2026, 16:47 UTC1.00under a minute
@GenshinLeakflow/19503 · this entry26 Oct 2026, 13:45 UTC@Seele_Leaks/3843026 Oct 2026, 14:02 UTC1.0017 minutes
@GenshinLeakflow/19677 · this entry5 Nov 2026, 04:18 UTC@Seele_Leaks/393175 Nov 2026, 04:20 UTC1.0072 seconds
@Seele_Leaks/350945 Sept 2026, 06:01 UTC@GenshinLeakflow/19193 · this entry5 Sept 2026, 06:20 UTC0.9619 minutes
@GenshinLeakflow/19073 · this entry13 Aug 2026, 03:25 UTC@Nahida_Leak/1199714 Aug 2026, 01:59 UTC1.0023 hours
@GenshinLeakflow/19083 · this entry13 Aug 2026, 03:57 UTC@Nahida_Leak/1200014 Aug 2026, 01:59 UTC1.0022 hours
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
@Seele_Leaks11 (8/8 hand-verifiable sample passed)0.962 minutesthis entry (8–3)
@Nahida_Leak6 (6/6 hand-verifiable sample passed)0.9818 hoursthis entry (6–0)
@HXG_Channel8 (8/8 hand-verifiable sample passed)0.9661 minutesthis entry (6–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. 5 of the 5 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 208 comparable posts for this entry, running 30 July 2026 to 16 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).

Views per post sit far above this size band

16,900 average views per post against 49,416 subscribers — an engagement rate of 34.2%. Across the 1,296 registered channels in the same cohort — 31,659–99,809 subscribers, posting mainly in Chinese — the middle half sit between 0.987% and 5.59%, with a median of 2.51%.

What this was computed from
Window30 days (6 October 2026 – 5 November 2026)
Posts measured112 of 112 published in the window (0 exact, 112 rounded by Telegram)
Views totalled1,893,390
Mature posts only46.1% over 70 posts read at least 24h after publication
Subscribers49,416 measured 4 November 2026
Cohortb31623:zho · 1,296 channels · p10 0.278% · p25 0.987% · p50 2.51% · p75 5.59% · p90 11.5%
Position in cohort99.228th percentile · 13.6× the cohort median
Uncertainty±0.06% of the figure, from Telegram’s rounding
Post languageChinese · 82.3% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the keys clone_mutual · clone_source · err_high, last confirmed 17 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

41,32450,20045,7627 August 202617 November 2026
65 measurements spanning 102 days, net +8,876. 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 39,993–51,531 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
17 Nov 2026, 08:5450,200+190
13 Nov 2026, 22:5550,010+64
11 Nov 2026, 06:4049,946+78
9 Nov 2026, 16:0949,868+87
8 Nov 2026, 06:2649,781+109
6 Nov 2026, 23:0549,672+81
6 Nov 2026, 00:5049,591+175
4 Nov 2026, 23:4049,416+388
3 Nov 2026, 22:1949,028+395
2 Nov 2026, 23:5648,633+153
1 Nov 2026, 21:0048,480+77
31 Oct 2026, 23:4148,403+47
31 Oct 2026, 02:0748,356+33
30 Oct 2026, 02:1948,323+37
28 Oct 2026, 22:4648,286+57
27 Oct 2026, 19:3748,229+61
26 Oct 2026, 17:4648,168+69
25 Oct 2026, 14:4848,099+55
24 Oct 2026, 13:2848,044+84
23 Oct 2026, 11:4447,960first reading

Engagement

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

ERR · 30 days
29.2%
avg views ÷ 50,200 subscribers
Avg views / post
14,600
125 posts measured
Reaction rate
0.634%
reactions ÷ views · ER floor
Posts in window
125
of 440 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 17 November 2026
Posts held440 (30 July 2026 – 17 November 2026)
Views total1,829,310
Reactions total11,603
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 05:47 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
1h 07m
Average length
56s

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

42,193 reactions across 438 posts, in 58 distinct kinds. The most used accounts for 24.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤10,32824.5%
👎8,77920.8%
👍5,46012.9%
🤣3,1827.54%
😱3,0617.25%
🤯1,4683.48%
🤔1,3893.29%
😭1,1172.65%
🤬9412.23%
🥰7991.89%
🤩7871.87%
😨5911.40%
😁4391.04%
🤪4180.991%
🔥4060.962%
🎉3460.82%
☃3070.728%
😍2520.597%
🤨2150.51%
👀2000.474%
38 further kinds1,7084.05%

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

Measured over the 440 most recent posts we hold, published 30 July 2026 to 17 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: 33 of 125 posts held from the last 30 days (26.4%) 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).

17 Nov 2026, 00:12 UTC≈5,070 views49 reactionsread 17 November 2026
Video

source #Astral_Leaks 安娜丝塔夏6命特殊动画 Anastasya C6 Unique Animation #安娜丝塔夏

❤26👎10😱4❤‍🔥3🌚2👍2🗿2

Signed 御坂妹

16 Nov 2026, 15:50 UTC≈8,600 views97 reactionsread 17 November 2026
Photo

1 / 2 / 3 / 4 #UncleNiceCock #Sakiko_Leaks #hxg_diluc 7.X未来角色信息 图中角色就是Simurgh 三个限定男角色 “Simurgh”, 诺伊, 戴因斯雷布 三个限定女角色 Yunyan,安德罗-巴西利克斯公主,K.K. 4星角色渊上+文输角色 今年文输角色是应该是女角色 Again this is "simurgh" being mentioned here 3 Limited Males = "Simurgh", Noy, Dainsleif 3 Limited Females = Yunyan, Princess Andro-Basilisks, K.K 4 stars: Enjou + "Wenshu" “Wenshu" is not a specific person. It means characters who promote Chinese Tradit…

👎49👍21❤14🤬6🤯3😱2💅1🥰1

Signed プラナ

16 Nov 2026, 14:43 UTC≈11,700 views61 reactionsread 17 November 2026

1 / 2 #红玉的落寞 #wwwhatever #sus 7.4+ 后半新角色实装安排 我舅舅的意思是有话还是早说,老藏着没意义 既然v3爆对了那聊点别的,30分钟后删,体系2的五星有浮萍,西摩格男孩,二公主,诺伊,K.K.和戴因斯雷布,四星有渊上和文输,当前渊上真不是五星,西摩格男孩是主题图中的人,我舅舅的看法是早说了对所有人都好,老捂着没意思 红玉说得基本对,目前确实是这样 后半算上云烟,限五目前三男三女,四星我这边不止两个 有人提到code对不上的问题,可能是真不算上枪主吧

👎27👍20❤6😱5🤣1🤯1🥰1

Signed Camgfy

16 Nov 2026, 13:38 UTC≈9,700 views108 reactionsread 17 November 2026
Video

1 / 2 #Seele_Leaks #析构万理的发条公主 7.3 地图场景背景音乐变更 7.3版本里,如果你去到7.2过场动画中被安娜丝塔夏冻结的丘丘人附近,背景音乐会变成钢琴独奏版的《琴弦啊,琴弦》,即7.2过场动画的背景音乐以及至冬堡夜晚的音乐。 Seele没有修正模型,但BGM是正常触发的 In 7.3, if you go near the hilichurl in Hallowed Plain that was frozen by Anastasya in the 7.2 cutscene, the BGM will become a piano solo version of Strings, O Strings, which is the BGM of the 7.2 cutscene and also nighttime Snezhnograd. 「GI 7.3」 I dont fix the prop,b…

😢73😭18👍5👎3❤2🤣2🤩2😱2

Signed Camgfy

16 Nov 2026, 13:38 UTC≈9,260 views28 reactionsread 17 November 2026

source #析构万理的发条公主 7.3 秘境描述文本 无可饶赦的愚行尚未将梦染成漆黑的岁月,纯白的无染之人曾是那样述说着、坚信着、畅想着更幸福的明天——再没有忧伤、哭泣和苦痛的明天。 可是幸福没有明天,它没有过去,没有未来。曾一度心怀梦想的软弱者最终还是背弃了共担的宏愿,独自吞下悔恨的苦果。 In the years before unforgivable folly had plunged every dream into darkness, the pure and untainted still spoke of, believed in, and dreamed of a happier tomorrow, one without sorrow, tears, or pain. But happiness has no tomorrow. It has neither past nor future. In …

👍15❤5👎3😱3🤬2

Signed Camgfy

16 Nov 2026, 12:30 UTC≈9,750 views47 reactionsread 17 November 2026
Photo

1 / 2 #析构万理的发条公主 7.3 v3 幽境危战 优化了文案,刚才的图可能看不出来,现在燃烧反应伤害也可以加条了 另外,除了血量和燃烧加条之外,没有任何其他改动(抗性、加条数值、持续时间等都没改) #幽境危战

❤20👏14👍5👎4🤔2😱2

Signed Camgfy

16 Nov 2026, 10:48 UTC≈10,300 views59 reactionsread 17 November 2026

source #析构万理的发条公主 7.3 V3 安娜丝塔夏 专武故事 那是纷争的血迹为新雪掩埋的时岁,苍星的圣炬初将皇都高穹照亮。 从无瑕的初雪与朔风中诞生的精灵,彼时仍是侍立于王廷的传令使, 因阻滞施佩金进军的战勋获赐圣枪,得以随行在维涅德之主的身后, 手捧纯净清馨的香膏登临高阶之上,为北境的新皇奉上盛典的序礼。 昔日饮血相残的妖灵王公敛去爪牙,与诸氏族的显贵一同举杯欢庆, 自远港而来的短命凡人亦屏息驻足,仰望那轮破开严冬的煌煌圣火。 彼时离席步上露台的少年远眺炬塔,蔚蓝如空的瞳中满溢诚挚欣慰, 回身望向被他称作挚友的银发少女,清澈的声息里难掩喜悦与期许。 「看哪,安娜丝塔夏,我的好朋友,看那圣炬的光热如何胜过风雪!」 「昔日相互攻伐的氏族如今已和解,羸弱之人也不必再为凛冬哀切。」 「即便极北的长夜永无终结的时日,只要大家共同承担荣光与苦厄,」 「总有一天,不管是妖精还是人类,一定能在爱的国度中过得快乐!」 沉默寡言的传…

🥰26☃9😱8👎7❤4👍2🎉1🤪1

Signed プラナ

16 Nov 2026, 10:42 UTC≈12,900 views46 reactionsread 17 November 2026
Video

source #Kazusa_Leaks 7.3 V3 达妮卡音效更新 安娜丝塔夏音效仍然缺失 GI 7.2.52 - Updated Danica SFX Anastasya still has no SFX at all. #达妮卡 #安娜丝塔夏

❤27👎9👍5😢2😱2😁1

Signed プラナ

16 Nov 2026, 10:30 UTC≈13,100 views97 reactionsread 17 November 2026
File

#GachaBase 7.3 v3 角色与武器改动 角色改动 - 安娜丝塔夏 - 达妮卡 武器文本改动 - 银昼 - 炎烈狮牙 圣遗物文本改动 - 遥天奉翠华引 改动细节 #安娜丝塔夏 #达妮卡 #武器 #圣遗物

👍40😭24❤9😱9👎7🤔2😘2🍾1

Signed Camgfy

16 Nov 2026, 10:23 UTC≈10,400 views19 reactionsread 17 November 2026
File

source #Sakiko_Leaks 7.3 V3 BGM ✓ New files: 7 ✓ Changed files: 9 ✓ Removed files: 0 #音乐 #周本

❤12🆒2👍1👎1😁1😱1🙏1

Signed プラナ

16 Nov 2026, 10:02 UTC≈10,800 views89 reactionsread 17 November 2026

source #Seele_Leaks 7.3 V3预下载大小 V3 2.62GB

😱60❤12😁5☃4🙏3👍2👎2🗿1

Signed プラナ

16 Nov 2026, 01:18 UTC≈15,300 views223 reactionsread 17 November 2026

Posted without readable text

👎97❤45🤣37👍10🤓9😱7🕊6🤔6

Signed プラナ

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

Posts edited after publishing

@GenshinLeakflow edited 24 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.

First edit seen
24 August 2026
Most recent edit
10 November 2026

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 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.

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.

Channels Telegram recommends alongside this one

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.

Seele Leaks
@Seele_Leaks · 150,730
#1
Team Stellar-Mew
@team_mew · 27,571
#2
Genshin Delta
@genshindelta · 14,298
#3
ㅤ
@PlumTeamLeaks · 8,704
#4
小灯泡Gularico
@divaleaks · 2,251
#5
Genshin Null
@GenshinNull · 6,023
#6
Genshin Rumors
@GenshinRumors · 3,187
#7
原神内鬼吧
@yuanshen_games_leaks · 3,517
#8
IX|Archive
@ninthspace · 1,859
#9
Nahida
@Nahida_Leak · 27,003
#10
DuolaDStudio|科技數碼翻墻雜談|日常分享
@DuolaDStudio · 204
#11
在花🎗️科技圈
@zaihuapd · 290,717
#12
原神国际服 | Genshin Impact Overseas
@GenshinOverseas · 1,626
#13
原神 | Genshin Impact CN
@YuanShen · 9,090
#14
GenshinImpactVersion
@GenshinVersion · 353
#15
Firefly
@FireflyLeak · 15,922
#16
Genshin Impact Extra - Italia 🇮🇹
@GenshinImpactExtra · 8,197
#17
Zenless Zone Zero - Zeta
@ZZZzetachannel · 12,338
#18
ZZZ Leak
@ZZZ_Leak · 4,823
#19
donut leaker
@donutleaker · 11,889
#20
Zani's oppai mole
@zanisOppai · 3,920
#21
Сплетник Фатуи | Сливы Геншин Импакт
@spletnik_fatui · 13,641
#22
Reddit | Genshin Leaks
@genshinreddit · 51,612
#23
Ростик и лунная жызнь
@yenselife · 11,218
#24
Геншин Импакт | Бледная
@blednayaleaks_genshin · 109,688
#25
Wuthering Waves | WuWa News | WuWa Updates
@waves_wuthering · 29,811
#26
Thereallo LLC
@PlayerGetTokenReq · 640
#27
Genshin Impact [RC]
@GenshinRC · 220,375
#28
Genshin Stellar Honey️❄️
@GenshinHoney · 11,090
#29
WuWa Land | Wuthering Waves
@wuwaland · 35,715
#30
Reddit | Honkai: Star Rail
@hsrreddit · 32,084
#31
Хонкай: Стар Рейл | Бледная
@blednayaleaks_hsr · 65,255
#32
Ванильные Сливки | Genshin Impact
@vanileaks · 671,369
#33
Вести от Паймон (старый юзернейм)
@paimon_leaks · 13
#34
Станція Герта | українськомовний Honkai: Star Rail
@HertaStationUA · 7,210
#35
Honkai: Star Rail | Миря
@honkai_star_rail_leaks · 46
#36
Genshin Media
@genshinmedia · 159,702
#37
Revue Impact
@revueimpact · 2,565
#38
Genshin Impact RU
@genshin_impact_ru_off · 474,494
#39
Геншин Импакт | Новости Промокоды
@genshinv · 53,310
#40
Ковчег Видере | Сливы Геншин Импакт
@videreleaks · 5,232
#41
Wuthering Waves
@wutheringwaves · 153,912
#42
Waileaks | Honkai Impact 3rd
@waileaks · 2,594
#43
Reddit | Zenless
@zenlessleak · 24,593
#44
Reddit | Genshin Impact
@redditgenshin · 29,670
#45
Zenless Zone Zero | iNFO
@Zenless_Zone_Zero_Info · 102,925
#46
Zenless Zone Zero | Миря
@zenless_zone_leaks · 31
#47
Honkai Star Rail Revengers
@Honkai_Star_Rail_Revengers · 438
#48
HSR | Kira
@hsr_kira · 2,176
#49
Honkai: Star Rail RU
@honkaistarrailofficial · 228,517
#50
AstraLore
@astralore · 18,755
#51

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.

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.

HXG’s Channel
@HXG_Channel · 57,767
Telegram ranks this channel #2 of 53 here — alongside 52 others — read 2 September 2026
Seele Leaks
@Seele_Leaks · 150,730
Telegram ranks this channel #2 of 56 here — alongside 55 others — read 28 August 2026
MeroMero
@merlin_impact · 42,611
Telegram ranks this channel #9 of 64 here — alongside 63 others — read 2 September 2026
Sakura Haven
@sakurahaven · 43,010
Telegram ranks this channel #19 of 57 here — alongside 56 others — read 2 September 2026
Wuthering Waves | WuWa News | WuWa Updates
@waves_wuthering · 29,811
Telegram ranks this channel #21 of 49 here — alongside 48 others — read 8 September 2026
Canlı İddaa Tahmin
@tahmin_iddaa_kupon · 29,800
Telegram ranks this channel #26 of 33 here — alongside 32 others — read 14 September 2026
Honkai: Star Rail - Zeta
@hsrZeta · 20,195
Telegram ranks this channel #29 of 55 here — alongside 54 others — read 28 September 2026
WuWa Land | Wuthering Waves
@wuwaland · 35,715
Telegram ranks this channel #66 of 76 here — alongside 75 others — read 2 September 2026
Reddit | Genshin Leaks
@genshinreddit · 51,612
Telegram ranks this channel #69 of 71 here — alongside 70 others — read 25 August 2026

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.

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

“Genshin Leakflow” (@GenshinLeakflow), 50,200 subscribers as measured 17 November 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.