4 measurements spanning 17 days, net +5. 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 233–240 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
4 Sept 2026, 07:16
239
+4
26 Aug 2026, 23:03
235
+1
19 Aug 2026, 01:45
234
no change
18 Aug 2026, 14:30
234
first reading
Engagement
8 posts held, back to 24 June 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 1 page of Telegram’s post history, 20 posts per page.
ERR · 30 days
20.9%
avg views ÷ 239 subscribers
Avg views / post
50.0
2 posts measured
Reaction rate
30.0%
reactions ÷ views · ER floor
Posts in window
2
of 8 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
Window
Rolling 30 days · latest post in window 16 August 2026
Posts held
8 (24 June 2026 – 16 August 2026)
Views total
100
Reactions total
30
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
18 Aug 2026, 14:30 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
17s
Average length
17s
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
142 reactions across 8 posts, in 8 distinct kinds. The most used accounts for 45.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
65
45.8%
🔥
51
35.9%
👍
14
9.86%
👏
5
3.52%
🤩
3
2.11%
❤🔥
2
1.41%
😍
1
0.704%
🥰
1
0.704%
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 8 of the 8 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 142 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 24 June 2026 to 16 August 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.
Дальневосточный аист повстречался мне сегодня на пути. В конце августа это обычное явление. Из-за неопытности и любопытства молодые аисты часто выходят на обочины дорог, не испытывая страха перед человеком и автомобилем.
И, кстати, с такими птицами всё в порядке. Их не надо спасать.
Август, 2026 г.
Амурская область, Благовещенский район.
Пролетая над речкой то в одну сторону, то в другую, озёрная чайка разглядывает водную поверхность в надежде чем-нибудь подкрепиться. Если повезёт, поймает небольшую рыбёшку или крупную стрекозу.
Август, 2026 г.
Амурская область, Благовещенский район.
Неожиданный всплеск воды и шум крыльев заставили вздрогнуть и обернуться. Небольшой большой баклан, неуклюже размахивая крыльями и разбегаясь по воде, пытался взлететь. Взлетел, распугав всю рыбу. Сделав полукруг в воздухе, баклан приводнился к группе своих собратьев, плавающих у дальнего берега.
Июль, 2026 г.
Амурская область, Константиновский район.
Если долго сидеть на берегу, то можно увидеть утёнка утки-касатки, кормящегося ряской. Вы бы слышали как он чавкал.
Июль, 2026 г.
Амурская область, Константиновский район.
После работы снова ездил наблюдать за длиннохвостыми сусликами. В этот раз я сел за остановкой, спрятавшись в тень и стал ждать. Сначала суслики осторожно выглядывали из нор, но потом, убедившись в отсутствии опасности, повылазили на обочину. Сюда их привлекает свежая зелень, повсходившая после покоса дорожниками. Как маленькие пушистые комбайны, суслики поедали листики травы, иногда выкапывая её вместе с корешками.
…
Наверное, многие автомобилисты Благовещенска замечали за старым мостом через Зею длиннохвостых сусликов, выбегающих на обочину в поисках чего-нибудь съестного.
Живут они там давно, но только сегодня я наконец-то до них добрался. Сфотографировать их с подхода - так себе затея. Близко не подпускают, а перед тем как спрятаться, издают предупреждающий крик для собратьев. Хотя любопытством и они не обделены. Вставая на за…
Это гнездо дальневосточные аисты построили ещё в апреле, но после прошедшего ранней весной пала, я думал, они его бросили. Во всяком случае, никаких признаков присутствия птиц поблизости я не наблюдал.
Вернувшись с отпуска, я решил проверить это гнездо и был рад обнаружить в нём двух уже довольно больших аистят.
Июнь, 2026 г.
Амурская область, Константиновский район.
Чтобы построить гнездо, деревенским ласточкам приходится изрядно повозиться в грязи. Комочек за комочком уносится под какой нибудь навес, где происходит лепка будущего домика. По некоторым данным, на одну постройку используется около 0.5 кг грязи. Для прочности гнездо армируется различными стебельками и травинками.
У небольшой лужи на деревенской дороге собралось несколько десятков ласточек и каждая норовит набрать в…
🔥10❤7👍3😍1
Showing the 8 most recent of 8 posts we hold for @forest_rustles. 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.
Mentions
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.
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.
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 4 September 2026 — this
entry's latest reading, not the date you are reading this.
“Лесные шорохи 🐾” (@forest_rustles), 239 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/forest_rustles.
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.