Channel
@COWASHIV
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
561subscribers
+7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001807606299 |
|---|---|
| Type | Channel |
| Username | @COWASHIV |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 4 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 4 October 2026 |
| On Telegram | t.me/COWASHIV |
Other / unclassifiable — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 75% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Oct 2026, 15:14 | 561 | +1 |
| 19 Sept 2026, 16:00 | 560 | +6 |
| 10 Sept 2026, 09:57 | 554 | +1 |
| 31 Aug 2026, 07:47 | 553 | -1 |
| 24 Aug 2026, 16:53 | 554 | +2 |
| 16 Aug 2026, 05:06 | 552 | -2 |
| 8 Aug 2026, 03:35 | 554 | no change |
| 7 Aug 2026, 20:39 | 554 | first reading |
15 posts held, back to 30 June 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 15 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
51 reactions across 13 posts, in 2 distinct kinds. The most used accounts for 88.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 45 | 88.2% | |
| ❤ | 6 | 11.8% |
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 14 of the 15 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 51 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 30 June 2026 to 6 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.
Water security is deeply tied to social inclusion. COWASH IV actively integrates gender and disability-focused strategies to help ensure that water points, hygiene and sanitation facilities are accessible to all.👥 From women and people with disabilities taking leading roles in Water, Sanitation and Hygiene (WASH) committee management to dedicated Menstrual Hygiene Management facilities in schools, as well as inclusi…
👍2
Safe water requires proactive measures. 🚰 Under COWASH IV, Water Safety Planning and routine water quality monitoring are core components of every new water point. By integrating environmental protection, such as green legacy efforts, with rigorous safety measures, #COWASH ensure that rural communities have access to safe, climate-resilient sustainable water sources. To learn more about our work: Visit our website …
👍3
COWASH Regional Impact Series: Tigray 💧📍 The COWASH project in Tigray began during its first phase in 2011 initially covering the then Ofla and Enda Mokoni Woredas. By its third phase, the project had expanded to seven Woredas. Following the peace agreement in Tigray, a Memorandum of Understanding was signed between the Ministry of Finance and the Tigray Bureau of Finance on 02 June 2023 which enabled COWASH IV to c…
❤3👍2
Building a water scheme is only the first step. Ensuring it keeps flowing for years to come requires community ownership and sustainability, and that starts with transparent community-led water tariff systems where households pay agreed sum whenever they collect water. 🚰 Managed by local Water, Sanitation and Hygiene committees, these systems ensure funds are always ready for operation, site protection, prompt maint…
👍4
Quality healthcare cannot be achieved without reliable access to safe water and sanitation facilities. 🏥 Recognizing this as a core focus area, COWASH IV constructs improved latrines and water points in rural health posts across #Ethiopia, delivering safe, reliable facilities for both health workers and visiting patients.💧 While upgraded infrastructure is critical for service delivery and patient dignity, lasting im…
👍2
COWASH Regional Impact Series: South-west Ethiopia People’s Region📍💧 South-west Ethiopia People’s Regional State (SWEPRS) is one of the eight project regions of COWASH IV. In this region, COWASH IV works in two woredas, Kechi and Mari Mansa in Dawro Zone. The project began operation in these Woredas in the 2013 Ethiopian Fiscal Year, when the Woredas were under the then South Nation and Nationalities and People’s Reg…
👍3
In WASH, infrastructure and financial access are most effective when paired with continuous community dialogue.💧🗣 COWASH IV is achieving this by combining its Saving and Loan Associations (SLAs) with its Community Conversation (CC) initiative to accelerate the construction of improved household latrines. While SLAs focus on providing the financial access necessary to empower households to invest in sanitation, the C…
👍2
COWASH Regional Impact Series: South Ethiopia Region 📍 COWASH IV works in four woredas in South Ethiopia Region: Gacho Baba and Kucha Alfa in Gamo Zone and Geze Gofa and Melo Gada in Gofa Zone. The project started working in these woredas in 2021 and has taken swift action to ensure the continuation of critical WASH services following the 2023 regional restructuring that established South Ethiopia Region. Here's th…
👍5❤3
COWASH: 1.2Million People, 8 Regions, 1 Proven Approach.💧 As COWASH IV moves through its final year, we’re reflecting on the power of the Community Managed Project (#CMP) Approach. By shifting the power of finance and management directly to the communities, #COWASH hasn’t just built infrastructure, it has built ownership. 👇 The impact so far: 🔹 1,222,937 people have been served with safe, climate-resilient community…
COWASH Training Programme Update: Strengthening Sanitation in South Ethiopia Region💧👩🏫 From June 30 to July 2, 2026, the COWASH IV team conducted a targeted On-the-Job Training programme in South Ethiopia Region. The training focused on the work progress, financial status, and long-term sustainability of Saving and Loan Associations (SLAs) in Gacho Baba and Geze Gofa Woredas. A total of 14 participants from SLA gro…
👍4
COWASH IV Regional Impact Series: Sidama 💧📍 COWASH's journey in Sidama began in 2014, during the second phase the project. Back then, the region operated under zonal administration within the Southern National, Nationalities and Peoples Region (SNNPR). Initially focusing on two woredas, Gorche and Arbe Gona, #COWASH played a key role in improving #WASH access. Following the restructuring of SNNPR, Sidama joined COWA…
👍4
How do you make improved sanitation affordable for rural communities? One way is to build a bridge between local savings, microfinance institutions and small businesses. 🤝 In Central Ethiopia's Tembaro Special Woreda, a successful alternative financing model for sanitation is emerging.📍Through a collaboration between the local community, COWASH IV, and VisionFund Microfinance Institution, communities in this Woreda …
👍6
Showing the 12 most recent of 15 posts we hold for @COWASHIV. 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.
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 4 October 2026 — this entry's latest reading, not the date you are reading this.
“COWASH IV Ethiopia” (@COWASHIV), 561 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/COWASHIV.
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.