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

Channel

Genshin Rumors

@GenshinRumors

On this record: Topic · Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry

3,196subscribers

+27 since we began measuring on 28 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

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

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

3,1693,1963,182.528 August 2026 — 3,169 subscribers29 August 2026 — 3,170 subscribers1 September 2026 — 3,175 subscribers4 September 2026 — 3,177 subscribers9 September 2026 — 3,188 subscribers17 September 2026 — 3,196 subscribers28 August 202617 September 2026
6 measurements spanning 20 days, net +27. 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 3,165–3,200 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 13:183,196+8
9 Sept 2026, 07:173,188+11
4 Sept 2026, 03:563,177+2
1 Sept 2026, 03:153,175+5
29 Aug 2026, 10:453,170+1
28 Aug 2026, 21:453,169first reading

Engagement

8 posts held, back to 31 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
8.39%
avg views ÷ 3,196 subscribers
Avg views / post
268
1 post measured
Reaction rate
1.87%
reactions ÷ views · ER floor
Posts in window
1
of 8 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 28 August 2026
Posts held8 (31 July 202628 August 2026)
Views total268
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 21:45 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.

Reaction mix

41 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 92.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁3892.7%
24.88%
🤔12.44%

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

Measured over the 8 most recent posts we hold, published 31 July 2026 to 28 August 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

28 Aug 2026, 14:18 UTC268 views5 reactionsread 28 August 2026
Photo

[新闻相关][搬运] 2026科隆游戏展,最佳移动端游戏为燕云十六声 #NGA 提名的游戏有: 明日方舟终末地 原神 白银之城 燕云十六声 绝区零 via NGA-手游瓜事件

😁5

Signed Auto Push Bot

23 Aug 2026, 08:17 UTC793 views5 reactionsread 28 August 2026
Photo

[疑似内容] [原神] 手机里有一款太阳从北面落山的游戏 #NGA 原神至冬更新后,有网友发现,至冬的太阳是从北面落山的。 但考虑到这是个架空世界,又是“虚假之天”,也许这是开发组的什么伏笔呢? 又或者,在俄罗斯等靠近极地的地方,太阳真的是从北面落山的? via NGA-手游瓜事件

😁5

Signed Auto Push Bot

22 Aug 2026, 15:57 UTC811 views8 reactionsread 28 August 2026
Photo

[米哈游] [原神]今日至冬开服的新笑话 #NGA 在今天更新前,原神B站账号发了这么个动态,意思是放出八个兑换码,然后每个兑换码内都有一抽的原石和一些时尚小垃圾,然后输入一个兑换码可以获取所有兑换码的奖励 注意这里的描述是: 然后在更新后玩家输入兑换码后发现获取的只有一抽的原石 这时候玩家发现原神官号的这条动态进行了编辑 编辑之后变成了 via NGA-手游瓜事件

😁8

Signed Auto Push Bot

21 Aug 2026, 05:18 UTC891 views4 reactionsread 28 August 2026
Photo

[夜幕之下][原神] 女性向游戏夜幕之下内道具与原神道具高度相似 #NGA 左上:《夜幕之下》中的道具 生命起搏液 左下:《原神》中的道具 精油 右上:《夜幕之下》中的道具 铝土矿 右下:《原神》中的道具 夜泊石 原神先,夜幕之下后。 官方已于昨晚偷偷更新替换素材,无相关公告。 via NGA-手游瓜事件

😁4

Signed Auto Push Bot

21 Aug 2026, 05:18 UTC716 views1 reactionsread 28 August 2026

[米哈游] 关于原神7.0的更新内容,海外出现了大量激烈的争论,尝试小切整理一下 #NGA via NGA-手游瓜事件

1

Signed Auto Push Bot

5 Aug 2026, 01:37 UTC≈2,280 views10 reactionsread 28 August 2026
Photo

[新瓜]小红薯原神玩家发表亲子言论惨遭数万楼网暴,某品牌员工用公号参与被公司辞退 #NGA via NGA-手游瓜事件

😁9🤔1

Signed Auto Push Bot

31 Jul 2026, 12:37 UTC≈2,640 views6 reactionsread 28 August 2026
Photo

[原神] 跳票了好几年的原神动画终于定档,27年2月首播 #NGA [s:ac:哭笑]这玩意为啥没人发啊,是原神已经没啥存在感了吗 跳票了这么旧,可算是定了个档了,虽然这剧情也没啥看头吧 via NGA-手游瓜事件

😁6

Signed Auto Push Bot

31 Jul 2026, 00:17 UTC≈2,160 views2 reactionsread 28 August 2026
Photo

[米哈游]疑似米哈游微博供应商跑路 #NGA 叠甲 以下内容系转发,本人未发表任何观点和看法: 米哈游系的博主寒冰冽刚拿到原神相关的企划奖项就疑似卖号。 不但把id改成任长盈win,不停地发汽车广告,ip地址也变了。 更离谱的是,还有多位创作者联合声讨他作为米哈游的供应商之一,一直以税务问题拖延结账,扣发签约自媒体的创作收益,甚至还忽悠他们自己交税,但拿不到报酬…… 根据对话来看,他确实是卖号跑路了。 via NGA-手游瓜事件

1😁1

Signed Auto Push Bot

Showing the 8 most recent of 8 posts we hold for @GenshinRumors. 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.

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 · 55,494
Telegram ranks this channel #6 of 53 here — alongside 52 others — read 2 September 2026
Genshin Leakflow
@GenshinLeakflow · 44,335
Telegram ranks this channel #7 of 51 here — alongside 50 others — read 28 August 2026
Seele Leaks
@Seele_Leaks · 139,342
Telegram ranks this channel #8 of 56 here — alongside 55 others — read 28 August 2026

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

“Genshin Rumors” (@GenshinRumors), 3,196 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/GenshinRumors.

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.