6 measurements spanning 19 days, net -17. 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 8,317–8,340 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
26 Aug 2026, 19:05
8,320
-1
23 Aug 2026, 21:26
8,321
-2
13 Aug 2026, 23:38
8,323
-8
11 Aug 2026, 00:41
8,331
-3
8 Aug 2026, 10:38
8,334
-3
7 Aug 2026, 13:46
8,337
first reading
Engagement
22 posts held, back to 1 December 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 21 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
19.7%
avg views ÷ 8,320 subscribers
Avg views / post
1,640
2 posts measured
Reaction rate
2.40%
reactions ÷ views · ER floor
Posts in window
2
of 22 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 28 August 2026
Posts held
22 (1 December 2025 – 28 August 2026)
Views total
3,286
Reactions total
79
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
28 Aug 2026, 17:57 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
6
Links
193
Lifetime counters from Telegram’s own channel header, read 28 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
414 reactions across 21 posts, in 10 distinct kinds. The most used accounts for 38.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
160
38.6%
👍
139
33.6%
🔥
48
11.6%
👏
26
6.28%
🎉
21
5.07%
💯
9
2.17%
🥰
6
1.45%
😭
2
0.483%
🫡
2
0.483%
👎
1
0.242%
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 21 of the 22 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 414reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 1 December 2025 to 28 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.
We're running a live Q&A for Machine Learning Zoomcamp 2026.
Join Alexey Grigorev on Tuesday, September 1 at 5 PM CET to learn about the course structure, modules, homework, projects, and certificates.
We'll cover:
- Who it's for and what you need before joining
- What you'll build: regression, classification, deep learning, deployment, and model serving
- Where to get help during the cohort
The live cohort start…
The next cohort of the Machine Learning Zoomcamp starts on September 14.
Join the course to
• Build regression and classification models in Python
• Work with key algorithms like linear/logistic regression, decision trees, and deep learning
• Take them to production using Docker, FastAPI, Kubernetes, and AWS Lambda
Join the live Q&A and launch events to learn more about the course before it starts.
400 course participants have already graduated with certificates. Congratulations!
If you're one of the graduates, you can find your certificate on the course management platform. Make sure you're logged in with the account you used to submit your project.
The deadline for Capstone 3 has passed. If you submitted your work during this attempt, there is still time left to review your peers. Remember, reviewing three …
The form for submitting capstone 3 is closed
If you submitted a project, you can find the assignments here:
https://courses.datatalks.club/ml-zoomcamp-2025/project/capstone3/eval
And by the way. Some of you might already be able to find your certificate in your enrollment profile here
https://courses.datatalks.club/ml-zoomcamp-2025/enrollment
We have opened a new submission form for course projects, which will close on February 3rd at 12:00 AM CET. You have less than a day left to complete your project.
The deadline for Capstone 2 has passed. If you submitted your work during this attempt, it's now time to review your peers. Remember, reviewing three peers is a mandatory requirement; if you do not complete this step, you will not pass the project.
You’ll have another chance to submit your project!
We received many requests to open another opportunity to submit the capstone project, and we have decided to do so. We'll soon create another submission form on the course management platform.
The deadline for Capstone 2 has passed. If you submitted your work during this attempt, it's now time to review your peers.
Remember, reviewing three peers is a mandatory re…
How many of you wanted to submit your project but didn't have a chance?
If there's enough interest, we can open another project attempt for submission.
React to this post with 👍 if you need another project submission attempt
👍53👎1
Showing the 12 most recent of 22 posts we hold for @mlzoomcamp. 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.
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 26 August 2026 — this
entry's latest reading, not the date you are reading this.
“ML Zoomcamp announcements” (@mlzoomcamp), 8,320 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/mlzoomcamp.
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.