Telegram RegisterThe public register of Telegram
Telegram profile photo for TyranorNext官方

Channel

TyranorNext官方

@tyranornext

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

841subscribers

+62 since we began measuring on 27 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004454021783
TypeChannel
Username@tyranornext
CreatedBetween 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 September 2026
Last confirmed live4 October 2026
Measurements held3
Confirmed unchanged1 time, most recently 4 October 2026
On Telegramt.me/tyranornext

Growth

77984181027 September 2026 — 779 subscribers27 September 2026 — 779 subscribers4 October 2026 — 841 subscribers27 September 20264 October 2026
3 measurements spanning 7 days, net +62. 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 770–850 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Oct 2026, 23:15841+62
27 Sept 2026, 23:22779no change
27 Sept 2026, 22:47779first reading

Engagement

20 posts held, back to 1 September 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
88.3%
avg views ÷ 841 subscribers
Avg views / post
743
16 posts measured
Reaction rate
1.41%
reactions ÷ views · ER floor
Posts in window
16
of 20 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 11 of 16 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 25 September 2026
Posts held20 (1 September 2026 – 25 September 2026)
Views total11,883
Reactions total123
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 23:22 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

166 reactions across 15 posts, in 7 distinct kinds. The most used accounts for 25.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4225.3%
👍4124.7%
❤3722.3%
🥰2716.3%
💩148.43%
👏42.41%
💯10.602%

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

Measured over the 20 most recent posts we hold, published 1 September 2026 to 25 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

25 Sept 2026, 10:13 UTC339 viewsread 27 September 2026

• 新增游戏引擎支持 添加 RealLive、AVG32、UK2 引擎支持 • 外观样式 应用设置增加平板模式侧边栏启动开关 此次不在telegram提供apk文件下载,可通过应用中更新或前往GitHub,对应版本号为 1.50

21 Sept 2026, 16:11 UTC634 views1 reactionsread 27 September 2026

• 关于wine的引入 目前仅与winlator cn达成共识,支持的版本为winlator cn 如果需要其他版本,请联系相关作者是否可开放跳转接口与传参调用容器 如有开放请在此处留言,后续会跟进适配

❤1

21 Sept 2026, 11:51 UTC679 views7 reactionsread 27 September 2026

• Artemis引擎 修复《秽翼的尤斯蒂娅》运行时递归爆栈闪退问题 • ons引擎 修复播放时的闪退与画面畸变 • FVP引擎 增加FVP引擎自定义字体功能 • krkr2引擎 新增原生Kirikiroid2文件浏览器界面的启动 • siglus引擎 修复部分游戏输入法键盘无法唤起和显示的问题 修复《月の彼方で逢いましょう》初次手机界面卡死 • 外观风格 新增高级玻璃主题,增加平板适配侧边导航栏 此次不在telegram提供apk文件下载,可通过应用中更新或前往GitHub,对应版本号为 1.48

❤7

20 Sept 2026, 14:00 UTC660 viewsread 27 September 2026

• 关于fvp引擎文本乱码以及汉化 由于涉及补丁版权以及分发限制,tyn并不打算实现加载功能 但是可自行使用文档中方案解决或者联系作者根据该文档示例进行适配分发

19 Sept 2026, 06:46 UTC717 views6 reactionsread 27 September 2026

• Winlator支持 测试性引入wine容器调用与支持。可从游戏页顶部添加PC游戏入库,不支持扫描。仅可调用专用测试版 • Fvp引擎 新增Fvp引擎内核,新增Fvp游戏扫描与识别入库 • Yuris与CatSystem2引擎 新增Yuris与CatSystem2引擎游戏扫描与识别入库,目前替代性使用Winlator容器作为运行层,后续更换对应引擎内核 • ONS引擎与Siglus引擎 更新引擎库 对应版本为1.42,安装包提供如下

👍6

18 Sept 2026, 08:21 UTC648 views5 reactionsread 27 September 2026

• Artemis引擎 单游戏引擎设置增加手动基础补丁等功能,应对部分游戏移植不完全的情况 此次不在telegram提供apk文件下载,可通过应用中更新或前往GitHub,对应版本号为 1.40

👍5

16 Sept 2026, 09:24 UTC754 views13 reactionsread 27 September 2026

• Siglus引擎 新增sig引擎内核,新增sig游戏扫描与识别入库 同步增加于mac端 此次不在telegram提供apk文件下载,可通过应用中更新或前往GitHub,对应版本号为 1.39

👍12👏1

15 Sept 2026, 12:16 UTC807 views15 reactionsread 27 September 2026

• krkrsdl3引擎 更新适配emote动态立绘触摸,柚子社全系/猫娘乐园全系/爱上火车/clover days'plus/驮作fd/女装百合钿/童真兄妹 • Artemis引擎 新增自研内核,已实测《闪亮女友》《常轨脱离三部曲》《甜蜜女友3》,理论大部分游戏可玩,新增官方最新内核V4(Rev.3294-emote) • 外置模拟器 新增PPSSPP与Eden显式跳转支持,新增psp与switch游戏扫描与识别入库,递交外部模拟器进行游玩 新增引擎页分类显示的开关,支持在应用设置中控制展示风格 新增复古玻璃风格对应的液态导航栏,规范名称为 液态玻璃:经典/透镜,应用设置中切换 此次不在telegram提供apk文件下载,可通过应用中更新或前往GitHub,对应版本号为 1.38

🔥14👏1

Showing the 12 most recent of 20 posts we hold for @tyranornext. 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.

Mentions

Named by 1 registered channel — 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.

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.

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

“TyranorNext官方” (@tyranornext), 841 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/tyranornext.

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.