Health & wellness — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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
9 measurements spanning 24 days, net +84. 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 6,874–6,984 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
15 Sept 2026, 09:19
6,971
+26
11 Sept 2026, 23:41
6,945
+15
7 Sept 2026, 05:35
6,930
+12
2 Sept 2026, 08:36
6,918
+15
30 Aug 2026, 06:06
6,903
+2
27 Aug 2026, 01:37
6,901
+12
24 Aug 2026, 03:49
6,889
+2
22 Aug 2026, 16:00
6,887
no change
22 Aug 2026, 15:45
6,887
first reading
Engagement
9 posts held, back to 18 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 9 posts for this entry, the most recent from 20 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
20 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 70.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
14
70.0%
🕊
6
30.0%
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 4 of the 9 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 20 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 18 August 2026 to 20 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.
Showing the 9 most recent of 9 posts we hold for @huhfcsh. 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Picture Universe @Oromia8Bureau · 33,945 Telegram ranks this channel #8 of 65 here — alongside 64 others — read 7 September 2026
Fresh መረጃ | FreshNews @freshmerejaet · 54,730 Telegram ranks this channel #36 of 73 here — alongside 72 others — read 23 August 2026
BBC News Afaan Oromoo @bbcAfaanOromoo · 51,780 Telegram ranks this channel #38 of 73 here — alongside 72 others — read 24 August 2026
Oromia Health Bureau @ORHBcommunication · 26,599 Telegram ranks this channel #40 of 73 here — alongside 72 others — read 12 September 2026
Nuuralhudaa @nuuralhudaa1 · 25,703 Telegram ranks this channel #44 of 61 here — alongside 60 others — read 13 September 2026
Crypto Horizon @Ethiopian_Education · 29,485 Telegram ranks this channel #44 of 64 here — alongside 63 others — read 11 September 2026
QUBEE MEDIA @Qubee_Media_Official · 62,371 Telegram ranks this channel #49 of 57 here — alongside 56 others — read 22 August 2026
This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 September 2026 — this
entry's latest reading, not the date you are reading this.
“Haramaya University Hiwot Fana Comprehensive Specialized Hospital” (@huhfcsh), 6,971 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/huhfcsh.
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.
