Мы дома!❤️ Возвращаться не хотелось, но школа 🏫 ждет!💫✨ Завтра снова приступаю к работе. 13 часов дороги вымотали, но это того стоило!
❤2

Channel
@wow_author
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
13,223subscribers
+942 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002055639904 |
|---|---|
| Type | Channel |
| Username | @wow_author |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/wow_author |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 12:58 | 13,223 | -4 |
| 2 Sept 2026, 07:46 | 13,227 | -6 |
| 1 Sept 2026, 04:24 | 13,233 | +30 |
| 31 Aug 2026, 04:28 | 13,203 | +20 |
| 30 Aug 2026, 03:14 | 13,183 | +16 |
| 29 Aug 2026, 02:38 | 13,167 | +7 |
| 27 Aug 2026, 23:54 | 13,160 | +12 |
| 26 Aug 2026, 21:39 | 13,148 | +29 |
| 25 Aug 2026, 21:47 | 13,119 | +30 |
| 24 Aug 2026, 21:54 | 13,089 | +64 |
| 23 Aug 2026, 08:04 | 13,025 | +75 |
| 21 Aug 2026, 16:24 | 12,950 | +51 |
| 20 Aug 2026, 13:18 | 12,899 | +7 |
| 19 Aug 2026, 13:12 | 12,892 | +28 |
| 18 Aug 2026, 11:13 | 12,864 | +31 |
| 17 Aug 2026, 09:58 | 12,833 | +44 |
| 15 Aug 2026, 18:02 | 12,789 | +51 |
| 14 Aug 2026, 06:14 | 12,738 | +41 |
| 12 Aug 2026, 22:42 | 12,697 | +37 |
| 11 Aug 2026, 22:15 | 12,660 | first reading |
67 posts held, back to 4 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 48 pages of Telegram’s post history, 20 posts per page.
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. It is computed over the 61 of 62 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 67 (4 August 2026 – 2 September 2026) |
| Views total | 61,567 |
| Reactions total | 906 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 20:24 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.
Measured directly from 16 videos 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.
931 reactions across 63 posts, in 9 distinct kinds. The most used accounts for 58.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 545 | 58.5% | |
| 🔥 | 226 | 24.3% | |
| 👍 | 120 | 12.9% | |
| 😁 | 13 | 1.40% | |
| ❤🔥 | 9 | 0.967% | |
| 💯 | 8 | 0.859% | |
| 👏 | 6 | 0.644% | |
| 🤩 | 2 | 0.215% | |
| 🥰 | 2 | 0.215% |
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 63 of the 67 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 931 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 67 most recent posts we hold, published 4 August 2026 to 2 September 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.
Мы дома!❤️ Возвращаться не хотелось, но школа 🏫 ждет!💫✨ Завтра снова приступаю к работе. 13 часов дороги вымотали, но это того стоило!
❤2
🔥 ЛИНГВИСТИЧЕСКИЕ КВЕСТЫ КО ДНЮ ЯЗЫКОВ НАРОДОВ РОССИИ! ГОТОВОЕ РЕШЕНИЕ ДЛЯ КЛАССНОГО ЧАСА🚀 Два уникальных интерактивных классных часа под ключ, которые влюбят детей в многообразие культур нашей страны через игру, логику и детективные расследования. Вам останется только скачать, распечатать и включить презентацию! 🎁 ⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️ https://payform.ru/7wcsAaH/ 💫 ВАРИАНТ 1: для 1–2 классов 📦 «ЛИНГВО-КОД: МИССИЯ “ПЕ…
🔥3❤2
Красивые бейджи для дежурных! Вы просили и я сделала⬇️ https://disk.yandex.ru/d/uoWqQpK5ti7_yg
❤5
С началом учебного года, мои дорогие! 💫❤️ Дублирую открытки для коллег!⬇️ https://disk.yandex.ru/d/FLpkoJ72VXvwYQ
❤2
Дыханьем спящим дышит тишина, И лето тихо уступает трон. Вам мудрость неба высшая дана, Вы справитесь, и год благословлён. Всё обязательно получится у вас, Мои родные, верные друзья. Пусть манит снова и зовёт ваш класс, Где ждёт открытий новая земля. Пусть на губах улыбка расцветёт, И не угаснет пламя юных глаз. Пусть эта осень радость принесёт И вдохновеньем озаряет вас. А я сквозь вихри буден и тревог Останусь рядо…
❤14👍5
Интересные идеи для 1 сентября ✨💫 А здесь вы найдете все необходимое для начала учебного года⬇️ https://t.me/wow_author/3199
❤9🔥5
Гений произведений✍🏻 pinned a photo
Дочь доводила, доводила, а потом как выдала!😅 «Мам, сними меня, пожалуйста!». А ведь весь отпуск было «дурацким» абсолютно все: море, еда, место…😵💫вчера меня до истерики довела, но сегодня так уж и быть…мини-диско😁
❤9😁4
Друзья! В нашем канале «Детский сад» появилась масса новых крутых материалов! Переходите и забирайте бесплатно ➡️ https://t.me/geniy_proizvedeniy_sad
❤4
Купоны для школьников. Вы просили и я сделала💫✨ https://disk.yandex.ru/d/sLKVzVtPF7rSPg Жду много реакций🤩 Я очень старалась!
❤20👍6🔥3
📢 Обновление локации «Станция 6» и материалов классного часа Уважаемые участники! На основе ваших отзывов и обратной связи мы полностью переработали шестую локацию и обновили сопроводительные материалы для классного часа «Единство народов России» (5–11 классы). 🛠 Что изменилось • Оптимизированы инструкции. Формулировка задания полностью пересмотрена, чтобы исключить двоякие трактовки. • Повышена прозрачность. Услови…
❤5
🍂ОСЕННЯЯ НАВИГАЦИЯ🍂 🇷🇺 Сценарий классного часа «Единство народов России» (1-4 классы)⬇️ https://payform.ru/blclsZO/ 🇷🇺 Сценарий классного часа «Единство народов России» (5-11 классы)⬇️ https://payform.ru/cncopCX/ 🍁 Универсальные линейки 2026 (для всех) и классные часы (для 1, 2,3, 4 классов) ⬇️ https://payform.ru/5mc6AZl/ 🍁 Только линейки 2026 (4 сценария + 5 караоке) ⬇️ https://payform.ru/l8cbOdT/ 🍁 Только кла…
❤5🤩1
Showing the 12 most recent of 67 posts we hold for @wow_author. 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.
@wow_author edited 5 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
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.
This channel appears in 18 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Гений произведений✍🏻” (@wow_author), 13,223 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/wow_author.
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.