Telegram RegisterThe public register of Telegram

Channel

Moonworks Games. ЭОН 2032

@moonworks

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cross-platform identity · Cite this entry

3,943subscribers

+47 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001036093948
TypeChannel
Username@moonworks
CreatedBetween 1 February 2016 and 30 September 2016— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/moonworks

Growth

3,8913,9433,9176 August 2026 — 3,896 subscribers6 August 2026 — 3,896 subscribers7 August 2026 — 3,891 subscribers11 August 2026 — 3,903 subscribers14 August 2026 — 3,943 subscribers6 August 202614 August 2026
5 measurements spanning 7 days, net +47. 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 3,883–3,951 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 07:153,943+40
11 Aug 2026, 00:333,903+12
7 Aug 2026, 14:203,891-5
6 Aug 2026, 20:303,896no change
6 Aug 2026, 20:203,896first reading

Engagement

7 posts held, back to 1 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
59.3%
avg views ÷ 3,943 subscribers
Avg views / post
2,340
1 post measured
Reaction rate
3.25%
reactions ÷ views · ER floor
Posts in window
1
of 7 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 21 July 2026
Posts held7 (1 June 202621 July 2026)
Views total2,340
Reactions total76
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 05:58 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
28s
Average length
28s

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

1,427 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 77.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,10477.4%
🍓15510.9%
🌭735.12%
🤝584.06%
🌚372.59%

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

Measured over the 7 most recent posts we hold, published 1 June 2026 to 21 July 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

21 Jul 2026, 12:24 UTC≈2,340 views76 reactionsread 8 August 2026

https://boosty.to/moonworks/posts/52e5f997-1bb4-4393-aa4d-dbd8b762e57a спасибо бустерам!

73🌚2🤝1

13 Jul 2026, 12:36 UTC≈4,340 views251 reactionsread 8 August 2026
Photo

Новости - Набрали 10000 вишлистов в Стиме! Спасибо! - Новый фон: Прихожая Максима - Новая романтическая музыкальная композиция - Новая ЦГ в 6 день с Женей - Продолжаем анимировать фоны Очаровательная летняя Саша от deredereday

197🤝29🍓22🌚3

4 Jul 2026, 12:52 UTC≈4,900 views80 reactionsread 8 August 2026

Бонусный скетч для бустеров

🍓59🌭108🤝3

4 Jul 2026, 12:17 UTC≈4,640 views253 reactionsread 8 August 2026
Photo

Новости! Все силы брошены на демку 🫡 - Нарезаем и собираем анимацию фонов: проведена глобальная работа по шейдерам и прочим крутым визуальным штукам - Написали тз по звукам 1-3 дня и отдали звуковику - Пишем недостающие “брожения” - Набросали еще три скетча ЦГ (мы их вам пока не покажем) - Несколько новых текстов и доработок старых

213🌭19🍓15🤝6

15 Jun 2026, 19:21 UTC≈6,260 views249 reactionsread 8 August 2026
Photo

Новости - Готов секси-ЦГ с Василисой от новой художницы - Рисуем другие ЦГшки - Новый фон - вход в Библиотеку - Дописали 14 день Ника-рута - Собираем демку, отлавливая несостыковочки - Апдейт движка: багфиксы, добавили забытое указание игровых дней, починили воспроизведение видео-очереди - Начали придумывать ачивки - Боремся с блокировками

205🌚21🤝17🍓6

11 Jun 2026, 09:23 UTC≈5,150 views247 reactionsread 8 August 2026
Forwarded from @cabbbrioletPhoto

Охаё гозаимас!

178🌭43🍓24🌚2

1 Jun 2026, 12:27 UTC≈7,790 views271 reactionsread 8 August 2026
Photo

Новости: - обсудили издание игры, оста, а также опенинги-эндинги - рисуем спрайт Марины - прорабатываем концовку рута Насти - продолжаем писать тру-рут - продолжаем делать демку: добавили “новости в аспере” - готов фон “коридор ВФУ" Отдельно поздравляем наших разработчиков с Днями рождения: Художник-кун, Норин, Sebastian Valmont! ❤️

230🍓29🌚9🤝2🌭1

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

Cross-platform identity — Wikidata

A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.

Q136445129 on Wikidata, read 9 August 2026
LabelMoonworks
DescriptionRussian visual novel developer and publisher
X / Twitter@moonworksgames
Official sitehttps://moonworks.ru/

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

“Moonworks Games. ЭОН 2032” (@moonworks), 3,943 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/moonworks.

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.