Channel
ππππππππ πΓππππππππ
@muhabbat_bandirgisi
On this record: Topic Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
2,390subscribers
-41 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 | -1001549593033 |
|---|---|
| Type | Channel |
| Username | @muhabbat_bandirgisi |
| Created | Between 1 August 2021 and 28 February 2023 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 16 September 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/muhabbat_bandirgisi |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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 |
|---|---|---|
| 26 Sept 2026, 04:01 | 2,390 | -3 |
| 16 Sept 2026, 21:29 | 2,393 | no change |
| 15 Sept 2026, 03:19 | 2,393 | +1 |
| 11 Sept 2026, 10:38 | 2,392 | -8 |
| 6 Sept 2026, 12:41 | 2,400 | -8 |
| 2 Sept 2026, 03:45 | 2,408 | -4 |
| 29 Aug 2026, 18:37 | 2,412 | +2 |
| 26 Aug 2026, 20:25 | 2,410 | -4 |
| 23 Aug 2026, 14:04 | 2,414 | -9 |
| 19 Aug 2026, 15:32 | 2,423 | +6 |
| 16 Aug 2026, 22:23 | 2,417 | -2 |
| 13 Aug 2026, 23:14 | 2,419 | -9 |
| 10 Aug 2026, 16:05 | 2,428 | -3 |
| 7 Aug 2026, 04:49 | 2,431 | 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.
@paziyletuz Β· 72,178
Telegram ranks this channel #47 of 61 here β alongside 60 others β read 29 August 2026
@www_karsu_uz Β· 28,507
Telegram ranks this channel #66 of 71 here β alongside 70 others β read 9 September 2026
This channel appears in 2 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 September 2026 β this entry's latest reading, not the date you are reading this.
βππππππππ πΓππππππππβ (@muhabbat_bandirgisi), 2,390 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/muhabbat_bandirgisi.
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.