Telegram RegisterThe public register of Telegram
Telegram profile photo for ALBALONGA с Еленой Чудиновой

Channel

ALBALONGA с Еленой Чудиновой

@albalongasec

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

372subscribers

+6 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-1001531055391
TypeChannel
Username@albalongasec
Created4 September 2021measured — 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/albalongasec

Growth

3663723696 August 2026 — 366 subscribers6 August 2026 — 366 subscribers6 August 2026 — 367 subscribers13 August 2026 — 372 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net +6. 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 365–373 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 16:18372+5
6 Aug 2026, 21:08367+1
6 Aug 2026, 21:02366no change
6 Aug 2026, 17:47366first reading

Engagement

13 posts held, back to 4 August 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
46.4%
avg views ÷ 372 subscribers
Avg views / post
173
13 posts measured
Reaction rate
5.83%
reactions ÷ views · ER floor
Posts in window
13
of 13 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. It is computed over the 12 of 13 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held13 (4 August 20266 August 2026)
Views total2,246
Reactions total124
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 21:02 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

124 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 46.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍5846.8%
3830.6%
🔥2016.1%
😁75.65%
🤔10.806%

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

Measured over the 13 most recent posts we hold, published 4 August 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, 16:24 UTC108 views7 reactionsread 6 August 2026

Оперировал товарища Фрунзе проверенный товарищ - "главный Розанов Владимир Николаевич хирург Меж коллегами своими - чародей умелых рук", как воспела его советская поэзия. За анестезию отвечал " лучший специалист" Очкин. И этот лучший специалист добавил к эфиру хлороформ, чтоб, значит, лучше вштырило. Интересно, Фрунзе на столе отбиваться пробовал?

😁7

6 Aug 2026, 16:05 UTC111 views10 reactionsread 6 August 2026

В Москве до сих пор есть станция Фрунзенская. Хотя Фрунзе имел отношения к метро строительству ровно столько же, сколько и ко флоту. И к академической науке войны.

👍10

6 Aug 2026, 16:03 UTC93 views11 reactionsread 6 August 2026

К перепосту выше. Мы ещё в щенячестве очень веселились насчет того, как товарищ Фрунзе не хотел на операцию: а, может не надо? А? Но товарищ Сталин сказал: надо. Откуда мы это знали? Ведь вокруг стоял совдеп. Да вот как-то знали. И не только это. Может потому, что всё же Москва. Она, как известно, слухом полнится. И ведь да, правдивым слухом.

👍101

6 Aug 2026, 15:56 UTC71 views8 reactionsread 6 August 2026
Forwarded from @istrkalkglkPhoto

С годами обстоятельства того или иного события стираются из общественной памяти, особенно если их и так не особо афишировали, тем не менее обстоятельства эти знать нужно, иначе может получиться смешно и грустно. Михаил Васильевич Фрунзе в советском пантеоне красных командиров гражданской войны занимает непомерно большое место, хотя сам никаким военным по сути не был, его дореволюционная специализация – терроризм и с

👍8

6 Aug 2026, 13:43 UTC876 views5 reactionsread 6 August 2026

Евросоюзовские уже додумались, что в событиях в Сеуте виноват Путин. Это уже начинает напоминать анекдот про еврея, читающего антисемитскую прессу. Но вообще там по прежнему интересно. Объявление, что большая часть нелегалов отослана обратно, оказалось очковтирательством. Тысячи три были под телекамеры высланы стройными рядами, остальные остались. По официальной версии всего проникло не 60 тысяч, а 80. Это по офи

🔥3👍2

6 Aug 2026, 08:29 UTC136 views20 reactionsread 6 August 2026

Как же я устаю от идиотии общества. Только вчера с друзьями на прогулке обсуждали новый пример оной: рОман, где "Сталин вселяется в мозг Николая Второго". А сегодня мне в комментах читатель всерьез спросил о том же. И привёл мнение батюшки Ткачева: " Чтобы Россия не погибла, Николай должен был стать Сталиным". Ведь "Сталин выиграл войну". На минуточку: это при Государе разве немец дошёл до Москвы и вымаривал г

👍14🔥41🤔1

5 Aug 2026, 19:36 UTC128 views12 reactionsread 6 August 2026

Символично, что сгорел целый город декораций для фильма про Молоди. Причем именно в дни, когда гоблины и прочие Антоновские шумели по поводу даты битвы. Я думаю, что нормальный фильм об этой битве когда-нибудь должен быть. И будет. Только без антоновских и гоблинов, без невежества и опрично-сталинистских спекуляций. Без преувеличения роли этой битвы, ибо лживо преувеличивать - это тоже неуважение к тем, кто на сам

👍93

5 Aug 2026, 17:18 UTC86 views16 reactionsread 6 August 2026
Forwarded from @ordinaryczarizmPhoto

БИТВА НА ВОЖЕ. КАК РУССКИЕ ВПЕРВЫЕ ПОБИЛИ ЕВРАЗИЙЦЕВ В современной историко-политической конъюнктуре РФ все громче раздается голос со стороны юрты. Апологеты неордынского дискурса умудряются ставить на территории России памятники и открывать тропы Чингисхану, школьникам на голубом глазу рассказывают про «евразийца» Александра Невского, а сожжение русских городов и разорение православных храмов называют «уникальным

🔥13👍3

Showing the 12 most recent of 13 posts we hold for @albalongasec. 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 — 278,641 of 1,548,671entries 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.

Forward network

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.

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

Чудинова, Елена Петровна (ru.wikipedia.org)
“…yandex.ru/id/5cb1306e456a7000b3a19c3d Елена Чудинова на "Дзен"] * [https://t.me/albalongasec Елена Чудинова на "Телеграмм"] * [http://tv.radonezh…”
read 16 August 2026

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.

“ALBALONGA с Еленой Чудиновой” (@albalongasec), 372 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/albalongasec.

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.