Telegram RegisterThe public register of Telegram
Telegram profile photo for بات ادمین

Channel

بات ادمین

@boT_afghan_EdaLat

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

1subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1001508087657
TypeChannel
Username@boT_afghan_EdaLat
Created10 July 2021measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live11 September 2026
Measurements held2
On Telegramt.me/boT_afghan_EdaLat

Growth

112 August 2026 — 1 subscribers15 August 2026 — 1 subscribers12 August 202615 August 2026
2 measurements spanning 3 days. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 10:151no change
12 Aug 2026, 14:471first reading

Engagement

7 posts held, back to 10 July 2021the 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 7 posts for this entry, the most recent from 20 July 2021. An engagement rate over an empty window would be a number about nothing.

Recent posts

20 Jul 2021, 09:14 UTC54 viewsread 15 August 2026

𝗔𝗙𝗚𝗛𝗔𝗡_𝗘𝗗𝗔𝗟𝗔𝗧: ⚡️#Arash boT @Arash_Takpar_bot id @Khaleq_bozorg_telegram ✨channel @afghan_EdaLat

13 Jul 2021, 19:05 UTC594 viewsread 15 August 2026

✨ #YaSiN boT @YaSiN_YaGhiM_boT id ༒@OsTuRe_aFqaN༒ ⚡️channel @afghan_EdaLat

12 Jul 2021, 20:54 UTC114 viewsread 15 August 2026

✨ #hamid boT @Shah_pesar_bangi_bot id @shah_pesar_bangi channel @afghan_EdaLat

12 Jul 2021, 20:51 UTC79 viewsread 15 August 2026

⚡️nam #Arin_Ravani iD @arian_afghanm 〽️#Davar channel @afghan_EdaLat

11 Jul 2021, 14:08 UTC324 viewsread 15 August 2026

𝗔𝗙𝗚𝗛𝗔𝗡_𝗘𝗗𝗔𝗟𝗔𝗧: ⚡️#MhMd boT @MhMd_ReZaLt_BoT id @mohamad_ReZaLt channel @afghan_EdaLat

10 Jul 2021, 21:29 UTC187 viewsread 15 August 2026

✨ #aMir boT @tars_andaz_bot id @drdastres channel @afghan_EdaLat

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

Mentions

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

“بات ادمین” (@boT_afghan_EdaLat), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/boT_afghan_EdaLat.

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.