Bot
پایه یازدهم
@Fileyazbot
On this record: Growth · Engagement · Citations · Cite this entry
11,343monthly users
-5,092 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | 7666954171 |
|---|---|
| Type | Bot |
| Username | @Fileyazbot |
| First recorded | 20 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 2 times, most recently 25 August 2026 |
| On Telegram | t.me/Fileyazbot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 24 Aug 2026, 00:04 | 11,343 | -1,026 |
| 20 Aug 2026, 21:44 | 12,369 | -595 |
| 20 Aug 2026, 10:03 | 12,964 | no change |
| 19 Aug 2026, 18:34 | 12,964 | -689 |
| 16 Aug 2026, 08:35 | 13,653 | -234 |
| 14 Aug 2026, 17:08 | 13,887 | -556 |
| 13 Aug 2026, 10:14 | 14,443 | -450 |
| 10 Aug 2026, 09:55 | 14,893 | -557 |
| 9 Aug 2026, 13:01 | 15,450 | -985 |
| 7 Aug 2026, 12:00 | 16,435 | 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.
Mentions
Named by 37 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.
@tarh_dars1405 · 62,11029 postsفیزیک شجاعی
@nf_je · 24,98815 postsزیست فرزام فرهمندنیا
@farhmandni · 42,0909 postsریاضی معین کرمی رایگان
@ryazikarami · 51,2459 postsفیزیک نوکنده رایگان 1405
@fiziknokande1403 · 10,0505 postsزبان قریشی
@ghorishie · 4,1384 postsزیست حنیف عظیمی
@haniif_azimi · 57,0394 postsفیزیک مهدی یحیوی
@yahavi · 27,9533 postsزیست رایگان همدانی 1405
@zisthamdani · 5,8123 postsفیزیک ارسلان رحمانی
@bhuy_147 · 1,8442 postsعربی عمومی و اختصاصی انسانی شاهرودی
@bhuy_165 · 2,3272 postsشیمی هادیان فرد
@bhuy_184 · 3,1012 postsفیزیک شجاعی
@bhuy_183 · 101 postفیزیک مهدی یحیوی
@Fizikk_yahyavii · 6431 postشیمی مومن زاده
@gcftdre · 3161 postزیست غلامی
@hvsjhdo · 6591 postفیزیک کنکور استاد ایرانی
@n_tfo · 7451 postریاضی عزیزی رایگان 1405
@riaziazizie · 3,2091 postشیمی مرادی رایگان
@shimimiradii · 6,8601 postفیلم فیزیک کنکور قضاتی
@vc_qn · 1,7611 postدینی فکری
@yk_we · 5801 postزیست محمد همدانی
@zist_hamedaniii · 2,5911 postزیست و زمین عمارلو رایگان
@zistamarloooe · 3,6191 postزیست خیراندیش
@zistkharandishe · 6481 post
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“پایه یازدهم” (@Fileyazbot), 11,343 monthly users as measured 24 August 2026. Telegram Register, tgregister.com/channel/Fileyazbot.
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.