Channel
Daniyal gelardi 🔹️دانیال گلردی🔹️
@danial_gelardi_music
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,129subscribers
+200 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001813035228 |
|---|---|
| Type | Channel |
| Username | @danial_gelardi_music |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/danial_gelardi_music |
Topic
Other / unclassifiable — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 22:36 | 3,129 | +28 |
| 14 Sept 2026, 07:15 | 3,101 | +9 |
| 10 Sept 2026, 23:59 | 3,092 | +16 |
| 10 Sept 2026, 23:49 | 3,076 | no change |
| 6 Sept 2026, 09:17 | 3,076 | -1 |
| 1 Sept 2026, 17:08 | 3,077 | -3 |
| 30 Aug 2026, 00:13 | 3,080 | +7 |
| 27 Aug 2026, 06:54 | 3,073 | +47 |
| 24 Aug 2026, 12:58 | 3,026 | +57 |
| 21 Aug 2026, 02:36 | 2,969 | +3 |
| 17 Aug 2026, 19:39 | 2,966 | +42 |
| 14 Aug 2026, 23:05 | 2,924 | -7 |
| 11 Aug 2026, 11:53 | 2,931 | +2 |
| 10 Aug 2026, 23:15 | 2,929 | 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.
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.
@musicdel_ir · 495,829
Telegram ranks this channel #12 of 58 here — alongside 57 others — read 10 August 2026
@raminyadollazadeh · 28,747
Telegram ranks this channel #21 of 76 here — alongside 75 others — read 12 September 2026
@ahangmazani_cLlp · 43,242
Telegram ranks this channel #35 of 85 here — alongside 84 others — read 29 August 2026
@rimix_mazni · 25,626
Telegram ranks this channel #51 of 86 here — alongside 85 others — read 14 September 2026
@boghzmazandaran · 60,830
Telegram ranks this channel #73 of 93 here — alongside 92 others — read 25 August 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Daniyal gelardi 🔹️دانیال گلردی🔹️” (@danial_gelardi_music), 3,129 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/danial_gelardi_music.
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.