Channel
БИБЛИОТЕКА ТАРО МБК
@mbktarot
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,276subscribers
+71 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001818177692 |
|---|---|
| Type | Channel |
| Username | @mbktarot |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/mbktarot |
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 13 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 |
|---|---|---|
| 6 Nov 2026, 13:20 | 5,276 | +4 |
| 3 Nov 2026, 08:10 | 5,272 | +6 |
| 31 Oct 2026, 05:17 | 5,266 | +1 |
| 27 Oct 2026, 18:59 | 5,265 | +3 |
| 24 Oct 2026, 20:09 | 5,262 | -3 |
| 19 Oct 2026, 07:49 | 5,265 | -1 |
| 15 Oct 2026, 21:39 | 5,266 | +5 |
| 12 Oct 2026, 15:06 | 5,261 | -2 |
| 5 Oct 2026, 17:15 | 5,263 | +7 |
| 27 Sept 2026, 20:22 | 5,256 | +4 |
| 18 Sept 2026, 08:56 | 5,252 | -3 |
| 14 Sept 2026, 02:39 | 5,255 | +4 |
| 10 Sept 2026, 11:01 | 5,251 | +14 |
| 5 Sept 2026, 03:57 | 5,237 | +3 |
| 31 Aug 2026, 22:07 | 5,234 | no change |
| 29 Aug 2026, 22:37 | 5,234 | +2 |
| 27 Aug 2026, 01:54 | 5,232 | +2 |
| 20 Aug 2026, 08:42 | 5,230 | +7 |
| 17 Aug 2026, 17:06 | 5,223 | +11 |
| 14 Aug 2026, 07:34 | 5,212 | 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.
@taro_pedia · 21,447
Telegram ranks this channel #67 of 67 here — alongside 66 others — read 22 September 2026
@Inquizitor_Library · 43,431
Telegram ranks this channel #69 of 71 here — alongside 70 others — read 29 August 2026
@profi_jennifer · 19,127
Telegram ranks this channel #76 of 78 here — alongside 77 others — read 3 October 2026
@tarotman · 19,922
Telegram ranks this channel #78 of 79 here — alongside 78 others — read 29 September 2026
@lykova_taro · 104,009
Telegram ranks this channel #83 of 84 here — alongside 83 others — read 19 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“БИБЛИОТЕКА ТАРО МБК” (@mbktarot), 5,276 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/mbktarot.
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.