Telegram RegisterThe public register of Telegram

Channel

አቶ Codes

@atocodes

On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry

759subscribers

+2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002115493544
TypeChannel
Username@atocodes
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/atocodes

Growth

7577597587 Aug 2026, 02:45 — 757 subscribers7 Aug 2026, 15:35 — 759 subscribers7 Aug 2026, 02:457 Aug 2026, 15:35
2 measurements taken within a single day, net +2. 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 757–759 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 15:35759+2
7 Aug 2026, 02:45757first reading

Engagement

15 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
12.8%
avg views ÷ 759 subscribers
Avg views / post
96.9
15 posts measured
Reaction rate
2.00%
reactions ÷ views · ER floor
Posts in window
15
of 15 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 8 of 15 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held15 (5 August 20266 August 2026)
Views total1,454
Reactions total17
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 02:45 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

17 reactions across 8 posts, in 6 distinct kinds. The most used accounts for 35.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥635.3%
👍423.5%
317.6%
😭211.8%
😁15.88%
😢15.88%

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 8 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 17reactions 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 5 August 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.

Recent posts

6 Aug 2026, 17:48 UTC90 views2 reactionsread 7 August 2026

And mebrat teftwal eja bloc 😭😭😭 Let's Support Abel ❤️

😭2

6 Aug 2026, 17:44 UTC90 views4 reactionsread 7 August 2026
Photo

Waiting for my interviewer to join Let's Support Abel ❤️

🔥4

6 Aug 2026, 14:56 UTC102 views1 reactionsread 7 August 2026

Which makes me married to 3 to 5 i guess Let's Support Abel ❤️

😁1

6 Aug 2026, 12:29 UTC120 views2 reactionsread 7 August 2026

Jemaw For the past few days I've been working on integrating an automated payment system for Equib Manager using my own npm package Ethio Receipt Parser. The package itself was working fine, but I ran into a problem. The server where it's hosted is outside Ethiopia, and it looks like Ethio Telecom doesn't accept requests coming from foreign servers (at least that's what I could understand from the past production f

2

6 Aug 2026, 11:00 UTC42 viewsread 7 August 2026
Forwarded from @CoolioCodes

hey it's me Coolio, you might know me from the community hike events i've hosted multiple times. (one coming very soon aswell so join up) so i ..... deleted my channel by mistake. i was trying to delete a post and instead deleted the whole channel smh. anyways this is my new channel engdi. we keep going, we keep growing. share this around the community and lets keep the momentum going ❤️ @CoolioCodes

6 Aug 2026, 04:40 UTC136 views1 reactionsread 7 August 2026

This is one of the reason why i hate Microsoft Oversized and overcomplicated Let's Support Abel ❤️

😢1

6 Aug 2026, 04:37 UTC128 viewsread 7 August 2026

When ever am testing my apps I test them not only in development but also in production environemnt and thats Where i found out the payment feature fails. So am still on building the working on the mobile side now to be testing and push to production Equib Manager V3.5 There are few things ive chnaged here and there anyways back to work #equb_manager Let's Support Abel ❤️

6 Aug 2026, 04:15 UTC119 views1 reactionsread 7 August 2026

This is amazing thing to see Vercil V ethio Let's Support Abel ❤️

1

6 Aug 2026, 04:14 UTC25 viewsread 7 August 2026
Forwarded from @SoloDevChroniclesPhoto

Introducing EthioDeploy Deploying applications shouldn't require hours of server setup, DevOps knowledge, or an international credit card. We built this to make hosting simple for developers, startups, and businesses. Connect your GitHub repository, push your code, and your application is online in seconds. Here's what you get with EthioDeploy: 1. Automatic stack detection Works out of the box with Next.js, Re

Showing the 12 most recent of 15 posts we hold for @atocodes. 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.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

5 Aug 2026, 11:57 UTCAnonymous Poll10 voters

Weekly Audio SMA stream ?

  1. 🔥 Yes, I enjoyed the last one50%
  2. 🤔 Maybe sometimes30%
  3. 😅 Keep it text only20%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 15 most recent posts we hold, published 5 August 2026 to 6 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 212,841 of 1,183,361entries 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.

Republishes

Channels on the register whose posts this channel has forwarded.

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 5 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.

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.

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 7 August 2026 — this entry's latest reading, not the date you are reading this.

“አቶ Codes” (@atocodes), 759 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/atocodes.

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.