Channel
@knittingannarodkina
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
122subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001112840803 |
|---|---|
| Type | Channel |
| Username | @knittingannarodkina |
| Created | Between 1 February 2017 and 31 October 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 12 September 2026 |
| On Telegram | t.me/knittingannarodkina |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Sept 2026, 02:18 | 122 | -1 |
| 28 Aug 2026, 13:43 | 123 | +1 |
| 9 Aug 2026, 03:31 | 122 | no change |
| 6 Aug 2026, 02:41 | 122 | first reading |
6 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 6 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
41 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 53.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5453930874699542906 | 22 | 53.7% | |
| custom 5440718610404241986 | 13 | 31.7% | |
| custom 5458722280085417045 | 5 | 12.2% | |
| custom 5404860405191298494 | 1 | 2.44% |
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 6 of the 6 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 41 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 24 July 2026 to 8 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.
🐋🐋🐋🐋🐋🐋🐋 🐋🐋🐋🐋🐋🐋 И три процесса🐋 Кашемировый пушок… это песня. Джемпер на мою предстоящую осень/зиму готов и сохнет. Но поскольку капелька лета еще осталась - продолжаю работать с шелком. Ну а черный процесс - это моя неизменная любовь Ализе Коттон Голд, я наверное уже надоела с ним. Ну как есть) мне нравится в этой пряже буквально все.
custom 54407186104042419866custom 54539308746995429062custom 54048604051912984941
🫘🫘🫘🫘🫘🫘🫘🫘🫘🫘🫘🫘🫘🫘 Мой самый-самый-самый любимый момент летом, касаемо вязания - это повязать на берегу, солнечным днем, под шум воды и отдыхающих. 🫘 Вяжу сейчас три проекта, но сильно засматриваюсь на четвертый, потому что мой бежевый джемпер уже почти готовенький. Хотелось связать что то универсальное, на долгие годы. Но не просто лицевой гладью. Тельняшки я люблю, так что решением послужил теневой узор🫘 И два проекта …
custom 54407186104042419864custom 54587222800854170453custom 54539308746995429061
👉👈 На спицах сейчас бежевый джемпер и вау, я решила связать плечевое крючком. Это редкий зверь🌿🤩 Оттенки расслабляющие и приятные. Узоры не затейливые, тактильно все супер мягкое и комфортное. ❤
custom 54539308746995429068custom 54587222800854170452
Я немножко новых стикеров добавила в свой набор ❤️
custom 54407186104042419863
Sticker, posted without a caption
🫘🤩🫘🫘🫘🤩🫘 🫘🤩🫘🫘🫘🫘🫘🫘🫘🫘🫘🫘 Завершила свой милый джемпер из остатков градиентного хлопка. И брошка с котенком по цветовой гамме, и по настроению, суперски вписалась в эту тельняшку 🤌🏻
custom 545393087469954290611
Showing the 6 most recent of 6 posts we hold for @knittingannarodkina. 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 4 September 2026 — this entry's latest reading, not the date you are reading this.
“AnnaRodkinaArt” (@knittingannarodkina), 122 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/knittingannarodkina.
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.