Channel
кондитерские
@tutvkusy
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,716subscribers
+35 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002164019887 |
|---|---|
| Type | Channel |
| Username | @tutvkusy |
| Description | намелака https://t.me/tutvkusy/1259 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 24 September 2026 |
| Last confirmed live | 24 September 2026 |
| Measurements held | 14 |
| On Telegram | t.me/tutvkusy |
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 24 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Sept 2026, 15:53 | 1,716 | no change |
| 18 Sept 2026, 12:42 | 1,716 | +5 |
| 14 Sept 2026, 08:16 | 1,711 | +3 |
| 10 Sept 2026, 23:56 | 1,708 | +6 |
| 6 Sept 2026, 01:15 | 1,702 | +1 |
| 2 Sept 2026, 06:05 | 1,701 | +2 |
| 30 Aug 2026, 11:36 | 1,699 | +1 |
| 27 Aug 2026, 20:53 | 1,698 | +6 |
| 24 Aug 2026, 20:35 | 1,692 | +2 |
| 18 Aug 2026, 04:03 | 1,690 | +2 |
| 14 Aug 2026, 23:56 | 1,688 | +1 |
| 11 Aug 2026, 15:27 | 1,687 | +4 |
| 8 Aug 2026, 09:36 | 1,683 | +2 |
| 7 Aug 2026, 13:07 | 1,681 | 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.
@receptycook · 24,751
Telegram ranks this channel #10 of 75 here — alongside 74 others — read 15 September 2026
@sliv_ot_blogerov_2_rezerv · 21,694
Telegram ranks this channel #22 of 53 here — alongside 52 others — read 23 September 2026
@re_ci_pe · 72,290
Telegram ranks this channel #27 of 72 here — alongside 71 others — read 20 August 2026
@best_kondi · 28,167
Telegram ranks this channel #36 of 84 here — alongside 83 others — read 10 September 2026
@vse_konditery_telega · 28,974
Telegram ranks this channel #41 of 80 here — alongside 79 others — read 9 September 2026
@fitnessotblogerov · 21,562
Telegram ranks this channel #42 of 50 here — alongside 49 others — read 23 September 2026
@konditer_decor · 22,860
Telegram ranks this channel #48 of 70 here — alongside 69 others — read 19 September 2026
This channel appears in 7 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 24 September 2026 — this entry's latest reading, not the date you are reading this.
“кондитерские” (@tutvkusy), 1,716 subscribers as measured 24 September 2026. Telegram Register, tgregister.com/channel/tutvkusy.
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.