Posted without readable text
custom 524226374091252604111custom 53707963409618969376custom 53731728881006947216

Channel
@murmanlegacy
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
117subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002129031986 |
|---|---|
| Type | Channel |
| Username | @murmanlegacy |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 18 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 2 times, most recently 18 August 2026 |
| On Telegram | t.me/murmanlegacy |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 20:58 | 117 | no change |
| 10 Aug 2026, 02:48 | 117 | first reading |
7 posts held, back to 18 July 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 pageof 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.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 7 (18 July 2026 – 4 August 2026) |
| Views total | 237 |
| Reactions total | 72 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 02:48 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.
118 reactions across 7 posts, in 8 distinct kinds. The most used accounts for 29.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5242263740912526041 | 35 | 29.7% | |
| custom 5373172888100694721 | 19 | 16.1% | |
| custom 5370796340961896937 | 18 | 15.3% | |
| custom 5370996623876840649 | 14 | 11.9% | |
| custom 5244617992876091643 | 11 | 9.32% | |
| custom 5371023776660091993 | 11 | 9.32% | |
| custom 5242603447055840161 | 8 | 6.78% | |
| custom 5371036841950603788 | 2 | 1.69% |
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 118reactions 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 18 July 2026 to 4 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.
Posted without readable text
custom 524226374091252604111custom 53707963409618969376custom 53731728881006947216
Posted without readable text
custom 524226374091252604111custom 53731728881006947217custom 52446179928760916435
Posted without readable text
custom 53707963409618969377custom 53709966238768406495custom 53710237766600919935
Posted without readable text
custom 52446179928760916436custom 53731728881006947212custom 52426034470558401611
Временный пост! Четвертая часть Истории Мурман в статьях ВК, уже ждет вас тут
custom 53710237766600919936custom 52426034470558401613custom 53710368419506037882
🤩🤩🤩🤩🤩🤩🤩 🤩🤩🤩🤩🤩🤩🤩 Сулани, утро. На вилле Маккарти нешуточно бушуют гормоны... Хавьер и Ханна. Надеюсь, вы ещё помните эту прекрасную пару? Если вдруг подзабыли или только присоединились к нам, со всей их историей можно ознакомиться по хештегу: #хавьерханна Ребята долгое время очень хотели малыша, но никак не могли забеременеть. И вот, в тот самый долгожданный момент, когда Ханна наконец узнаёт о своей беременности, …
custom 53709966238768406499custom 52422637409125260415custom 53707963409618969375
🤩🤩🤩🤩🤩🤩🤩🤩🤩 🤩🤩🤩🤩🤩🤩 [Поместье Лютер] После всего пережитого напряжения, интриг на работе и бесконечной суеты, этой парочке как никогда нужна перезагрузка. Подальше от чужих глаз, "назойливых начальников" и душного города. Прислушиваясь к тому, как внутри Сабрисы бьются два новых маленьких сердца, Тейлор озвучивает идеальный план: бросить всё и сбежать в полноценный отпуск. Туда, где только солнце, бескрайний океан и …
custom 52422637409125260418custom 52426034470558401614custom 53731728881006947214
Showing the 7 most recent of 7 posts we hold for @murmanlegacy. 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 — 613,901 of 1,583,249entries 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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“⋄𝐒𝐚𝐛𝐫𝐢𝐁𝐞𝐳𝐚𝐦⋄𝐓𝐒𝟒⋄” (@murmanlegacy), 117 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/murmanlegacy.
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.