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 26 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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
7 measurements spanning 54 days, net -4. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 127–134 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
1 Oct 2026, 00:59
129
+1
17 Sept 2026, 05:21
128
-1
8 Sept 2026, 18:38
129
-1
23 Aug 2026, 05:16
130
-1
16 Aug 2026, 07:23
131
-2
9 Aug 2026, 00:17
133
no change
7 Aug 2026, 17:34
133
first reading
Engagement
3 posts held, back to 24 July 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 3 posts for this entry, the most recent from 29 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
19 reactions across 3 posts, in 7 distinct kinds. The most used accounts for 31.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5244736692887236286
6
31.6%
custom 5368730848239564636
4
21.1%
custom 5271715474122485320
2
10.5%
custom 5341779490370499257
2
10.5%
custom 5409040662500752483
2
10.5%
custom 5411260095440901888
2
10.5%
🔥
1
5.26%
Custom emoji. 6 of the rows above are 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 3 of the 3 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 19 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 24 July 2026 to 29 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.
Вернулась к большому и, что уж скрывать, дорогому во всех отношениях проекту — спойлер на фото)
Одно украшение из серии уже готово и выгуляно, но руки так и не дошли собрать красивый рилс 🤦🏻♀️🫠
Честно признаюсь, иногда устаю от определенных материалов и техник — и тогда беру перерыв, чтобы упорядочить хаос или просто поработать в других техниках.
Так случилось и в этот раз с бисером:
кажется, весь июль душа не ле…
Никакой серьезность в это утро понедельника — только чистый модный дофамин и яблочки из акрила! 🖤
Меня бесконечно забавляют эти бусинки и признаться честно — свой яблонный сад я в последнее время не снимаю примерно никогда 🥰
Осталось только решить: фруктовое ассорти или яблочный минимализм?
💙 Заказ: сообщения канала или личное сообщение мне — @liwexy
Ну что, фанаты морского стиля и ракушечного безумия на базе?)
Влюбилась в эти керамические ракушки еще зимой и к середине лета, наконец-то, собрала эти чокеры — ничего лишнего, только пойманное в бусины солнце и настроение быть самой загорелой девчонкой на планете ✨
💙 Заказ: сообщения канала или личное сообщение мне — @liwexy
Чокер из ракушек: 2500₽
Чокер с жемчугом: 3100₽
Серьги: 2300₽
Showing the 3 most recent of 3 posts we hold for @li_made. 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 1 October 2026 — this
entry's latest reading, not the date you are reading this.
“Li_Made ✨ Треугольники и другие искры” (@li_made), 129 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/li_made.
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.
