Отримали повторно всі розміри 🤍

Channel
Lavi Drop
@lavidrop
On this record: Topic · Growth · Engagement · Posts · Cite this entry
17subscribers
-2,069 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001979648945 |
|---|---|
| Type | Channel |
| Username | @lavidrop |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 4 October 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 4 October 2026 |
| On Telegram | t.me/lavidrop |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 4 Oct 2026, 03:59 | 17 | +6 |
| 18 Sept 2026, 16:41 | 11 | -2,157 |
| 14 Sept 2026, 18:20 | 2,168 | +2 |
| 11 Sept 2026, 10:00 | 2,166 | -1 |
| 6 Sept 2026, 15:38 | 2,167 | +4 |
| 2 Sept 2026, 05:13 | 2,163 | +12 |
| 30 Aug 2026, 14:28 | 2,151 | +33 |
| 27 Aug 2026, 12:58 | 2,118 | +3 |
| 24 Aug 2026, 03:55 | 2,115 | -4 |
| 20 Aug 2026, 05:52 | 2,119 | +1 |
| 17 Aug 2026, 09:36 | 2,118 | +3 |
| 13 Aug 2026, 22:37 | 2,115 | +5 |
| 11 Aug 2026, 00:57 | 2,110 | +24 |
| 7 Aug 2026, 20:32 | 2,086 | no change |
| 7 Aug 2026, 19:38 | 2,086 | first reading |
Engagement
4 posts held, back to 6 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 1 page 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 4 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Must-have цього сезону 🤍 Відкриті плечі, корсетна шнурівка та акцентний крій створюють ефектний образ для будь-якої події✨ Розміри: S, M, L Арт. 102 🔖 1150 грн
Відео 🤩🤩
Вау, це той самий корсет, який робить силует ідеальним 🔥 Лови погляди разом із нами 🖤 • щільна посадка • регулюючі бретелі • металева фурнітура • must-have цього сезону Розміри: S, М, L Білі і чорні Арт. 137 🔖 1100 грн Розмірна сітка 🎀 S: талія 55-65см, довжина по спині 30 см, бюст до 92см М: талія 62-75, довжина по спині 31 см, бюст до 96см L: талія 70-78, довжина 32см, бюст до 102см
Showing the 4 most recent of 4 posts we hold for @lavidrop. 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 4 October 2026 — this entry's latest reading, not the date you are reading this.
“Lavi Drop” (@lavidrop), 17 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/lavidrop.
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.