Telegram RegisterThe public register of Telegram
Telegram profile photo for КАРТОЧКИ ТОВАРА WB/OZON ИНФОГРАФИКА

Channel

КАРТОЧКИ ТОВАРА WB/OZON ИНФОГРАФИКА

@designer_WB_Dasha

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

220subscribers

-1 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-1002006210327
TypeChannel
Username@designer_WB_Dasha
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live7 October 2026
Measurements held3
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/designer_WB_Dasha

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 7 October 2026 and assigned it the closest of 31 fixed categories, at 66% 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

220221220.57 August 2026 — 221 subscribers8 August 2026 — 221 subscribers7 October 2026 — 220 subscribers7 August 20267 October 2026
3 measurements spanning 61 days, net -1. 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 220–221 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 17:55220-1
8 Aug 2026, 10:33221no change
7 Aug 2026, 12:33221first reading

Engagement

19 posts held, back to 7 February 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 19 posts for this entry, the most recent from 7 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

183 reactions across 19 posts, in 15 distinct kinds. The most used accounts for 16.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54249724700231040893016.4%
custom 53530469548194624012815.3%
❤2413.1%
custom 54721648748868466992111.5%
custom 5215203703190989803189.84%
custom 5355198673305216688179.29%
👍158.20%
custom 5384085485171778811147.65%
😍52.73%
custom 545160994309223968542.19%
🤗31.64%
custom 520426120885254018610.546%
⚡10.546%
🏆10.546%
💘10.546%

Custom emoji. 8 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 19 of the 19 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 183 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 7 February 2026 to 7 June 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.

Recent posts

7 Jun 2026, 18:42 UTC74 views6 reactionsread 8 August 2026
Photo

Смотри всю информацию в закрепе 📌 Заказать 📩 @Dasha_Yanikova

❤5⚡1

7 Jun 2026, 18:42 UTC75 views5 reactionsread 8 August 2026
Photo

Смотри всю информацию в закрепе 📌 Заказать 📩 @Dasha_Yanikova

👍4🏆1

7 Jun 2026, 18:41 UTC60 views6 reactionsread 8 August 2026
Photo

Нейрофотосессия с вашим товаром + инфографика Смотри всю информацию в закрепе 📌 Заказать 📩 @Dasha_Yanikova

😍5💘1

7 Jun 2026, 18:41 UTC52 views6 reactionsread 8 August 2026
Photo

Нейрофотосессия с вашим товаром Смотри всю информацию в закрепе 📌 Заказать 📩 @Dasha_Yanikova

❤5👍1

7 Jun 2026, 18:40 UTC41 views6 reactionsread 8 August 2026
Photo

Нейрофотосессия с вашим товаром Смотри всю информацию в закрепе 📌 Заказать 📩 @Dasha_Yanikova

👍5❤1

31 Mar 2026, 21:14 UTC141 views10 reactionsread 8 August 2026
Photo

Смотри всю информацию в закрепе 📌 Заказать 📩 @Dasha_Yanikova

custom 52152037031909898034custom 53530469548194624014custom 54249724700231040892

31 Mar 2026, 21:14 UTC130 views10 reactionsread 8 August 2026
Photo

Смотри всю информацию в закрепе 📌 Заказать 📩 @Dasha_Yanikova

custom 53551986733052166884custom 54249724700231040894custom 52152037031909898031custom 53840854851717788111

31 Mar 2026, 21:14 UTC112 views10 reactionsread 8 August 2026
Photo

Смотри всю информацию в закрепе 📌 Заказать 📩 @Dasha_Yanikova

custom 53840854851717788114custom 54721648748868466994custom 54249724700231040892

31 Mar 2026, 21:13 UTC89 views10 reactionsread 8 August 2026
Photo

Рич-контент к кейсу выше Смотри всю информацию в закрепе 📌 Заказать 📩 @Dasha_Yanikova

custom 53551986733052166885custom 52152037031909898033custom 53840854851717788111custom 54721648748868466991

31 Mar 2026, 21:13 UTC65 views10 reactionsread 8 August 2026
Photo

Смотри всю информацию в закрепе 📌 Заказать 📩 @Dasha_Yanikova

custom 54516099430922396854custom 54721648748868466993custom 53551986733052166882custom 54249724700231040891

31 Mar 2026, 21:13 UTC67 views10 reactionsread 8 August 2026
Photo

Смотри всю информацию в закрепе 📌 Заказать 📩 @Dasha_Yanikova

custom 54721648748868466995custom 53551986733052166884🤗1

Showing the 12 most recent of 19 posts we hold for @designer_WB_Dasha. 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 7 October 2026 — this entry's latest reading, not the date you are reading this.

“КАРТОЧКИ ТОВАРА WB/OZON ИНФОГРАФИКА” (@designer_WB_Dasha), 220 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/designer_WB_Dasha.

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.