Внимание, колядки от stroika, которые ждут вас на страницах календаря. Предзаказ до 15 декабря осталось всего ничего.
custom 542944850455038773917❤12👾5❤🔥2custom 52762597556800823811

Channel
@Mossprint_tg
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
383subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002288215082 |
|---|---|
| Type | Channel |
| Username | @Mossprint_tg |
| Description | Мы — творческое сообщество, открытое к сотрудничеству и совместной работе. Печатаем мерч и издаем различные зины, участие в которых могут принять творцы любого формата. Анонимка: http://t.me/asklerbot?start=bl1dm ВК https://vk.com/mossprint |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Mossprint_tg |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 06:05 | 383 | no change |
| 7 Aug 2026, 22:14 | 383 | first reading |
17 posts held, back to 15 November 2025 — the 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 17 posts for this entry, the most recent from 9 December 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 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.
341 reactions across 16 posts, in 14 distinct kinds. The most used accounts for 40.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 139 | 40.8% | |
| custom 5429448504550387739 | 88 | 25.8% | |
| 👾 | 35 | 10.3% | |
| custom 5276259755680082381 | 31 | 9.09% | |
| 🔥 | 16 | 4.69% | |
| 🍓 | 14 | 4.11% | |
| ❤🔥 | 6 | 1.76% | |
| 🆒 | 3 | 0.88% | |
| ⚡ | 2 | 0.587% | |
| 💊 | 2 | 0.587% | |
| 💘 | 2 | 0.587% | |
| 🎄 | 1 | 0.293% | |
| 👻 | 1 | 0.293% | |
| 🤗 | 1 | 0.293% |
Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 16 of the 17 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 341reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 15 November 2025 to 9 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Внимание, колядки от stroika, которые ждут вас на страницах календаря. Предзаказ до 15 декабря осталось всего ничего.
custom 542944850455038773917❤12👾5❤🔥2custom 52762597556800823811
МОХ: Зин Studio Ghibli pinned a photo
Спойлер моего домового для календарика от @Mossprint_tg
custom 527625975568008238110👾4custom 54294485045503877393❤2
Чем ближе зима, тем холоднее ночи. 🏠 В октябре домовой в нашем календаре поможет и печь затопить, и уют в дома поддержать. 🐧 Предзаказ домового (и всего календаря)
custom 52762597556800823818❤3👾2custom 54294485045503877391
Спойлер в календарь славянской мифологии от студии Мох 🌱 Развороты в стиле средневековых манускриптов и ботаническая иллюстрация это моя римская империя и арт терапия
❤14👾2custom 54294485045503877392
🪷 Природе отведено особое место в славянской мифологии. Неверно сорванное растение может накликать на нарушителя гнев лешего, а синенький цветочек излечит от всех бед. В нашем календаре вас ждет фрагмент манускрипта по ботанике, где расскажем, чем обернется найденный в правильную ночь цветок папоротника 🌿
❤14👾2custom 54294485045503877391
🤩🤩🤩🤩🤩🤩🤩🤩🤩 👑 Торжественно открываем предзаказ календаря на 2026 год! Мы собрали художников и писателей, чтобы они заглянули в ближайшие леса и болота и вытащили оттуда исконно славянские страхи. 🌿 Теперь каждый месяц в календаре МОХа вас встречает новая тварь, не забудьте выучить правила поведения, иначе встреча с ними может плохо закончиться! 🍄 Вас ждут 14 артов и 12 текстов с хтонью и великолепной природой. Предза…
❤12👾10custom 54294485045503877398🍓1
🐓 Юный леший заглядывает в последний раз! Обложку для календаря МОХа нарисовала Handsandtoes. А наш леший из анонсов – творение stroika, которая к тому же иллюстрирует тринадцатую страничку для вас! 🧔
❤10🍓6custom 54294485045503877395custom 52762597556800823812❤🔥1🎄1👻1👾1
🪴Юный леший принёс вам новость: Жменька и Поганка рисуют для календаря МОХа 👹 Свет и несвет едины, так как являются следствием друг-друга. Что останется, если потушить свечку? – Пишет вселенная софико, а ещё расскажет о тварях на их страничках. Леший вернется завтра с последним анонсом!
❤13custom 54294485045503877395🆒3custom 52762597556800823812⚡1👾1
🪴Юный леший принёс вам новость: питчу✷ и Katrin Bars рисуют для календаря МОХа 👹 Вот только мертвые не говорят, потому что остаются от них только удаленные аккаунты, урны с прахом и неминуемое наказание свыше. – Пишет avoron, а ещё расскажет о тварях на их страничках. Леший вернется завтра с новым анонсом!
❤13custom 54294485045503877393🔥2⚡1❤🔥1👾1
спойлер от Неки!
❤8💊2👾1
спойлер в календарик🤩
custom 542944850455038773910❤8🔥3🍓2👾1
Showing the 12 most recent of 17 posts we hold for @Mossprint_tg. 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.
Citation-graph rank — 1,142,942 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“МОХ: Зин Studio Ghibli” (@Mossprint_tg), 383 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Mossprint_tg.
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.