Telegram RegisterThe public register of Telegram

Channel

Nagram X CI

@NagramX

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

19,353subscribers

+298 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002354396604
TypeChannel
Username@NagramX
DescriptionGitHub: https://github.com/risin42/NagramX Discussion: @NagramX_Chat
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/NagramX

Growth

19,05519,35319,2046 August 2026 — 19,055 subscribers6 August 2026 — 19,055 subscribers7 August 2026 — 19,081 subscribers8 August 2026 — 19,147 subscribers9 August 2026 — 19,174 subscribers9 August 2026 — 19,239 subscribers10 August 2026 — 19,278 subscribers11 August 2026 — 19,310 subscribers12 August 2026 — 19,353 subscribers6 August 202612 August 2026
9 measurements spanning 7 days, net +298. 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 19,010–19,398 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 20:4519,353+43
11 Aug 2026, 22:2219,310+32
10 Aug 2026, 21:0319,278+39
9 Aug 2026, 22:1219,239+65
9 Aug 2026, 01:2119,174+27
8 Aug 2026, 03:5819,147+66
7 Aug 2026, 03:0319,081+26
6 Aug 2026, 05:0019,055no change
6 Aug 2026, 04:5319,055first reading

Engagement

13 posts held, back to 20 June 2026the 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 · 30 days
64.2%
avg views ÷ 19,353 subscribers
Avg views / post
12,400
9 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
9
of 13 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 8 August 2026
Posts held13 (20 June 20268 August 2026)
Views total111,880
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 23:48 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

Links
259

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

Recent posts

8 Aug 2026, 05:23 UTC≈10,600 viewsread 12 August 2026
File

Release version. Commit Message: Version Bump See commit details ee899ef Full Changelog: b4cb1e2...ee899ef

3 Aug 2026, 11:49 UTC≈10,800 viewsread 12 August 2026
File

Test version. Commit Message: update to 12.9.2 (6991) See commit details 6b24fac

3 Aug 2026, 11:10 UTC≈10,200 viewsread 12 August 2026
File

Release version. Commit Message: Version Bump See commit details b4cb1e2 Full Changelog: 749ca56...b4cb1e2

3 Aug 2026, 03:36 UTC≈9,280 viewsread 12 August 2026
File

Test version. Commit Message: fix: support Gemini latest model parameter See commit details b2e0dad

1 Aug 2026, 12:21 UTC≈10,000 viewsread 12 August 2026
File

Test version. Commit Message: feat: add UnifiedPush WebPush support Co-Authored-By: Timothy Redaelli Co-authored-by: xtaodada Co-Authored-By: HlebRud <305529755+HlebRud@users.noreply.github.com> See commit details b5ed5a1

27 Jul 2026, 11:56 UTC≈13,100 viewsread 12 August 2026
File

Test version. Commit Message: fix: prevent crash when selecting restriction duration See commit details c7d775a

26 Jul 2026, 14:05 UTC≈12,000 viewsread 12 August 2026
File

Test version. Commit Message: feat: separate swipe-to-next for topics See commit details 8a3a5c7

19 Jul 2026, 11:54 UTC≈18,600 viewsread 12 August 2026
File

Test version. Commit Message: fix(dialogs): prevent dialogs title overlap during right sliding (#414) See commit details beaec62

17 Jul 2026, 12:36 UTC≈17,300 viewsread 12 August 2026
File

Test version. Commit Message: update to 12.9.0 (6966) See commit details 80c6040 https://telegram.org/blog/communities-editor-invisible-messages

7 Jul 2026, 14:01 UTC≈23,600 viewsread 12 August 2026
File

Release version. Commit Message: Version Bump See commit details 749ca56 2114eea...749ca56 https://telegram.org/blog/watch-apps-and-more

28 Jun 2026, 07:31 UTC≈27,400 viewsread 12 August 2026
File

Test version. Commit Message: feat: support rich message translation See commit details 2bcd1bd

21 Jun 2026, 11:55 UTC≈30,000 viewsread 8 August 2026
File

Test version. Commit Message: fix: handle channel action mode with hidden bottom bar See commit details 110a1c2

Showing the 12 most recent of 13 posts we hold for @NagramX. 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 — 321,783 of 1,160,990entries 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.

Mentions

Named by 5 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.

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

“Nagram X CI” (@NagramX), 19,353 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/NagramX.

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.