Channel
Ephrem Diriba
@EphremDiriba
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,271subscribers
-101 since we began measuring on 7 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001371363312 |
|---|---|
| Type | Channel |
| Username | @EphremDiriba |
| Created | Between 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 2 times, most recently 7 November 2026 |
| On Telegram | t.me/EphremDiriba |
Topic
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 26 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 04:19 | 4,271 | -1 |
| 29 Oct 2026, 15:51 | 4,272 | -10 |
| 26 Oct 2026, 12:41 | 4,282 | -6 |
| 23 Oct 2026, 22:46 | 4,288 | -6 |
| 21 Oct 2026, 01:30 | 4,294 | -13 |
| 18 Oct 2026, 01:08 | 4,307 | -5 |
| 14 Oct 2026, 22:49 | 4,312 | -6 |
| 11 Oct 2026, 21:01 | 4,318 | -22 |
| 5 Oct 2026, 02:17 | 4,340 | -8 |
| 26 Sept 2026, 13:57 | 4,348 | -7 |
| 17 Sept 2026, 15:01 | 4,355 | -3 |
| 13 Sept 2026, 13:00 | 4,358 | -9 |
| 10 Sept 2026, 02:15 | 4,367 | -5 |
| 7 Sept 2026, 12:46 | 4,372 | no change |
| 7 Sept 2026, 07:17 | 4,372 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
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.
@Academy_365 · 48,462
Telegram ranks this channel #7 of 47 here — alongside 46 others — read 23 September 2026
@marriage_counseling · 59,601
Telegram ranks this channel #10 of 50 here — alongside 49 others — read 24 September 2026
@matchtalklive · 69,515
Telegram ranks this channel #23 of 40 here — alongside 39 others — read 13 September 2026
@Oromiaeducationbureauo1 · 29,793
Telegram ranks this channel #23 of 52 here — alongside 51 others — read 7 September 2026
@oro_football_troll1 · 30,364
Telegram ranks this channel #29 of 47 here — alongside 46 others — read 14 September 2026
@Reading_PDF · 19,036
Telegram ranks this channel #35 of 57 here — alongside 56 others — read 3 October 2026
This channel appears in 6 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“Ephrem Diriba” (@EphremDiriba), 4,271 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/EphremDiriba.
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.