Telegram RegisterThe public register of Telegram
Telegram profile photo for NeriPlayer CI Builds

Channel

NeriPlayer CI Builds

@neriplayer_ci

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

603subscribers

+0 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1002992652008
TypeChannel
Username@neriplayer_ci
Description开发者的个人频道 @ouom_pub 项目地址 https://github.com/cwuom/NeriPlayer OWNER: @ouom_bot CI 版本通常具有不稳定性 ------ My Channel: @ouom_pub ​GitHub: https://github.com/cwuom/NeriPlayer ​Note: CI builds are typically unstable.
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/neriplayer_ci

Growth

60311 Aug 2026, 16:17 — 603 subscribers11 Aug 2026, 16:30 — 603 subscribers11 Aug 2026, 16:1711 Aug 2026, 16:30
2 measurements taken within a single day. 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 602–604 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 16:30603no change
11 Aug 2026, 16:17603first reading

Engagement

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

ERR · 30 days
14.9%
avg views ÷ 603 subscribers
Avg views / post
89.8
20 posts measured
Reaction rate
2.00%
reactions ÷ views · ER floor
Posts in window
20
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 2 of 20 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 11 August 2026
Posts held20 (7 August 202611 August 2026)
Views total1,797
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 16:30 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

Photos
9
Videos
1
Links
459

Lifetime counters from Telegram’s own channel header, read 11 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.

Reaction mix

5 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍5100.0%

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 2 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 5reactions 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 7 August 2026 to 11 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

11 Aug 2026, 13:49 UTC37 viewsread 11 August 2026
File

检测到新的 GitHub 推送! Commit SHA: 5bba4e76efa521b24c3c6c4dd7c0e166009ee960 fix: refine PlaylistModernVisualColorsProvider layout and add verification test (#334) 提交者: INTENTION 查看详情

11 Aug 2026, 12:01 UTC57 viewsread 11 August 2026
File

检测到新的 GitHub 推送! Commit SHA: 3035571366c329d18461ff8d762a0ebe323674c2 feat: optimize storage analysis and refine cache details UI (#328) * feat: implement granular storage usage visualization and fine-grained cache management * refactor: clean up settings UI and optimize storage scanning logic * feat: optimize storage analysis and refine cache details UI 提交者: INTENTION 查看详情

11 Aug 2026, 11:10 UTC59 viewsread 11 August 2026
File

检测到新的 GitHub 推送! Commit SHA: 7dca8bc030b3d93303fb203577e12dec6703be06 Merge pull request #331 from cwuom/revert-330-intention/fix-background-next-silence Revert "feat: enhance media cache integrity and playback recovery robustness" 提交者: INTENTION 查看详情

11 Aug 2026, 09:03 UTC65 viewsread 11 August 2026
File

检测到新的 GitHub 推送! Commit SHA: fd9d70b3795895bb31e90241be82c10528a5da34 feat: implement cross-process WebView state clearing and platform-specific logout (#329) 提交者: INTENTION 查看详情

11 Aug 2026, 07:37 UTC67 viewsread 11 August 2026
File

检测到新的 GitHub 推送! Commit SHA: 4cf3623614a2b3b3af1a33c8f2d12ada2b7a5a3d fix: reset download file name template when dialog is canceled (#326) close #325 提交者: INTENTION 查看详情

11 Aug 2026, 06:57 UTC64 viewsread 11 August 2026
File

检测到新的 GitHub 推送! Commit SHA: 57eaacd78f1a373d26aaa859c826c454d2b6fba6 feat: add NetEase playlist picker and support syncing songs to custom playlists (#322) * feat: add NetEase playlist picker and support syncing songs to custom playlists * fix: harden NetEase playlist sync with request tracking and improve error reporting * fix(netease): batch failed playlist song checks 提交者: INTENTION 查看详情

11 Aug 2026, 05:30 UTC59 viewsread 11 August 2026
File

检测到新的 GitHub 推送! Commit SHA: e981b5fe82fea00c96ef3c8add0d1a8b85fd2415 fix: handle system back navigation in lyrics editor (#324) 提交者: INTENTION 查看详情

11 Aug 2026, 03:25 UTC66 viewsread 11 August 2026
File

检测到新的 GitHub 推送! Commit SHA: b7e248f94249107e5f65b60cce89bfa229214c05 feat: stop playback and service on task removal and enhance audio route loss handling (#314) * feat: stop playback and service on task removal and enhance audio route loss handling * refactor: restructure onTaskRemoved and ensure reliable playback state persistence * fix: require PCM audio processing for Bilibili source in PlaybackAudioOffloadP

11 Aug 2026, 01:53 UTC71 viewsread 11 August 2026
File

检测到新的 GitHub 推送! Commit SHA: 6308fa6080b1e863edc5acb8de07584752cb40ab fix: mute Listen Together listeners on audio route loss instead of pausing (#318) 提交者: INTENTION 查看详情

10 Aug 2026, 13:05 UTC86 views2 reactionsread 11 August 2026
File

检测到新的 GitHub 推送! Commit SHA: 3d1b6b06b47e275ac738f35ee94b2316bb333cc2 refactor: extract SettingsPageHost and optimize split-layout transitions for nested settings pages (#315) 提交者: INTENTION 查看详情

👍2

10 Aug 2026, 10:33 UTC87 viewsread 11 August 2026
File

检测到新的 GitHub 推送! Commit SHA: 26e56674b59c7f6dab961003bb2722f76552417b feat: enable playback fade-in and crossfade by default 提交者: cwuom 查看详情

10 Aug 2026, 08:06 UTC90 viewsread 11 August 2026
File

检测到新的 GitHub 推送! Commit SHA: 9dcafb17ef8122c861eb200ce701037490a24506 Merge remote-tracking branch 'origin/master' 提交者: cwuom 查看详情

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

Citation-graph rank — 230,498 of 1,480,975entries 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.

Forward network

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.

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

“NeriPlayer CI Builds” (@neriplayer_ci), 603 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/neriplayer_ci.

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.