4 measurements spanning 7 days, net -5. 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 763β772 and does not start at zero.
Measurement log β every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
14 Aug 2026, 21:23
764
-7
8 Aug 2026, 01:49
771
no change
8 Aug 2026, 00:00
771
+2
7 Aug 2026, 18:10
769
first reading
Engagement
10 posts held, back to 5 November 2024 β 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
70.9%
avg views Γ· 764 subscribers
Avg views / post
542
1 post measured
Reaction rate
2.21%
reactions Γ· views Β· ER floor
Posts in window
1
of 10 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 24 July 2026
Posts held
10 (5 November 2024 β 24 July 2026)
Views total
542
Reactions total
12
Forwards / comments
not exposed by the public surface β not measured, not estimated
Readings taken
8 Aug 2026, 01:49 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
154 reactions across 9 posts, in 10 distinct kinds. The most used accounts for 57.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
β€
89
57.8%
π₯
16
10.4%
π€‘
13
8.44%
β€βπ₯
11
7.14%
β‘
7
4.55%
π
7
4.55%
π
6
3.90%
π
2
1.30%
π₯°
2
1.30%
π€―
1
0.649%
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 9 of the 10 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 154reactions in total: the kind of figure the paragraph above means by βa reaction total printed elsewhere on the pageβ.
Measured over the 10 most recent posts we hold, published 5 November 2024 to 24 July 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.
βπͺ Heroku 2.1.0 is here!
βπͺ Some time later, we update the layers again to the latest ones and do not forget about the innovations!
βπ· This time we brought a lot of new things! The list of changes was split into two pages...
The most important and large-scale thing is that we have completely moved from aiogram to Telethon. Yes, yes, you heard right, now there will be no hassles about the bot, its slow operation or β¦
π After a full six months of development, torment, and suffering, my team and I are ready to present the new version of Heroku!
βπ With Heroku v2.0.0, you can make your modules even more beautiful using Bot API 9.4+, and far more convenient thanks to the latest release of Telethon 2.0.0.
βπ Alongside the latest layers, a HUGE amount of new and interesting features has been added! For example: a placeholder system tβ¦
Hello everyone πͺ΅
After a long development of version 1.7.2, numerous changes and code revisions, I can confidently say that the further we go, the better it gets. βοΈ
We are already getting better and better, and more to come. π§ββοΈ
Enjoy using it!
With love, πͺπͺπͺπͺ
πͺπͺπͺπͺ now on LavHost!
π«‘ On the eve of the release, we decided to add Heroku to the well-known LavHost
πΆβπ«οΈ From today, every LavHost user can install Heroku in just a couple of clicks!
π This channel canβt be displayed because it violated Telegram's Terms of Service.
β¬οΈ To install, just go to @lavhostbot and follow these steps:
β’ Enter the command /buy, select and pay the invoice
β’ Send the payment receipt if reqβ¦
In honor of adding Heroku to the already famous Hikka hosting, and also on March 8 (International Women's Day), I want to give you a couple of links to subscribe to this same host, happy holiday to everyone!
β€οΈ Happy New Year to all! I'm sure you're waiting for this momentous event and waiting for the v1.6.8 update, which will be released exactly on New Year's Eve Moscow time! (utc +3) π
π€·ββοΈ This year, at the moment, a total of 234 commits have been released to the main branch of the project (master) and an additional 120 to the beta branch (v1.6.8). π Very soon you will see many bug fixes, the final renaming to Herokuβ¦
Showing the 10 most recent of 10 posts we hold for @heroku_ub. 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.
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.
Shares as published, totalling 99%. 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 10 most recent posts we hold, published 5 November 2024 to 24 July 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.
Citation-graph rank
Citation-graph rank β 179,827 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 4 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 14 August 2026 β this
entry's latest reading, not the date you are reading this.
βπͺ | Heroku Userbotβ (@heroku_ub), 764 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/heroku_ub.
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.
