Channel
ВЯЗАНАЯ КОПИЛКА
@knitvip
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,837subscribers
+9 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 | -1001692027532 |
|---|---|
| Type | Channel |
| Username | @knitvip |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/knitvip |
Topic
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 09:35 | 3,837 | +4 |
| 30 Oct 2026, 09:44 | 3,833 | -1 |
| 27 Oct 2026, 04:26 | 3,834 | +5 |
| 23 Oct 2026, 20:07 | 3,829 | +2 |
| 20 Oct 2026, 23:07 | 3,827 | +1 |
| 17 Oct 2026, 21:15 | 3,826 | +3 |
| 14 Oct 2026, 21:38 | 3,823 | +1 |
| 11 Oct 2026, 14:19 | 3,822 | -2 |
| 5 Oct 2026, 13:37 | 3,824 | -1 |
| 27 Sept 2026, 18:42 | 3,825 | +5 |
| 12 Sept 2026, 02:38 | 3,820 | -2 |
| 6 Sept 2026, 13:39 | 3,822 | no change |
| 3 Sept 2026, 01:54 | 3,822 | -4 |
| 27 Aug 2026, 11:03 | 3,826 | -1 |
| 24 Aug 2026, 13:15 | 3,827 | +3 |
| 20 Aug 2026, 14:45 | 3,824 | -4 |
| 17 Aug 2026, 19:47 | 3,828 | -4 |
| 14 Aug 2026, 14:16 | 3,832 | +2 |
| 11 Aug 2026, 11:25 | 3,830 | +3 |
| 8 Aug 2026, 10:08 | 3,827 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
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.
@knittmi · 22,978
Telegram ranks this channel #23 of 77 here — alongside 76 others — read 19 September 2026
@knitting_gr · 27,013
Telegram ranks this channel #26 of 80 here — alongside 79 others — read 11 September 2026
@knitforsoul · 47,899
Telegram ranks this channel #41 of 72 here — alongside 71 others — read 7 September 2026
@knitideas · 25,787
Telegram ranks this channel #58 of 83 here — alongside 82 others — read 14 September 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“ВЯЗАНАЯ КОПИЛКА” (@knitvip), 3,837 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/knitvip.
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.