Простой способ закрытия петель иглой ✨
👍13

Channel
@knitideas
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
25,574subscribers
-30 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001142309418 |
|---|---|
| Type | Channel |
| Username | @knitideas |
| Created | Between 1 July 2016 and 29 February 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/knitideas |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 08:39 | 25,574 | -5 |
| 1 Sept 2026, 22:36 | 25,579 | -1 |
| 1 Sept 2026, 00:18 | 25,580 | -3 |
| 30 Aug 2026, 21:14 | 25,583 | +3 |
| 30 Aug 2026, 00:13 | 25,580 | -2 |
| 27 Aug 2026, 21:08 | 25,582 | -4 |
| 26 Aug 2026, 18:18 | 25,586 | -2 |
| 25 Aug 2026, 18:55 | 25,588 | -11 |
| 24 Aug 2026, 15:54 | 25,599 | +2 |
| 23 Aug 2026, 01:04 | 25,597 | -1 |
| 21 Aug 2026, 11:06 | 25,598 | +1 |
| 20 Aug 2026, 11:32 | 25,597 | -1 |
| 19 Aug 2026, 10:27 | 25,598 | -2 |
| 18 Aug 2026, 11:23 | 25,600 | -3 |
| 17 Aug 2026, 12:17 | 25,603 | +1 |
| 16 Aug 2026, 04:25 | 25,602 | +3 |
| 14 Aug 2026, 14:08 | 25,599 | -1 |
| 13 Aug 2026, 06:24 | 25,600 | -1 |
| 12 Aug 2026, 09:03 | 25,601 | -1 |
| 11 Aug 2026, 11:54 | 25,602 | first reading |
47 posts held, back to 29 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 72 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 36 of 38 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 47 (29 July 2026 – 2 September 2026) |
| Views total | 49,728 |
| Reactions total | 729 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 23:20 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 16 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.
912 reactions across 41 posts, in 10 distinct kinds. The most used accounts for 64.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 587 | 64.4% | |
| ❤ | 282 | 30.9% | |
| 🔥 | 14 | 1.54% | |
| 🥰 | 14 | 1.54% | |
| 👏 | 6 | 0.658% | |
| ✍ | 3 | 0.329% | |
| 😍 | 2 | 0.219% | |
| 🤩 | 2 | 0.219% | |
| 👎 | 1 | 0.11% | |
| 🙏 | 1 | 0.11% |
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 45 of the 47 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 992 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 47 most recent posts we hold, published 29 July 2026 to 2 September 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.
Простой способ закрытия петель иглой ✨
👍13
Posted without readable text
❤1
Закрытие петель двухцветным полым шнуром 🌿 Три главных правила для идеального i-cord: Спицы: берите на 1–2 размера меньше основных. Внимание: строго следите, чтобы пряжа не перекручивалась. Натяжение: слегка подтягивайте нить перед началом каждого ряда. Больше классных идей смотрите в MAX 🤩
👍20❤7
Posted without readable text
Вяжем котика по схеме 🐱 Больше классных идей смотрите в MAX 🤩
👍14🥰3
Posted without readable text
Тонкий женский джемпер, связанный спицами🌿 Больше классных идей смотрите в MAX 🤩
👍15✍2❤1
Двухцветная полая (двойная) резинка спицами — это плотный и объемный двусторонний узор, у которого лицевая и изнаночная стороны окрашены в разные цвета. Особенности узора: Полотно получается двойным, несвязанным по центру (полым), похожим на чулок или кармашек. Каждая сторона формируется за счет петель только одного цвета. Отлично подходит для вязания шарфов, шапок, воротников и отделки краев изделий
👍32❤6✍1👏1
Кленовый лист 🍁 Автор МК: happiness_by_kris Описание кленового листочка 🍁 Основная часть. 1. Набрать 18 вп 2. Со 2-й от крючка петли вяжем сначала по первой стороне цепочки из вп: 16 сбн, 3 сбн в одну петлю, переходим на другую сторону цепочки из вп: 16, 1 вп, вязание развернуть 3. Пропустить 1 петлю, 16 сбн, 3 сбн в одну петлю, 14 сбн, вп, вязание повернуть 4. Пропустить 1 петлю, 14 сбн, 3 сбн в одну, 15 сбн, вп…
👍20❤7
Кленовый лист 🍁 Автор МК: happiness_by_kris Описание ⬇️ Больше классных идей смотрите в MAX 🤩
👍23❤6🤩1
Мотив крючком 🌸 Больше классных идей смотрите в MAX 🤩
❤18👍6
Идея вязания шали крючком 🌿 Больше классных идей смотрите в MAX 🤩
👍19❤5🤩1
Showing the 12 most recent of 47 posts we hold for @knitideas. 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.
@knitideas edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Citation-graph rank — 62,555 of 1,630,085 entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 2 seed channels' Telegram-generated recommendation lists 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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“Вязаные Идеи. Вязание” (@knitideas), 25,574 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/knitideas.
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.