Channel
Dj_fred🎼🎧🎸
@djfredir
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,235subscribers
+133 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001358493608 |
|---|---|
| Type | Channel |
| Username | @djfredir |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 4 times, most recently 5 November 2026 |
| On Telegram | t.me/djfredir |
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 18 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 |
|---|---|---|
| 26 Oct 2026, 17:35 | 2,235 | +1 |
| 24 Oct 2026, 01:39 | 2,234 | +1 |
| 20 Oct 2026, 22:36 | 2,233 | -3 |
| 18 Oct 2026, 00:15 | 2,236 | -2 |
| 14 Oct 2026, 18:48 | 2,238 | +4 |
| 10 Oct 2026, 23:20 | 2,234 | -1 |
| 4 Oct 2026, 16:22 | 2,235 | +10 |
| 24 Sept 2026, 22:37 | 2,225 | +11 |
| 18 Sept 2026, 15:13 | 2,214 | no change |
| 15 Sept 2026, 12:01 | 2,214 | +5 |
| 11 Sept 2026, 18:55 | 2,209 | +14 |
| 7 Sept 2026, 04:39 | 2,195 | +3 |
| 2 Sept 2026, 16:03 | 2,192 | +2 |
| 30 Aug 2026, 15:07 | 2,190 | +11 |
| 27 Aug 2026, 06:18 | 2,179 | +71 |
| 24 Aug 2026, 07:05 | 2,108 | +4 |
| 20 Aug 2026, 05:12 | 2,104 | -1 |
| 16 Aug 2026, 20:15 | 2,105 | +3 |
| 15 Aug 2026, 11:21 | 2,102 | 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.
@madword66 · 27,020
Telegram ranks this channel #7 of 53 here — alongside 52 others — read 22 September 2026
@nexdjcom · 21,089
Telegram ranks this channel #12 of 68 here — alongside 67 others — read 22 September 2026
@amirtatalooriginaal · 50,261
Telegram ranks this channel #13 of 30 here — alongside 29 others — read 28 August 2026
@DjBAD · 112,627
Telegram ranks this channel #41 of 85 here — alongside 84 others — read 15 August 2026
@solidance · 99,426
Telegram ranks this channel #45 of 83 here — alongside 82 others — read 15 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 26 October 2026 — this entry's latest reading, not the date you are reading this.
“Dj_fred🎼🎧🎸” (@djfredir), 2,235 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/djfredir.
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.