Channel
کلیپ بختیاری🤍
@clip_bakhtiyari1
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,434subscribers
-13 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001901784447 |
|---|---|
| Type | Channel |
| Username | @clip_bakhtiyari1 |
| Created | Between 1 March 2023 and 31 January 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/clip_bakhtiyari1 |
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 82% 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, 21:21 | 3,434 | +10 |
| 14 Sept 2026, 06:16 | 3,424 | -5 |
| 10 Sept 2026, 16:15 | 3,429 | -12 |
| 8 Sept 2026, 20:08 | 3,441 | no change |
| 5 Sept 2026, 20:57 | 3,441 | -1 |
| 1 Sept 2026, 21:25 | 3,442 | +4 |
| 29 Aug 2026, 22:28 | 3,438 | +2 |
| 27 Aug 2026, 07:35 | 3,436 | -2 |
| 24 Aug 2026, 06:48 | 3,438 | +5 |
| 20 Aug 2026, 04:15 | 3,433 | -9 |
| 17 Aug 2026, 11:39 | 3,442 | -4 |
| 13 Aug 2026, 16:08 | 3,446 | -1 |
| 12 Aug 2026, 20:30 | 3,447 | 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.
@ghasem_fazeli · 150,353
Telegram ranks this channel #10 of 89 here — alongside 88 others — read 14 August 2026
@ghasemfazeliii · 86,013
Telegram ranks this channel #11 of 72 here — alongside 71 others — read 18 August 2026
@MusicoRemixam · 149,659
Telegram ranks this channel #11 of 64 here — alongside 63 others — read 12 August 2026
@mohamadzamani58 · 21,800
Telegram ranks this channel #22 of 61 here — alongside 60 others — read 22 September 2026
@shomall_music_orginal · 56,746
Telegram ranks this channel #23 of 78 here — alongside 77 others — read 24 August 2026
@mahali_delbaran · 59,186
Telegram ranks this channel #25 of 73 here — alongside 72 others — read 22 August 2026
This channel appears in 6 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.
“کلیپ بختیاری🤍” (@clip_bakhtiyari1), 3,434 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/clip_bakhtiyari1.
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.