Channel
Bs_soul🤍
@bs_soul
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,473subscribers
-76 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001773955419 |
|---|---|
| Type | Channel |
| Username | @bs_soul |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 September 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/bs_soul |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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 |
|---|---|---|
| 2 Nov 2026, 23:47 | 2,473 | -8 |
| 30 Oct 2026, 14:16 | 2,481 | -2 |
| 27 Oct 2026, 14:16 | 2,483 | +2 |
| 24 Oct 2026, 08:35 | 2,481 | -1 |
| 21 Oct 2026, 02:06 | 2,482 | +2 |
| 18 Oct 2026, 02:08 | 2,480 | -4 |
| 15 Oct 2026, 08:29 | 2,484 | -8 |
| 12 Oct 2026, 10:18 | 2,492 | -23 |
| 5 Oct 2026, 16:56 | 2,515 | +5 |
| 28 Sept 2026, 06:41 | 2,510 | -2 |
| 18 Sept 2026, 21:41 | 2,512 | -6 |
| 15 Sept 2026, 14:40 | 2,518 | no change |
| 14 Sept 2026, 17:20 | 2,518 | -6 |
| 10 Sept 2026, 21:59 | 2,524 | -11 |
| 6 Sept 2026, 01:42 | 2,535 | -6 |
| 2 Sept 2026, 03:48 | 2,541 | -6 |
| 29 Aug 2026, 19:03 | 2,547 | -3 |
| 26 Aug 2026, 09:57 | 2,550 | -2 |
| 23 Aug 2026, 08:52 | 2,552 | +8 |
| 19 Aug 2026, 13:44 | 2,544 | 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.
@azizon_uz · 54,861
Telegram ranks this channel #12 of 41 here — alongside 40 others — read 23 August 2026
@zarmeduni · 34,216
Telegram ranks this channel #49 of 62 here — alongside 61 others — read 31 August 2026
@samarkand_rabota1 · 13
Telegram ranks this channel #63 of 70 here — alongside 69 others — read 5 October 2026
@Samarqandliklar_24uzb · 117,139
Telegram ranks this channel #63 of 64 here — alongside 63 others — read 19 August 2026
This channel appears in 4 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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“Bs_soul🤍” (@bs_soul), 2,473 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/bs_soul.
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.