Telegram RegisterThe public register of Telegram
Telegram profile photo for Вязание @voobrazhalkina

Channel

Вязание @voobrazhalkina

@voobrazhalkina_mk

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry

5,519subscribers

-12 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001551649228
TypeChannel
Username@voobrazhalkina_mk
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/voobrazhalkina_mk

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

5,5195,5315,5257 August 2026 — 5,531 subscribers7 August 2026 — 5,531 subscribers14 August 2026 — 5,528 subscribers20 August 2026 — 5,525 subscribers26 August 2026 — 5,520 subscribers29 August 2026 — 5,521 subscribers1 September 2026 — 5,522 subscribers10 September 2026 — 5,523 subscribers14 September 2026 — 5,521 subscribers17 September 2026 — 5,519 subscribers7 August 202617 September 2026
10 measurements spanning 41 days, net -12. 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 5,517–5,533 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 15:205,519-2
14 Sept 2026, 00:215,521-2
10 Sept 2026, 09:595,523+1
1 Sept 2026, 14:165,522+1
29 Aug 2026, 07:495,521+1
26 Aug 2026, 09:185,520-5
20 Aug 2026, 07:425,525-3
14 Aug 2026, 07:385,528-3
7 Aug 2026, 19:185,531no change
7 Aug 2026, 19:095,531first reading

Engagement

7 posts held, back to 31 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 7 pages 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
36s
Average length
36s

Measured directly from 1 video 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.

Reaction mix

68 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥3450.0%
2130.9%
👍1116.2%
❤‍🔥22.94%

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 5 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 68 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 31 July 2026 to 5 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.

Recent posts

5 Aug 2026, 13:12 UTC392 viewsread 8 August 2026

Сегодня последний день скидок -50 % ❤️‍🔥 Следующие только в ноябре на черную пятницу

Signed Natali

5 Aug 2026, 13:12 UTC472 views25 reactionsread 12 August 2026
Photo

Вариации с круглым воротником

🔥118👍4❤‍🔥2

Signed Natali

3 Aug 2026, 16:22 UTC555 views20 reactionsread 12 August 2026
Photo

Новый топ🔥 Еще идет распродажа МК до 5 августа

🔥20

Signed Natali

31 Jul 2026, 18:48 UTC645 views7 reactionsread 12 August 2026
Video

Домой приехали без ног 😄🥵

7

Signed Natali

31 Jul 2026, 18:47 UTC537 views10 reactionsread 12 August 2026
Photo

Сегодня с дочкой ездили на экскурсию в Несвиж и в Мир в замки Просто купили сборную экскурсию Были одни россияне в автобусе Кто ездил ?? ☺️

👍7🔥3

Signed Natali

Showing the 7 most recent of 7 posts we hold for @voobrazhalkina_mk. 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Вяжите для души
@knitforsoul · 48,136
Telegram ranks this channel #24 of 72 here — alongside 71 others — read 7 September 2026
Ирина Невзорова
@nevzorovaclub · 32,650
Telegram ranks this channel #36 of 76 here — alongside 75 others — read 7 September 2026
Юлия Гендина. Вязание для дома. Poufpeople
@poufpeople · 25,146
Telegram ranks this channel #38 of 75 here — alongside 74 others — read 14 September 2026
Худеем с Сергеем Обложко
@hudeemsoblozhko · 51,477
Telegram ranks this channel #87 of 94 here — alongside 93 others — read 25 August 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“Вязание @voobrazhalkina” (@voobrazhalkina_mk), 5,519 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/voobrazhalkina_mk.

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.