3 measurements spanning 4 days, net +117. 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 327–480 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
8 Oct 2026, 10:37
462
+117
4 Oct 2026, 17:22
345
no change
4 Oct 2026, 16:47
345
first reading
Engagement
20 posts held, back to 17 August 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
166.4%
avg views ÷ 462 subscribers
Avg views / post
769
5 posts measured
Reaction rate
3.07%
reactions ÷ views · ER floor
Posts in window
5
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 4 October 2026
Posts held
20 (17 August 2026 – 4 October 2026)
Views total
3,844
Reactions total
118
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
4 Oct 2026, 17: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
208 reactions across 17 posts, in 9 distinct kinds. The most used accounts for 62.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
129
62.0%
🔥
46
22.1%
👍
11
5.29%
custom 5388704211397522006
9
4.33%
❤🔥
4
1.92%
🎉
3
1.44%
🙏
3
1.44%
🍾
2
0.962%
😎
1
0.481%
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.
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 17 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 208 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 17 August 2026 to 4 October 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.
Telegram Stars
Stars received
57
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
57
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @entinyGram. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 17 August 2026 to 4 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
📡 entinyGram v12.10.6-77b9c20 (build 20261004) — Завантажити / Download
⚠️ 32-біт (arm7) для старих пристроїв, більшості не треба — тут / 32-bit (arm7) for old devices, most people don't need it — here
[*] Rebase to 12.10.6 (ported by entinyGram)
[+] Separate Search button: додано окрему кнопку пошуку на нижніх вкладках
[+] Clock format: додано налаштування формату годинника
[+] Translate in send preview: додано пе…
📡 entinyGram v12.10.4-945c63e (build 20260926) — Завантажити / Download
⚠️ 32-біт (arm7) для старих пристроїв, більшості не треба — тут / 32-bit (arm7) for old devices, most people don't need it — here
[+] Локальні папки: додано папки, що зберігаються лише на пристрої.
[+] Іконки папок: додано власні іконки для папок.
[+] Стрічка: додано єдину хронологічну стрічку каналів.
[+] Forward Pro: додано редаговане пересил…
Today is my birthday and I’m turning 22 🎂
Huge thank you to everyone who’s been around, supported me, believed in the project, and just stayed close. You’re all seriously cool 🔥 You mean more than you know.
The best gift right now is simply spreading the word about entinyGram. Share it, mention it, tell a friend — that already means everything. The project will always stay open, no matter what ✨
A few small wins s…
By the way, about the badges.
These badges are just a little trinket and a token of appreciation from me.
I give them out at my discretion to those who help develop the client (often by reporting in @entinyGramChat). I don’t divide people and I don’t sell anything. It’s simply my way of saying thank you for your help.
The client will always stay open, free, and without analytics. I will never ask for money for any…
And this is also a temporary post.
Tell me, where did you find this client? I’m curious — I didn’t advertise it at all. I just made a fork, clumsily added some “banned features”, and a month later 50 people are already here through word of mouth.
I’d love to hear your story.
A quick post for a couple of days.
Hey, everyone! I've been seeing your reports about issues with the app, its features, and some bugs. Please don't hesitate to let us know about any bugs so that future releases will be much more stable. Thanks, folks!
Hey, everyone! Some of you just got a notification about an “update”.
You can ignore it. No need to install anything.
It’s not a virus, not malware, not some shady push — just a random buggy implementation of a beta version that somehow went out.
There are actually two separate apps. The second one is just a debug/test version I use myself and catch logs from people.
Sorry for the false alarm. Everything’s fine.
❤4👍3
Signed Oleksii "Entaytion" Kulinich
Showing the 12 most recent of 20 posts we hold for @entinyGram. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
From the last build, I removed the universal APK from the build process. How should we handle APK releases going forward?
Separate APKs for each architecture (arm64-v8a, armeabi-v7a, etc.)85%
One universal APK (all architectures in a single file)12%
Don’t build APKs at all — source only / self-build instructions (as it is now)4%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 17 August 2026 to 4 October 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Mentions
Named by 2 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.
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 8 October 2026 — this
entry's latest reading, not the date you are reading this.
“entinyGram” (@entinyGram), 462 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/entinyGram.
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.
