Channel
𝑹𝒂𝒎𝒂𝑴𝒖𝒔𝒊𝒄..
@ramamusic_ir
On this record: Topic · Growth · Engagement · Citations · Telegram's recommendations · Cite this entry
2,716subscribers
+131 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001178787189 |
|---|---|
| Type | Channel |
| Username | @ramamusic_ir |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 September 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/ramamusic_ir |
Topic
Music — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 15 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 13:17 | 2,716 | -2 |
| 6 Nov 2026, 14:45 | 2,718 | -5 |
| 3 Nov 2026, 11:39 | 2,723 | -13 |
| 31 Oct 2026, 04:30 | 2,736 | -7 |
| 28 Oct 2026, 05:20 | 2,743 | +12 |
| 25 Oct 2026, 01:08 | 2,731 | -4 |
| 22 Oct 2026, 11:46 | 2,735 | +4 |
| 19 Oct 2026, 05:27 | 2,731 | -5 |
| 16 Oct 2026, 06:36 | 2,736 | +11 |
| 12 Oct 2026, 23:59 | 2,725 | +2 |
| 6 Oct 2026, 20:36 | 2,723 | +15 |
| 30 Sept 2026, 06:02 | 2,708 | +40 |
| 16 Sept 2026, 00:22 | 2,668 | +19 |
| 14 Sept 2026, 01:42 | 2,649 | no change |
| 12 Sept 2026, 05:56 | 2,649 | +18 |
| 8 Sept 2026, 10:19 | 2,631 | +22 |
| 3 Sept 2026, 09:42 | 2,609 | +2 |
| 31 Aug 2026, 00:25 | 2,607 | +2 |
| 28 Aug 2026, 06:42 | 2,605 | -3 |
| 25 Aug 2026, 00:18 | 2,608 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Mentions
Named by 50 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.
@Eng_Online · 36,42120 postsمرکز تعمیرات موبایل
@repairms · 23,63113 postsبیمکس دیزایــن | 𝐁𝐦𝐚𝐱𝐝𝐞𝐬𝐢𝐠𝐧
@bmaxdesign · 28,63310 postsمهدی هک | آموزش هک و امنیت™
@Mahdiihack · 20,4877 postsسفارش پروژه | پروژه بگیر 🥇
@prozhebegir_ir · 17,4247 postsEngineeringReverse | مهندسی معکوس
@EngineeringReverse · 21,5946 postsکامپیوتر و نرم‌افزار
@spcware · 13,6556 postsArras and Design
@Design_groooup · 12,6155 postsModirShabake
@modirshabake · 14,4375 posts💻 programmer_best
@programmer_best · 14,8225 postsVOXEL 3D OBJECT
@Voxel3DDVray · 12,8075 postsVoxel Object Revit
@VoxelObjectRevit · 12,0895 postsEnglish Unique | آموزش زبان انگلیسی
@english_uniquee · 19,4054 postsآزمون طراحی معماری نظام مهندسی
@tarrahimemari · 11,6794 postsChilliTech | چیلی تک
@ChilliTech · 10,0193 posts𝗠𝘆𝗱𝗲𝘃𝗶𝗹
@karyabivipmorvarid9 · 1,1963 posts🚨استخدامی فوری تهران و ایران
@estekhdami_fouri · 6,7732 postsفونت برتر
@FontBartar · 113,9332 postsHashtagify! | آموزش هوش مصنوعی
@hashtagifyofficial · 12,8472 postsUnii_kar
@unii_kar · 23,6032 postsآکادمی عصر رایان شبکه
@asrehshabakeh1 · 10,8781 postاستخدام ادمین |پروژه های ادمینی
@moniforosh4 · 4,7101 post🔹️Proje miluni🔹️
@PROAJECTE · 17,0551 postVoxel studios Learning
@VoxelLearn · 30,3891 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.
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.
@Efsha_Bad_Tv · 22,005
Telegram ranks this channel #43 of 64 here — alongside 63 others — read 18 September 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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“𝑹𝒂𝒎𝒂𝑴𝒖𝒔𝒊𝒄..” (@ramamusic_ir), 2,716 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/ramamusic_ir.
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.