Bot
آهنگیفای
@ahangify_bot
On this record: Topic · Growth · Engagement · Citations · Cite this entry
284,348monthly users
-5,488 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
Register entry
| Telegram ID | 359788243 |
|---|---|
| Type | Bot |
| Username | @ahangify_bot |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 60 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/ahangify_bot |
Topic
Music — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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) | Monthly users | Change |
|---|---|---|
| 11 Nov 2026, 02:56 | 284,348 | -676 |
| 9 Nov 2026, 10:16 | 285,024 | +4,118 |
| 7 Nov 2026, 23:55 | 280,906 | -3,573 |
| 5 Nov 2026, 23:16 | 284,479 | +277 |
| 5 Nov 2026, 00:26 | 284,202 | +353 |
| 3 Nov 2026, 23:10 | 283,849 | +679 |
| 2 Nov 2026, 21:04 | 283,170 | +1,089 |
| 1 Nov 2026, 21:46 | 282,081 | +572 |
| 31 Oct 2026, 20:28 | 281,509 | +1,939 |
| 30 Oct 2026, 23:27 | 279,570 | +1,803 |
| 29 Oct 2026, 20:19 | 277,767 | +1,194 |
| 28 Oct 2026, 16:50 | 276,573 | -99 |
| 27 Oct 2026, 16:21 | 276,672 | -116 |
| 26 Oct 2026, 18:20 | 276,788 | -157 |
| 25 Oct 2026, 19:57 | 276,945 | +456 |
| 24 Oct 2026, 18:48 | 276,489 | +496 |
| 23 Oct 2026, 21:45 | 275,993 | +32 |
| 23 Oct 2026, 00:08 | 275,961 | -412 |
| 21 Oct 2026, 23:01 | 276,373 | -598 |
| 20 Oct 2026, 15:58 | 276,971 | first reading |
Engagement
No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@Adabvadanesh · 2723 postsصدای دهبالا. _ یزد (سامانه تلگرامی خبری )
@dehbala_yazd_ir · 8343 postsمنصوره بادآهنگ 🍏SEEB TORSH 🍏
@seeb_torsh · 1363 postsSam PlayList
@Samonmusic · 12 postsle délice
@moodelice · 912 postsکانال تیک تاک و استوری❤😍
@Tik_Tak2022 · 8631 postposhteh
@ali_sheybanee · 4081 postاز الف تا یای ویراستاری |کارآموزیهایی در ویرایش
@alphaze · 7581 postمزون
@araposhmezon · 831 postCRY✨
@crystalcrap · 4711 post❌⚔گایشگاه گذره⚔❌
@gayeshgah_gozreh · 1621 postنگــــــــــــاه کــــــــویـــــــــــر
@kavirmot · 2071 post📚 لابهلای سطرها
@labelaye_satrha · 7231 postMahdis_the_notetaker
@mah77755 · 2661 postTuska
@tuskaartworks · 2641 post
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 355 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@funzaban · 33,88329 postsآموزش دنس
@hiphopdance_ir · 728 posts🌻کانال رکاب زنان آفتابگردان🌻
@SunflowerCyclists · 2158 postsآذرالسلطنه
@mahisefatazar · 22,2877 postsIran Fender
@iran_fender · 6226 postsAlp
@alpplaylist · 7505 posts~: 𝑟𝑦𝑏𝑒𝑟 :~
@Creator_Ryber · 35 posts.
@Jeweleryzarkade · 45 postsفرآوردهای روغنی ناب
@naab_product · 165 postsShkibaam💕
@shkibaam · 9,3195 posts♡|• آسایشگاه •|♡
@Asayeshgah_delnevesht · 34 postsClem
@DeviantHunter · 294 postsMusic the best
@musicthebest001 · 24 postsلینکدونی پسرکده
@pesar_kade · 14,9234 postsداستان یکشنبه
@sundaystory1 · 1284 posts❀ 𝐓𝐢𝐓𝐢𝐥𝐚𝐧𝐝 ❀
@tanyazabetian · 9904 postsAdab va Danesh
@Adabvadanesh · 2723 postsAhadis
@ahadisalavi · 53 postsHindi_urdu UT
@hindi_urdu · 293 postsیاسمن رحمانی
@rahmanipoem · 1273 postsSorloot Life Style
@sorloot · 4753 postspaperback
@swingerofbirchess · 9,5143 postsوَهْم
@vahamat · 3403 postsکانال رسمی وحیداکجوان
@vahidakjavanmusic0831 · 563 posts
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“آهنگیفای” (@ahangify_bot), 284,348 monthly users as measured 11 November 2026. Telegram Register, tgregister.com/channel/ahangify_bot.
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.