Posted without readable text
custom 529668690360772656018custom 546315475505434983716custom 546985416530176196016custom 525380018627832517410custom 53662320921013479586custom 52311019799036754333custom 52153311821153009032

Channel
@lumikko_sk
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
212subscribers
+29 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001913630668 |
|---|---|
| Type | Channel |
| Username | @lumikko_sk |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/lumikko_sk |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 22:19 | 212 | -2 |
| 8 Sept 2026, 06:36 | 214 | +2 |
| 29 Aug 2026, 12:28 | 212 | +1 |
| 22 Aug 2026, 07:28 | 211 | +11 |
| 14 Aug 2026, 13:26 | 200 | +17 |
| 8 Aug 2026, 12:31 | 183 | no change |
| 7 Aug 2026, 18:19 | 183 | first reading |
7 posts held, back to 14 May 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 7 posts for this entry, the most recent from 24 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
594 reactions across 7 posts, in 8 distinct kinds. The most used accounts for 24.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5296686903607726560 | 144 | 24.2% | |
| custom 5215331182115300903 | 120 | 20.2% | |
| custom 5463154755054349837 | 108 | 18.2% | |
| custom 5253800186278325174 | 69 | 11.6% | |
| custom 5366232092101347958 | 69 | 11.6% | |
| custom 5469854165301761960 | 45 | 7.58% | |
| custom 5231101979903675433 | 28 | 4.71% | |
| custom 5467501927677857452 | 11 | 1.85% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 7 of the 7 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 594 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 14 May 2026 to 24 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Posted without readable text
custom 529668690360772656018custom 546315475505434983716custom 546985416530176196016custom 525380018627832517410custom 53662320921013479586custom 52311019799036754333custom 52153311821153009032
🔥🔥🔥🔥🔥🔥 🌸🌸🌸🌸🌸🌸🌸🌸🌸🌸 💐💐💐💐💐💐💐💐💐💐💐 👍сейчас занимаюсь подготовкой ткани для нового изделия🤩 🤍ВТО, 🤍раскрой, 🤍дублирование деталей. 🌷надеюсь скоро приступлю к пошиву🤩 🤩 #LUMIKKO_одежда #рабочий_процесс@lumikko_sk #шьюсама #isew #sewing #ручнаяработа #ялюблюшить #хоббидлядуши #handmade
custom 521533118211530090320custom 529668690360772656020custom 525380018627832517418custom 546315475505434983718custom 53662320921013479584custom 52311019799036754333custom 54698541653017619603custom 54675019276778574522
🔥🔥🔥🔥 🌛🌻🦅🌼💫🦊 🩵🌸🌸🌸🌸🩵 ☀️с возвращением меня 🤗 после большого перерыва📖 ☀️где я была, спросите 😎 были сложности со свободным временем🛀 😺но наконец-то я здесь. ☀️Делюсь с вами летним костюмчиком из кулирки на 110 рост📖 💕Предельно простой, но очень сочный 📖 🤔делитесь в комментариях, как проходит ваше лето 🏝️? #готовые_работы@lumikko_sk #sewing #isew #handmade #ялюблюшить #летожара #одеждадлядетей #LUMIKKO_одежда
custom 529668690360772656029custom 536623209210134795823custom 523110197990367543319custom 54698541653017619609custom 52153311821153009035custom 54675019276778574524custom 54631547550543498371
Sticker, posted without a caption
custom 52966869036077265608
Video, posted without a caption
custom 529668690360772656013custom 521533118211530090312custom 54631547550543498376custom 53662320921013479581
🆔🔤🔤🔤🆔 ☀️Хочу поделиться с вами замечательной новостью — у моего хобби появился свой логотип 👍💚 ⏺️Теперь у LUMIKKO есть не только идеи, ткани и строчки, но и своё лицо ☺️ 💕Сейчас я шью для своей семьи — с любовью, вдохновением и огромным удовольствием. 🛎️Одним из первых изделий с новым логотипом стал летний костюм для моего маленького модника👦 🤩Каждая вещь для меня — это не просто одежда. Это тепло рук, внимание к …
custom 529668690360772656053custom 546315475505434983752custom 521533118211530090341custom 546985416530176196011custom 52311019799036754332custom 52538001862783251742custom 53662320921013479581
🌸🐒🌛🌛🐒🍎 🔥🔥🔥🔥🔥🔥🔥🔥🔥 💥 очень давно я делилась процессом пошива жилета 👍 🆗 наконец-то вылаживаю фото уже законченного изделия👍 😱Итак скажу, это самое сложное, что я шила, потому что: 1️⃣ изделие на подкладке; 2️⃣ инструкция только в виде фото и пошаговым описанием, на умном профессиональном для швеи языке, 50+ страниц🤯 когда первый раз прочитала совсем ничего не поняла😳 но на 20 раз стало немного проясняться 🤔 3️⃣на од…
custom 521533118211530090340custom 525380018627832517439custom 536623209210134795834custom 546315475505434983715custom 54698541653017619606custom 54675019276778574525custom 52966869036077265603custom 52311019799036754331
Showing the 7 most recent of 7 posts we hold for @lumikko_sk. 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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Lumikko - шью в удовольствие, ткани с принтом, пряжа, мк, выкройки 🪡✨” (@lumikko_sk), 212 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/lumikko_sk.
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.