Telegram RegisterThe public register of Telegram

Channel

Domashka

@dmsk_bag

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

115subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002381107548
TypeChannel
Username@dmsk_bag
DescriptionТворчество, самовыражение, рюкзаки Сайт: maxbag.ru
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/dmsk_bag

Growth

1157 Aug 2026, 20:55 — 115 subscribers9 Aug 2026, 05:46 — 115 subscribers7 Aug 2026, 20:559 Aug 2026, 05:46
2 measurements spanning 1 day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 114–116 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 05:46115no change
7 Aug 2026, 20:55115first reading

Engagement

9 posts held, back to 17 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 9 posts for this entry, the most recent from 14 February 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
45
Videos
1
Links
6

Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
5s
Average length
5s

Measured directly from 1 video 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.

Reaction mix

170 reactions across 9 posts, in 18 distinct kinds. The most used accounts for 28.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4828.2%
❤‍🔥4526.5%
3822.4%
💯74.12%
🕊74.12%
🍓31.76%
👍31.76%
💔31.76%
😍31.76%
🦄31.76%
21.18%
👌21.18%
🎃10.588%
💅10.588%
💋10.588%
😁10.588%
😘10.588%
🥰10.588%

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 9 of the 9 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 170reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 9 most recent posts we hold, published 17 November 2025 to 14 February 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.

Recent posts

14 Feb 2026, 12:13 UTC413 views28 reactionsread 9 August 2026
Photo

С праздником ❤️

15💯5🔥2😍2💔1🥰1😁1😘1

10 Feb 2026, 07:23 UTC429 views12 reactionsread 9 August 2026
Forwarded from @kof_roasteryPhoto

KOF ЗАЛЕЗЕТ В ВАШ КАРМАН Друзья, за последние 20 лет мировое образование пластиковых отходов как минимум удвоилось. Так что в 2026 грош цена красивой и технологичной упаковке, если из нее, после использования, нельзя сшить трусы сделать картхолдер! Так же подумал и Макс из мастерской DOMASHKA и вы просто посмотрите, что получается! Источник и материала и вдохновения, одновременно, наша новая B2B упаковка. Еще DOMAS

🔥72❤‍🔥1🍓1👍1

9 Feb 2026, 09:15 UTC337 views14 reactionsread 9 August 2026
Photo

Сейчас активно работаем над новым аксессуаром который тоже из упаковок из-под зерна. Если хотите помочь, ответьте на микро-тест, который даст мне немного больше понимания о ваших желаниях. Тест тут

❤‍🔥6🔥3💯2🍓1🎃1👍1

30 Jan 2026, 13:24 UTC337 views18 reactionsread 9 August 2026
Photo

Теперь в кофейне полдень на специальной полочке продаются наши картхолдеры, заглядывайте.

❤‍🔥9🔥51🍓1💅1💋1

28 Jan 2026, 11:35 UTC297 views8 reactionsread 9 August 2026
Photo

Мне всегда очень стыдно когда вы приезжаете выбрать рюкзак в мастерскую, а у нас в жуткий беспорядок

🕊71

26 Jan 2026, 07:49 UTC298 views27 reactionsread 9 August 2026
Photo

Наглядный пример того, чем хорош локальный бренд. Девушке понравилась модель рюкзака, но единственное, что не подходило, это то, что туда не помещалась обувь. Нужно было после тренировки ехать сразу на работу, поэтому важно было уместить кроссовки. Мы увеличили боковые части. А для того чтобы рюкзак также держал форму, мы добавили ремни: если не нужен такой большой объём, их можно стянуть, и рюкзачок будет смотрет

❤‍🔥15🔥7💔211👍1

24 Jan 2026, 09:05 UTC259 views21 reactionsread 9 August 2026
Photo

Нам прислали много новых упаковок Постараемся уже сегодня сделать картхолдеры, самому интересно как выйдет

🔥13❤‍🔥6👌2

22 Jan 2026, 06:51 UTC269 views17 reactionsread 9 August 2026
Photo

На сайте новая модель рюкзака Долго решал с чем такие яркие ручки будут считаться в итоге получилось круто. Мех дает классную фактуру, а ручки яркий акцент Продолжаем экспериментировать Буду рад вашим мыслям в комментах по поводу того что вышло

❤‍🔥8🔥5🦄31

17 Nov 2025, 12:55 UTC371 views25 reactionsread 9 August 2026
Photo

Наш новый сотрудник, ленивый зумер. Постоянно спит на работе

18🔥6😍1

Showing the 9 most recent of 9 posts we hold for @dmsk_bag. 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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 9 August 2026 — this entry's latest reading, not the date you are reading this.

“Domashka” (@dmsk_bag), 115 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/dmsk_bag.

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.