Telegram RegisterThe public register of Telegram

Channel

«Наследие»

@nasledie34

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

635subscribers

+28 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001761082692
TypeChannel
Username@nasledie34
Created11 March 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/nasledie34

Growth

606635620.56 August 2026 — 607 subscribers6 August 2026 — 607 subscribers7 August 2026 — 606 subscribers13 August 2026 — 635 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net +28. 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 602–639 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 02:33635+29
7 Aug 2026, 02:44606-1
6 Aug 2026, 17:47607no change
6 Aug 2026, 08:00607first reading

Engagement

9 posts held, back to 23 July 2026the 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.

ERR · 30 days
18.1%
avg views ÷ 635 subscribers
Avg views / post
115
9 posts measured
Reaction rate
5.72%
reactions ÷ views · ER floor
Posts in window
9
of 9 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 6 August 2026
Posts held9 (23 July 20266 August 2026)
Views total1,032
Reactions total59
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 17:47 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.

Reaction mix

59 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 33.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2033.9%
custom 53980170061653052871016.9%
👍1016.9%
58.47%
🕊58.47%
🔥46.78%
👏35.08%
🎉23.39%

Custom emoji. One row above is a 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 count beside it isTelegram’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 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 59reactions 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 23 July 2026 to 6 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.

Recent posts

6 Aug 2026, 05:11 UTC25 views9 reactionsread 6 August 2026
Photo

🚂 В сентябре 1942 года вокзал Сталинград-1, разбитый авиацией и артиллерией, всё ещё сохранял стратегическое значение. Через него проходили пути, вокруг которых можно было выстроить оборону. 🥰 Генерал-полковник Александр Родимцев писал: «После Мамаева кургана вокзал считался едва ли не главным в тактическом отношении пунктом города». В ночь на 15 сентября 1942 года батальон гвардейцев при поддержке трёх танков Т-

3🕊3custom 53980170061653052873

5 Aug 2026, 12:55 UTC151 views10 reactionsread 6 August 2026
Photo

📖 Закажите комикс «Похоронен: река Волга» и откройте историю легендарного БК-31 🥰 Военно-исторический музей «Наследие» представляет иллюстрированную историю бронекатера БК-31 и его экипажа, защищавшего Сталинград в самые тяжёлые месяцы великой битвы. 🔥 В основе комикса лежат реальные события. Огненная Волга, налёты вражеской авиации, напряжённые бои и судьбы моряков-речников складываются в историю, которая захватыв

4👍3🔥2custom 53980170061653052871

2 Aug 2026, 05:21 UTC188 views6 reactionsread 6 August 2026
Photo

– Если разобраться, так и у нас, бывших десантников, опыт был невелик — года не прошло, как мы начали службу в войсках. Но в боевой обстановке люди закаляются быстро, и по фронтовым меркам год — срок немалый. Потому и смотрели на нас как на бывалых, умудренных жизненным и боевым опытом людей, требовали, чтобы мы оказывали помощь врачам, кое-кто из которых был значительно старше и по возрасту, и по стажу работы в ме

🎉2custom 53980170061653052872👍1🕊1

26 Jul 2026, 23:14 UTC174 views5 reactionsread 6 August 2026
Photo

Вчера вся страна отметила День Военно-Морского Флота. Сегодня хотим поделиться редким историческим кадром: празднование 200-летия Российского флота в Санкт-Петербурге, 1896 год. На фотографии запечатлена торжественная церемония у памятника Петру I.

5

26 Jul 2026, 04:07 UTC75 views4 reactionsread 6 August 2026
Photo

⛴ Из всех объединений ВМФ ближе всего к нашему городу Каспийская флотилия, одна из старейших в стране. Она была создана по указу Петра I в 1722 году вместе с военным портом в Астрахани. В годы Великой Отечественной войны Каспий и Волга стали единой дорогой фронта. Корабли флотилии охраняли коммуникации, сопровождали транспорты и боролись с минной угрозой. По Каспию к Волге шли нефть и горючее, нужные армии, промышл

custom 53980170061653052874

24 Jul 2026, 09:51 UTC51 views4 reactionsread 6 August 2026
Photo

🎬 Победа под Сталинградом стала одним из главных символов будущего разгрома нацизма Она укрепила веру советских людей в скорую Победу и сопровождала Красную армию на всём пути: от освобождения оккупированных территорий СССР до сражений в Европе. Образ героического города быстро вошёл в кинематограф. Фильмы о победах Красной Армии показывали в Москве, Виннице, и в Вене, и в других городах, освобождённых Красной арм

21👍1

23 Jul 2026, 19:22 UTC144 views7 reactionsread 6 August 2026
Photo

Редкие фотографии довоенного Сталинграда – Смотреть пост

👍32🔥2

23 Jul 2026, 12:10 UTC171 views5 reactionsread 6 August 2026
Photo

📷 Редкие фотографии довоенного Сталинграда, сделанные канадскими коммунистами в 1933 году. Оригинал хранится в фондах Нью-Йоркской публичной библиотеки. В альбом вошли 24 снимка городских улиц, зданий и повседневной жизни. 🥰Фотографии снабжены подписями на английском и французском языках, страницы оформлены тщательно и с большим вниманием к деталям.

2👏21

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

Citation-graph rank — 1,252,252 of 1,345,403entries 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.

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

“«Наследие»” (@nasledie34), 635 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/nasledie34.

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.