Leoking pinned a file

Channel
Leoking
@Leoking34
On this record: Topic · Growth · Engagement · Posts · Cite this entry
5,120subscribers
+208 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 | -1001385016262 |
|---|---|
| Type | Channel |
| Username | @Leoking34 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/Leoking34 |
Topic
Ecommerce storefront — 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 99% 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 |
|---|---|---|
| 17 Nov 2026, 08:59 | 5,120 | +10 |
| 11 Nov 2026, 18:50 | 5,110 | +8 |
| 7 Nov 2026, 18:30 | 5,102 | +3 |
| 4 Nov 2026, 08:48 | 5,099 | +6 |
| 31 Oct 2026, 22:19 | 5,093 | -5 |
| 28 Oct 2026, 21:58 | 5,098 | +5 |
| 26 Oct 2026, 06:10 | 5,093 | +4 |
| 23 Oct 2026, 01:57 | 5,089 | +4 |
| 20 Oct 2026, 05:21 | 5,085 | +12 |
| 17 Oct 2026, 15:47 | 5,073 | +8 |
| 15 Oct 2026, 01:29 | 5,065 | +13 |
| 12 Oct 2026, 02:18 | 5,052 | +27 |
| 5 Oct 2026, 04:58 | 5,025 | +25 |
| 27 Sept 2026, 00:37 | 5,000 | +12 |
| 15 Sept 2026, 17:17 | 4,988 | +10 |
| 11 Sept 2026, 23:59 | 4,978 | +18 |
| 7 Sept 2026, 12:38 | 4,960 | +12 |
| 2 Sept 2026, 10:05 | 4,948 | +4 |
| 30 Aug 2026, 01:34 | 4,944 | +13 |
| 27 Aug 2026, 09:37 | 4,931 | first reading |
Engagement
14 posts held, back to 5 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 7 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 14 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
💫🌸Новые модели. Мягкий и качественный велюр. Полный каталог уже доступен.
File, posted without a caption
НОВИНКА! НОВЫЕ ШЕРСТЯНЫЕ ПЛЕДЫ🌨️❄️💨❤️☔️
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
⬆️NEW LUXURY ❤️НОВИНКИ Шерстяные наборы 10 предметов
Photo, posted without a caption
⬆️NEW LUXURY ❤️НОВИНКИ Шерстяные наборы 10 предметов
Photo, posted without a caption
Showing the 12 most recent of 14 posts we hold for @Leoking34. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“Leoking” (@Leoking34), 5,120 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/Leoking34.
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.