Channel
ДОМ МЕДОВЫХ НИТОК🧶
@dom_medovyh_nitok
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,506subscribers
-39 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 | -1002030071295 |
|---|---|
| Type | Channel |
| Username | @dom_medovyh_nitok |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/dom_medovyh_nitok |
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 28 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 |
|---|---|---|
| 3 Nov 2026, 23:31 | 1,506 | +1 |
| 1 Nov 2026, 06:07 | 1,505 | -2 |
| 25 Oct 2026, 15:04 | 1,507 | -3 |
| 22 Oct 2026, 18:16 | 1,510 | -3 |
| 19 Oct 2026, 15:11 | 1,513 | -1 |
| 16 Oct 2026, 06:47 | 1,514 | -3 |
| 13 Oct 2026, 00:28 | 1,517 | +2 |
| 6 Oct 2026, 14:38 | 1,515 | +8 |
| 29 Sept 2026, 08:20 | 1,507 | -9 |
| 27 Sept 2026, 23:10 | 1,516 | no change |
| 16 Sept 2026, 06:57 | 1,516 | -1 |
| 12 Sept 2026, 14:58 | 1,517 | -3 |
| 8 Sept 2026, 09:56 | 1,520 | -6 |
| 3 Sept 2026, 10:12 | 1,526 | +1 |
| 31 Aug 2026, 01:14 | 1,525 | -1 |
| 28 Aug 2026, 02:45 | 1,526 | -6 |
| 24 Aug 2026, 20:17 | 1,532 | -3 |
| 20 Aug 2026, 18:53 | 1,535 | -3 |
| 17 Aug 2026, 14:25 | 1,538 | -5 |
| 14 Aug 2026, 11:49 | 1,543 | 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.
@grekovadanilina · 19,196
Telegram ranks this channel #4 of 77 here — alongside 76 others — read 3 October 2026
@forest_fairy_home · 43,035
Telegram ranks this channel #7 of 58 here — alongside 57 others — read 28 August 2026
@dom_krasota_ksu · 29,209
Telegram ranks this channel #8 of 69 here — alongside 68 others — read 8 September 2026
@modnayacoma · 26,203
Telegram ranks this channel #19 of 78 here — alongside 77 others — read 12 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“ДОМ МЕДОВЫХ НИТОК🧶” (@dom_medovyh_nitok), 1,506 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/dom_medovyh_nitok.
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.