![Telegram profile photo for [🩻💻] dyloshki confessions](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMzIwIiBoZWlnaHQ9IjMyMCIgcHJlc2VydmVBc3BlY3RSYXRpbz0ibm9uZSIgdmlld0JveD0iMCAwIDEwMCAxMDAiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyI%2BPGRlZnM%2BPGxpbmVhckdyYWRpZW50IGlkPSJnIiB4MT0iMCUiIHgyPSIwJSIgeTE9IjAlIiB5Mj0iMTAwJSI%2BPHN0b3Agb2Zmc2V0PSIwJSIgc3RvcC1jb2xvcj0iI2ZmY2Q2YSIvPjxzdG9wIG9mZnNldD0iMTAwJSIgc3RvcC1jb2xvcj0iI2ZmYTg1YyIvPjwvbGluZWFyR3JhZGllbnQ%2BPC9kZWZzPjxzdHlsZT50ZXh0e2ZvbnQ6NjAwIDQ0cHggLWFwcGxlLXN5c3RlbSxCbGlua01hY1N5c3RlbUZvbnQsJ1NlZ29lIFVJJyxSb2JvdG8sSGVsdmV0aWNhLEFyaWFsLHNhbnMtc2VyaWYsJ0FwcGxlIENvbG9yIEVtb2ppJywnU2Vnb2UgVUkgRW1vamknLCdTZWdvZSBVSSBTeW1ib2wnOy13ZWJraXQtdXNlci1zZWxlY3Q6bm9uZTt1c2VyLXNlbGVjdDpub25lfTwvc3R5bGU%2BPHJlY3Qgd2lkdGg9IjEwMCIgaGVpZ2h0PSIxMDAiIGZpbGw9InVybCgjZykiLz48dGV4dCB0ZXh0LWFuY2hvcj0ibWlkZGxlIiB4PSI1MCIgeT0iNjYiIGZpbGw9IiNmZmYiPkRDPC90ZXh0Pjwvc3ZnPg%3D%3D)
Channel
[🩻💻] dyloshki confessions
@dyloshka_conf
On this record: Topic · Growth · Engagement · Cite this entry
2,399subscribers
-93 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 | -1002113546520 |
|---|---|
| Type | Channel |
| Username | @dyloshka_conf |
| Created | 13 January 2024 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 16 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/dyloshka_conf |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 76% 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 |
|---|---|---|
| 17 Sept 2026, 15:18 | 2,399 | -11 |
| 16 Sept 2026, 14:56 | 2,410 | no change |
| 13 Sept 2026, 17:36 | 2,410 | -5 |
| 10 Sept 2026, 06:39 | 2,415 | -6 |
| 5 Sept 2026, 08:19 | 2,421 | -6 |
| 1 Sept 2026, 19:38 | 2,427 | -7 |
| 30 Aug 2026, 02:26 | 2,434 | -12 |
| 27 Aug 2026, 07:12 | 2,446 | -7 |
| 24 Aug 2026, 15:47 | 2,453 | -3 |
| 20 Aug 2026, 14:36 | 2,456 | -8 |
| 17 Aug 2026, 14:58 | 2,464 | -14 |
| 14 Aug 2026, 01:47 | 2,478 | -5 |
| 11 Aug 2026, 03:31 | 2,483 | -8 |
| 8 Aug 2026, 11:18 | 2,491 | -1 |
| 7 Aug 2026, 19:49 | 2,492 | 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“[🩻💻] dyloshki confessions” (@dyloshka_conf), 2,399 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/dyloshka_conf.
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.