https://youtu.be/d81o0xVEekQ?is=YUyBKWUiSbz-Vc85

Channel
Hailu Yohannes Ministries
@hailuyohannes
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,196subscribers
-15 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001320580152 |
|---|---|
| Type | Channel |
| Username | @hailuyohannes |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 2 times, most recently 18 September 2026 |
| On Telegram | t.me/hailuyohannes |
Topic
Religion — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 18 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 23:17 | 1,196 | -3 |
| 11 Sept 2026, 05:00 | 1,199 | -1 |
| 6 Sept 2026, 03:00 | 1,200 | -1 |
| 1 Sept 2026, 16:58 | 1,201 | -1 |
| 29 Aug 2026, 13:43 | 1,202 | -1 |
| 26 Aug 2026, 13:35 | 1,203 | -2 |
| 23 Aug 2026, 16:04 | 1,205 | -1 |
| 17 Aug 2026, 11:58 | 1,206 | -2 |
| 14 Aug 2026, 05:28 | 1,208 | +1 |
| 10 Aug 2026, 21:28 | 1,207 | -4 |
| 6 Aug 2026, 20:02 | 1,211 | no change |
| 6 Aug 2026, 19:57 | 1,211 | first reading |
Engagement
20 posts held, back to 9 August 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 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 4 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
https://www.youtube.com/live/xuWtEtGATV4?is=-Kq_TbxgPxqadUsX
https://youtu.be/p_07ablXXWA?si=HDDpGNsrd781oK2X
https://youtu.be/kREi-AK0-L8?si=20zzGru4SrkWudfs
Share it
https://youtu.be/Eju32F8sSw0?si=YWsX1fhrpmgorhOJ
https://youtu.be/xclfQ5dSJ-0?si=P3l8m95l_ldan4lc
https://youtu.be/BBq5SiU88wA?si=0asZ7n7Tb2c8ViTv
https://youtu.be/BBq5SiU88wA?si=5ZORgSA9N_oXGyio
https://youtu.be/uplM7zNaAF8?si=s1SOpaJlOwbBhQOV
https://youtu.be/uplM7zNaAF8?si=hEo8H-c67kRKF_YJ
https://youtu.be/XUYIomXcKJc?si=8U2GpYHF0LY9EkJb
Showing the 12 most recent of 20 posts we hold for @hailuyohannes. 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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Hailu Yohannes Ministries” (@hailuyohannes), 1,196 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/hailuyohannes.
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.