Telegram RegisterThe public register of Telegram
Telegram profile photo for Понт Аксинский

Channel

Понт Аксинский

@pont_aksinskiy

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

1,949subscribers

+4 since we began measuring on 7 August 2026

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

Register entry

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

Growth

1,9451,9491,9477 August 2026 — 1,945 subscribers7 August 2026 — 1,945 subscribers11 August 2026 — 1,948 subscribers15 August 2026 — 1,949 subscribers7 August 202615 August 2026
4 measurements spanning 8 days, net +4. 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 1,944–1,950 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 02:121,949+1
11 Aug 2026, 12:031,948+3
7 Aug 2026, 15:021,945no change
7 Aug 2026, 12:121,945first reading

Engagement

7 posts held, back to 29 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
32.1%
avg views ÷ 1,949 subscribers
Avg views / post
626
7 posts measured
Reaction rate
7.99%
reactions ÷ views · ER floor
Posts in window
7
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 6 August 2026
Posts held7 (29 July 20266 August 2026)
Views total4,382
Reactions total350
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 15: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.

What this channel posts

Video runtime
1m 24s
Average length
1m 24s

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

350 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 47.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 611404772868410727516547.1%
custom 538910302917573376811232.0%
custom 53417314296864703277220.6%
custom 531204830940838515210.286%

Custom emoji. Every 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 counts beside them areTelegram’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 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 350reactions 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 29 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, 18:18 UTC254 views27 reactionsread 7 August 2026
Forwarded from @chernaya100Video

Одна из самых ярких историй о русской доблести в Первой Мировой — из уст прекрасной Аксиньи. Почитать подробности обороны Осовца от непосредственных участников — тут.

custom 534173142968647032720custom 53891030291757337684custom 61140477286841072753

5 Aug 2026, 16:53 UTC397 views52 reactionsread 7 August 2026
Photo

Суровая стальная вода и мы

custom 611404772868410727526custom 538910302917573376815custom 534173142968647032711

5 Aug 2026, 16:12 UTC453 views83 reactionsread 7 August 2026
Photo

Когда поняли, что Белое море круче белого песка и уехали на Русский Север, а не в Азию ♠️

custom 611404772868410727550custom 538910302917573376822custom 534173142968647032711

31 Jul 2026, 21:22 UTC677 views37 reactionsread 7 August 2026
Forwarded from @russia_and_anvilPhoto

Явление произошло, когда в городе была белая Северная Армия во главе с генералом Е.К. Миллером. «Это знаменательное событие произошло в воскресенье, 3 августа 1919 года, накануне эвакуации из Архангельска добровольческих войск Антанты. Семеро детей от 10 до 14 лет — Галина и Ольга Зеленины, Эмилия, Валентина и Виктор Перешневы, Сергей Попов, Юлия Киселева, — находясь возле дома №135 по Новгородскому проспекту, увиде

custom 538910302917573376818custom 611404772868410727511custom 53417314296864703277custom 53120483094083851521

31 Jul 2026, 20:24 UTC≈1,400 views40 reactionsread 7 August 2026
Photo

Удивительно светлые люди в Архангельске! Каждый день — настоящий подарок в плане знакомств и встреч. Вчера познакомились с Владимиром Владимировичем, увлекшего нас беседой… Про Латгалию и прадедушку Фридриха. Он же рассказал нам с Саввой историю про чудесное явление Богородицы 3 августа 1919 года и про местную икону, этому событию посвященную. Вскоре после ухода, Владимир Владимирович вернулся к нам, и вручил списо

custom 611404772868410727523custom 538910302917573376812custom 53417314296864703275

30 Jul 2026, 13:08 UTC544 views52 reactionsread 7 August 2026
Forwarded from @russia_and_anvilPhoto

Белые в Архангельске! 30 и 31 июля 1 и 2 августа С 10:00 до 20:00 Петровский Парк, стенд Б-12 Ждём!

custom 538910302917573376831custom 611404772868410727516custom 53417314296864703275

29 Jul 2026, 20:46 UTC657 views59 reactionsread 7 August 2026
Photo

Архангельск встретил красиво.

custom 611404772868410727536custom 534173142968647032713custom 538910302917573376810

Showing the 7 most recent of 7 posts we hold for @pont_aksinskiy. 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 — 267,447 of 1,481,306entries 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

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.

Mentions

Named by 4 registered channels — 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.

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.

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

“Понт Аксинский” (@pont_aksinskiy), 1,949 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/pont_aksinskiy.

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.