[#Notice #Update] 我们启用了备用服务器。 由于相关情况比较复杂,使用期间可能会产生各种问题,请尽量不要做播放视频以外的操作,如换密码或上传头像。 使用备用服务器期间一切变更都不会保留,包括播放记录等,同时注册保持关闭。 可能存在性能劣化的情况。
❤12👍1

Channel
@nijigen_emby
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
11,005subscribers
+9 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001327967885 |
|---|---|
| Type | Channel |
| Username | @nijigen_emby |
| Description | NSFW-G 对吗? 打开你的电脑,准时收看二次元~ 教程 https://intro.bgp.yt/ (https://)media.nijigem.by 443 @nijigen_help_bot emby 管理机器人 @nijigen_pm_bot 双向私聊助手 |
| Created | Between 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/nijigen_emby |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 11:22 | 11,005 | +10 |
| 12 Aug 2026, 22:52 | 10,995 | +4 |
| 11 Aug 2026, 22:42 | 10,991 | -2 |
| 10 Aug 2026, 20:17 | 10,993 | +4 |
| 9 Aug 2026, 18:12 | 10,989 | -3 |
| 8 Aug 2026, 19:21 | 10,992 | -6 |
| 7 Aug 2026, 19:52 | 10,998 | +2 |
| 7 Aug 2026, 17:30 | 10,996 | no change |
| 7 Aug 2026, 17:26 | 10,996 | first reading |
30 posts held, back to 25 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 17 pagesof 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. It is computed over the 24 of 26 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 15 August 2026 |
|---|---|
| Posts held | 30 (25 July 2026 – 15 August 2026) |
| Views total | 54,156 |
| Reactions total | 404 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 17:03 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 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
404 reactions across 22 posts, in 18 distinct kinds. The most used accounts for 25.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 101 | 25.0% | |
| 🙏 | 60 | 14.9% | |
| 😱 | 32 | 7.92% | |
| 🌚 | 28 | 6.93% | |
| 👍 | 27 | 6.68% | |
| 😁 | 26 | 6.44% | |
| ⚡ | 25 | 6.19% | |
| 🤣 | 24 | 5.94% | |
| 🤯 | 17 | 4.21% | |
| 🫡 | 17 | 4.21% | |
| 🤗 | 15 | 3.71% | |
| 😢 | 10 | 2.48% | |
| 💊 | 6 | 1.49% | |
| 👏 | 5 | 1.24% | |
| 🤡 | 4 | 0.99% | |
| 🥰 | 4 | 0.99% | |
| 😎 | 2 | 0.495% | |
| 🤔 | 1 | 0.248% |
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 24 of the 30 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 404reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 30 most recent posts we hold, published 25 July 2026 to 15 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.
[#Notice #Update] 我们启用了备用服务器。 由于相关情况比较复杂,使用期间可能会产生各种问题,请尽量不要做播放视频以外的操作,如换密码或上传头像。 使用备用服务器期间一切变更都不会保留,包括播放记录等,同时注册保持关闭。 可能存在性能劣化的情况。
❤12👍1
[#Outage #Update] 目前服务器依然在维修中。这段时间内我们会在频道内轮播番剧。
👍21
Live stream started
Live stream finished (1 day)
原国务院总理朱镕基8月12日11时06分在北京逝世,享年98岁。新华社18时刊登讣告全文。 (新华社)
🙏60😁4
Live stream started
野兽日
❤4
二次元emby 0721频道 pinned «[#Outage #Notice] 故障公告 服务器出现突发的故障,已经通知机房进行排障。(数据都有定时备份) No ETA»
王警官拿放大镜仔细观察重要证据许久后,终于把重要证据烧掉了。 王警官与犯罪嫌疑人进行了长达两个多小时的周旋,最终二人都被管理员赶下旋转木马 平日配合默契的王警官与助手小刘发生了分歧。王警官认为虽然死者身处密室,但身体缠有绷带,应该是死后被人为放入密室的。而小刘认为,王警官不应当在单位组织去埃及旅游时说这些有的没的。 11:17王警官抵达案发现场, 11:17王警官向法医了解情况。 11:17王警官询问嫌疑人的不在场证明, 11:17王警官发现自己的手表坏了。 王警官从小天赋异禀,抓周的时候就抓了个小偷。 听到嫌疑人自述犯下此案是由于贪念作祟,王警官立即指出贪没有 suì 这个读音。
❤9
[#Outage #Notice] 故障公告 服务器出现突发的故障,已经通知机房进行排障。(数据都有定时备份) No ETA
❤30🫡17😱8
避雷有这些行为的噶啦game男生 (一),一直存档的: 这种男生心机深重,步步为营,随时准备推倒重来。他根本不相信命运,他只想掌控你! (二),从不存档的: 这种男生极其自负,丝毫不尊重蝴蝶效应,说明他根本不在乎你们的结局,这种人根本没有责任感。 (三),只在遇到选项才存档的:这种男生极度鸡贼,是典型的投机分子!平时不作为,一到关键时刻就想留后路。他在这时候存档,说明他做决定根本不是因为爱你,而是在权衡利弊!一旦发现选得不如意,他连负责的机会都不给你,直接读档把你像弃子一样甩掉! (四),开自动模式的: 这种男生极度懒惰且毫无参与感。他连手指都懒得动,说明他在感情里只想坐享其成。他不是在看剧情,他是在把你的人生当背景音乐播放,完全没把你当回事! (五),不开自动模式的: 这种男生控制欲爆表,连0.5秒的停顿都要掌控。他不停点击鼠标,说明他根本没有耐心听你说话,只想快点把你的价值榨干然后进下一章! (六),一到特殊CG就开自动模式…
❤15
那是八月八日的傍晚,我坐在HO2287航班的靠窗座位上。波音787客舱里贴满了MyGO!!!!!五位成员的等身立牌,纪念登机牌上印着高松灯的侧影。我把那只棉花娃娃放在膝头——是年初在百联ZX创趣场快闪店排队三小时才买到的限定款,千早爱音的刘海歪了一绺,我用针线缝过三次。邻座的中年男人瞥了一眼,嘴角微微一动,大约是想说“这么大的人还带娃娃”,但终究什么也没说。 起飞后约莫四十分钟,机身猛地一沉。 那种震颤不像寻常的气流颠簸——是金属在撕扯自己的声音,从机腹深处传上来,沉闷而锐利。客舱顶部的氧气面罩噼里啪啦地弹落下来,像一片倒悬的白色水母。有人在尖叫,有人在哭。我听见广播里机长的声音断断续续:“……各位乘客……紧急……请保持……”后面的话被一阵更剧烈的抖动吞没了。 我的第一反应是把棉花娃娃塞进外套里。 说不清为什么。那只娃娃的棉芯软得没有骨头,它的眼睛是两颗黑色的塑料圆片,不会眨,不会流泪。可我总觉得它在看我——用爱音那种永远带着点…
Showing the 12 most recent of 30 posts we hold for @nijigen_emby. 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.
Citation-graph rank — 1,279,064 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republishes
Channels on the register whose posts this channel has forwarded.
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 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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“二次元emby 0721频道” (@nijigen_emby), 11,005 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/nijigen_emby.
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.