Channel
@shapok38
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
2,486subscribers
+1 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001749772994 |
|---|---|
| Type | Channel |
| Username | @shapok38 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/shapok38 |
Other / unclassifiable — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 08:20 | 2,486 | +1 |
| 14 Sept 2026, 07:19 | 2,485 | -2 |
| 10 Sept 2026, 05:16 | 2,487 | +2 |
| 5 Sept 2026, 07:18 | 2,485 | -1 |
| 1 Sept 2026, 02:34 | 2,486 | +1 |
| 28 Aug 2026, 04:30 | 2,485 | no change |
| 28 Aug 2026, 04:15 | 2,485 | first reading |
11 posts held, back to 21 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 11 posts for this entry, the most recent from 15 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 videos 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.
641 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 46.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 296 | 46.2% | |
| 🔥 | 248 | 38.7% | |
| 👍 | 69 | 10.8% | |
| 🥰 | 11 | 1.72% | |
| 👏 | 10 | 1.56% | |
| 🍓 | 6 | 0.936% | |
| ❤🔥 | 1 | 0.156% |
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 11 of the 11 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 641 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 21 February 2026 to 15 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.
Друзья, кто ещё без Дофаминового шнурка? Срочно вяжем! Носим! Блистаем! 🤩🤩🤩 Есть множество вариантов стилизации, на шее (причем можно повязать разными способами), в прическе (вплести в косу, повязать на хвост), на поясе… Нужны только спицы 5мм, полмотка Glamour от @lanagrossa Пряжу можно купить в @vyazhem_schastie
🔥25👍7❤5
Юля @shapok38 связала стильный аксессуар и поделилась #бесплатноеописание 🥰 Вам потребуется: ⚜️ Lana Grossa GLAMOUR - 0,5 мотка; ⚜️ спицы 5мм. Набрать 3 петли, привязать 4 ряда лицевой гладью. Затем в каждом лицевом ряду добавить по 1 петле, привязывая первую кромочную за правую и левую стенки - 6 раз. Продолжить вязание на 9 петлях лицевой гладью 1,5 м. Закончить симметрично. Носить как ожерелье/шарфик/галстук. С…
❤15👍9🔥4
Друзья, всем привет из Новосибирска! Сегодня я познакомилась с крючком… Да да, Юлечка, 46 годиков, сегодня впервые вязала крючком, и мне очень понравилось! Увлекательно! Начала вязать косынку. Мне ужасно интересно 😍 Пряжа Lana Grossa с пайетками, Filo Paillettes, 55% хлопок, 39% п/э, 6% п/а, 150м/50г из @vyazhem_schastie Буду делиться процессом! Всех обняла, Юля❤️
🔥60❤18👏10🥰1
Video message, posted without a caption
❤51
Дорогие мои подруги! Поздравляю вас с нашим днём! Желаю, чтобы у вас всегда было время на себя и своё любимое хобби 🌷 P.S. реанимировала свой давний проект под рабочим названием #лебединые_перчатки Весеннее настроение 😊
❤108🔥30🍓6🥰5
Татьяна связала шапку для мужа на 23 февраля, но и ей она очень идёт! 🤩🤩🤩 Роскошное сочетание получилось! А вам какая сторона больше приглянулась? Мк тут 👇🏼👇🏼👇🏼 https://t.me/shapok38 Пряжа тут👇🏼👇🏼👇🏼 Casagrande Cash 20 https://dolcefilato.com/products/casagrande-cash-20/?utm_source=telegram_post Купить пряжу можно только на сайте нашего интернет-магазина или непосредственно в магазине по адресу: Москва, ул…
❤30👍12
Чудесное воплощение #шапка_иньЯн от Татьяны @DolceFilato Интересное сочетание глубокого коричневого и графитового. 014 и 026 Casagrande cash20 В комментах - пара скринов. Шапка - огненный огонь 🔥
❤11
Video message, posted without a caption
🔥52
Друзья, всем привет из Новосибирска! Вот такая пышная объемная шапка - Тыковка получилась на базе описание #шапка_иньЯн. СергейВалерич любит объемные макушки, тут ничего уж не поделаешь. 😊 Просто связала полотно нужной длины, и закрыла макушку за три ряда: провязывала попарно все петли, в каждом новом ряду сокращая количество петель в 2 раза. В итоге стянула 11 лицевых петель 🤗 Тут главное - хорошо подтягивать пе…
👍29❤15🥰5🔥4❤🔥1
Video message, posted without a caption
❤21
Друзья, всем привет из Новосибирска! ❄️ Помните бежево-голубую Инь-Ян? Наконец, вручила её хозяйке. АлисСергевна очень довольна 😊 Сразу надела новую шапку и уже не снимала. Не знаю, то ли ей и вправду так шапка понравилась, то ли она хотела порадовать маму 😅 Кстати, на первом фото я в своей красно-красной Инь-Ян, она всё ещё держится среди моих фаворитов 🥰 У Алисы ОГ 60, размер шапки 58-60, пряжа Casagrande cash…
🔥73❤22👍12
Showing the 11 most recent of 11 posts we hold for @shapok38. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“38shapok” (@shapok38), 2,486 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/shapok38.
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.