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 20 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
10 measurements spanning 62 days, net -39. 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 803–854 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
8 Oct 2026, 14:00
809
-10
27 Sept 2026, 08:00
819
-6
10 Sept 2026, 19:17
825
-2
2 Sept 2026, 14:35
827
-6
27 Aug 2026, 06:13
833
-6
20 Aug 2026, 12:42
839
-3
14 Aug 2026, 09:37
842
-5
8 Aug 2026, 01:19
847
no change
8 Aug 2026, 00:26
847
-1
7 Aug 2026, 14:47
848
first reading
Engagement
7 posts held, back to 25 June 2024 — 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
80 reactions across 3 posts, in 7 distinct kinds. The most used accounts for 43.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5332698589476979039
35
43.8%
custom 5330547798704149707
11
13.8%
custom 5467738640505411621
11
13.8%
💘
11
13.8%
💋
8
10.0%
❤🔥
3
3.75%
❤
1
1.25%
Custom emoji. 3 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 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 80 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 25 June 2024 to 6 August 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.
всем приветик, мои хорошие!!😒
✨ не пугайтесь, мне не снесли канал или что-то подобное, это я вернулась и решила начать все с чистого листа, ведь очень соскучилась по вам за время моего отсутствия 😱
🌟и вернулась я не с пустыми руками, а с новыми идеями и украшениями! а ещее скоро планируется розыгрыш, но не буду рассказывать все сразу, сами увидите 🌟
🤍🤍🤍🤍🤍🤍🤍🤍
так что включайте уведомления и ждите новый дроп,…
📝📝📝📝📝📝📝📝 • ria_jwll
через пвз озона 📦
📦 Все о доставке!! 📦
— Оформление
🔤• оформляю доставку я сама в приложении озона, от вас будут нужны только город, адрес удобного пвз и номер телефона!
🔤• после оформления вы сами сможете следить за посылкой, для этого перейдите в раздел Ozon доставка > Заказы > Получения
🔤• когда посылку доставят штрихкод будет у вас в приложении 💌
➿➿➿➿➿➿➿➿➿➿➿➿
стоимость …
🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩
🤩💌💌💌💌💌💌🌟🌟🤩🤩
🤩 ria_jwll 🤩
🍉🍏🫐🍏🍉
➖️чтобы заказать украшения вам нужно написать @xiste и отправить фото желаемого изделия 💞
🍋🧄🥭🍍🍏🍐🫐🍏
➖️ личная встреча г. Туймазы
➖️ через озон 📦
🧄🍑🥕🍏🍍🍏
➖️когда все будет готово, мастер отправит вам реквизиты для оплаты
➖️оплатить надо в течение 48ч, иначе заказ будет отменен 💞
🍓🍈🍋🍓🍐🍓🍋🥥🍏🥕🫐🍓
➖️для заказа напишите …
Showing the 7 most recent of 7 posts we hold for @ria_jwll. 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 8 October 2026 — this
entry's latest reading, not the date you are reading this.
“⊹˙• rіᥲ_ȷᥕᥣᥣ ∘˙⊹ 🌷” (@ria_jwll), 809 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/ria_jwll.
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.
