4 measurements spanning 8 days, net +38. 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 461–511 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
14 Aug 2026, 19:36
505
+35
7 Aug 2026, 16:36
470
+3
7 Aug 2026, 05:01
467
no change
7 Aug 2026, 04:48
467
first reading
Engagement
20 posts held, back to 25 May 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 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
189.4%
avg views ÷ 505 subscribers
Avg views / post
957
7 posts measured
Reaction rate
3.72%
reactions ÷ views · ER floor
Posts in window
7
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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 3 August 2026
Posts held
20 (25 May 2026 – 3 August 2026)
Views total
6,696
Reactions total
249
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 05:01 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
635 reactions across 20 posts, in 24 distinct kinds. The most used accounts for 41.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
261
41.1%
💋
142
22.4%
🤮
53
8.35%
💯
41
6.46%
🔥
29
4.57%
💘
24
3.78%
🥰
21
3.31%
❤🔥
13
2.05%
👍
8
1.26%
💩
8
1.26%
🙏
8
1.26%
🤡
5
0.787%
😭
4
0.63%
🆒
3
0.472%
🖕
3
0.472%
🎉
2
0.315%
😎
2
0.315%
🦄
2
0.315%
☃
1
0.157%
🍌
1
0.157%
4 further kinds
4
0.63%
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 20 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 635reactions 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 25 May 2026 to 3 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.
just in case this comes up in the future: i do not maintain nor endorse any inugram forks. use them at your own risk, i am not responsible for any damage.
also a reminder that being open-source doesn't always mean the apk is built from that source (inugram is), stay vigilant :3
(not to discourage anyone from doing that! just a disclaimer of sorts)
#release
v12.9.2-8dfa8f1 (build 40, based on 6991)
4f94583: rebase to 6991
51243f8: fix album spoiler re-hiding on scroll (stock bug)
78954b8: hopefully fix stories crash when sender is deleted
6b63ced: fix bubble tails still visible in ripple
6bbcac7: fix new items gallery flashing
6af3984: fix black screen when rotating with a chat preview open (stock bug)
b6b5f9b: hopefully fix webm stickers sometimes getting stu…
#release
v12.9.0-d66111d (build 36, based on 6966)
e40d49d: fix light status bar in classic ui
e86e314: stock crash fixes
03bc797: classic ui fixes
2bc6f9a: display options for communities in chat list
13aaefb: copy name by long-tapping it in the profile
a121dd1: show member count on the join request sheet
c2b5ab0: fix folder pins missing when dialog not cached (stock bug)
cf8b8f7: "select all" in dialogs list
502dc…
#release
v12.9.0-d373544 (build 35, based on 6966)
4417e79: rebase to 12.9.0 (6966)
4d30b54: fix motion photos crash
465414b: fix crash when video cover frame fails to decode (stock bug)
d87f7c1: fix gallery crash on android 9
2c43be1: fix biometric gate crash on null context
e1c78fd: fix crash when opening a profile whose note was removed server-side
28dc376: fix hide with spoiler pending for newly taken photos
c54…
#release
v12.8.1-0e1b2d3 (build 33, based on 6916)
85cca81: fix expandable switch counter badge overlapping the switch on long titles (stock bug)
5eee7a2: split classic ui tab bars toggle: folders bar, shared media tabs
f6b72d1: only show admins/permissions for chats
d76b726: improve clasic ui shared media tab
ac2fc58: fix blurry small stickers (stock bug)
20df435: full-quality sticker previews in stickerset preview…
#release
v12.8.1-55aea6c (build 32, based on 6916)
c5f62c9: fix "hide with spoiler" not always appearing
f52a5e9: fix chat editor crash
26cf275: fix voice recorder fab crash
acf3adf: auto-disable proxy when vpn is connected
7b92f5b: biometric confirmation before deleting chats/logout
9fadeb3: outlined text style for painter
6d2d0ce: fix a bunch of stock memory leaks
c72f8a6: install fonts from messages
703fbd0: tg:/…
#release
v12.8.1-78056e6 (build 31, based on 6916)
f38c916: allow channels in paranoia
5ee112b: fix photo zoom/video progress resetting on message edit (stock bug)
88cdbc3: revert chat header sizings in non-island ui
4f1c4c8: font library: customizable media editor fonts + app font stack (#19)
ecfb75d: fix passkeys in keepassdx
b7b6aad: hopefully fix pip opening with failed red snapshot (stock bug)
98dab9e: fix "sho…
❤15💋6❤🔥4🤮3🍾1💘1
Showing the 12 most recent of 20 posts we hold for @InugramCI. 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 — 1,168,354 of 1,350,102entries 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.
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 14 August 2026 — this
entry's latest reading, not the date you are reading this.
“Inugram CI” (@InugramCI), 505 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/InugramCI.
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.