Telegram RegisterThe public register of Telegram
Telegram profile photo for የደስታዬ እልልታ - Yedestaye Elilta

Channel

የደስታዬ እልልታ - Yedestaye Elilta

@yedestaye_elilta

Has discussion group

On this record: Growth · Engagement · Citations · Telegram's recommendations · Cite this entry

50,880subscribers

+70 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001139747863
TypeChannel
Username@yedestaye_elilta
Created18 October 2017measured — cross-checked against a third-party dataset (TGDataset)
First recorded12 August 2026
Last confirmed live19 August 2026
Measurements held15
Confirmed unchanged1 time, most recently 19 August 2026
On Telegramt.me/yedestaye_elilta

Growth

50,80750,88050,843.56 August 2026 — 50,810 subscribers6 August 2026 — 50,807 subscribers7 August 2026 — 50,818 subscribers8 August 2026 — 50,827 subscribers9 August 2026 — 50,832 subscribers10 August 2026 — 50,829 subscribers11 August 2026 — 50,825 subscribers12 August 2026 — 50,825 subscribers12 August 2026 — 50,843 subscribers13 August 2026 — 50,848 subscribers14 August 2026 — 50,849 subscribers16 August 2026 — 50,858 subscribers17 August 2026 — 50,873 subscribers18 August 2026 — 50,879 subscribers19 August 2026 — 50,880 subscribers6 August 202619 August 2026
15 measurements spanning 14 days, net +70. 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 50,796–50,891 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Aug 2026, 21:3450,880+1
18 Aug 2026, 17:5450,879+6
17 Aug 2026, 14:2950,873+15
16 Aug 2026, 06:5750,858+9
14 Aug 2026, 19:3650,849+1
13 Aug 2026, 10:2850,848+5
12 Aug 2026, 11:2350,843+18
12 Aug 2026, 03:0550,825no change
11 Aug 2026, 09:2350,825-4
10 Aug 2026, 09:3550,829-3
9 Aug 2026, 06:4250,832+5
8 Aug 2026, 07:2750,827+9
7 Aug 2026, 07:0550,818+11
6 Aug 2026, 09:3150,807-3
6 Aug 2026, 03:5350,810first reading

Engagement

No public post preview. We read this entry on 12 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Citation-graph rank

Citation-graph rank — 401,216 of 1,565,402entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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.

Dr. Eyob Mamo
@Dreyob · 79,320
Telegram ranks this channel #64 of 83 here — alongside 82 others — read 19 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 19 August 2026 — this entry's latest reading, not the date you are reading this.

“የደስታዬ እልልታ - Yedestaye Elilta” (@yedestaye_elilta), 50,880 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/yedestaye_elilta.

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.