Channel
🪬ARCHIVE-ЭЗОкниги- 888📒
@tarotolgabiblioteka
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,753subscribers
+68 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 | -1001786715377 |
|---|---|
| Type | Channel |
| Username | @tarotolgabiblioteka |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 2 times, most recently 16 September 2026 |
| On Telegram | t.me/tarotolgabiblioteka |
Topic
Literature — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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 |
|---|---|---|
| 12 Sept 2026, 12:38 | 5,753 | +9 |
| 8 Sept 2026, 15:59 | 5,744 | +4 |
| 3 Sept 2026, 10:03 | 5,740 | +6 |
| 30 Aug 2026, 18:09 | 5,734 | +7 |
| 30 Aug 2026, 11:58 | 5,727 | no change |
| 27 Aug 2026, 13:05 | 5,727 | +7 |
| 24 Aug 2026, 02:56 | 5,720 | -5 |
| 20 Aug 2026, 20:46 | 5,725 | +8 |
| 17 Aug 2026, 11:04 | 5,717 | +14 |
| 13 Aug 2026, 18:07 | 5,703 | +13 |
| 10 Aug 2026, 12:37 | 5,690 | +6 |
| 7 Aug 2026, 19:13 | 5,684 | -1 |
| 7 Aug 2026, 12:52 | 5,685 | 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.
@Inquizitor_Library · 42,245
Telegram ranks this channel #12 of 71 here — alongside 70 others — read 29 August 2026
@runelor · 20,951
Telegram ranks this channel #22 of 88 here — alongside 87 others — read 25 September 2026
@taro_pedia · 21,742
Telegram ranks this channel #47 of 67 here — alongside 66 others — read 22 September 2026
@karinatarotv · 22,454
Telegram ranks this channel #51 of 77 here — alongside 76 others — read 20 September 2026
@taro_jennifer · 78,397
Telegram ranks this channel #65 of 87 here — alongside 86 others — read 19 August 2026
@lykova_taro · 104,122
Telegram ranks this channel #74 of 84 here — alongside 83 others — read 19 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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“🪬ARCHIVE-ЭЗОкниги- 888📒” (@tarotolgabiblioteka), 5,753 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/tarotolgabiblioteka.
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.