Telegram RegisterThe public register of Telegram
Telegram profile photo for Yara_3

Channel

Yara_3

@yaraloko14

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

228subscribers

-4 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002306964982
TypeChannel
Username@yaraloko14
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/yaraloko14

Growth

2282322307 August 2026 — 232 subscribers8 August 2026 — 232 subscribers16 August 2026 — 228 subscribers7 August 202616 August 2026
3 measurements spanning 9 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 227–233 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 08:55228-4
8 Aug 2026, 10:05232no change
7 Aug 2026, 18:31232first reading

Engagement

20 posts held, back to 30 March 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
61.8%
avg views ÷ 228 subscribers
Avg views / post
141
3 posts measured
Reaction rate
3.64%
reactions ÷ views · ER floor
Posts in window
3
of 20 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 2 of 3 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 1 August 2026
Posts held20 (30 March 20261 August 2026)
Views total423
Reactions total12
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 10:05 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

98 reactions across 16 posts, in 5 distinct kinds. The most used accounts for 48.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52402254353331866424748.0%
custom 51907849543924073232525.5%
custom 53234703153705852851515.3%
custom 524032927475749088277.14%
custom 528319576279089973544.08%

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

Measured over the 20 most recent posts we hold, published 30 March 2026 to 1 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

1 Aug 2026, 09:25 UTC93 viewsread 8 August 2026
Forwarded from @lokomotivacademyPhoto

Поражение сегодня у #Локо2011

25 Jul 2026, 10:41 UTC137 views4 reactionsread 8 August 2026
Forwarded from @lokomotivacademyPhoto

Громим «Мастер-Сатурн» на выезде 💥 Так держать, паровозы! ❤️

custom 52402254353331866424

25 Jul 2026, 10:41 UTC193 views8 reactionsread 8 August 2026
Forwarded from @lokomotivacademyPhoto

Делимся отличным настроением и заряжаем болельщиков позитивом этой победной фотографией #Локо2011 😍

custom 52402254353331866424custom 51907849543924073233custom 52403292747574908821

8 Jul 2026, 12:47 UTC238 views8 reactionsread 8 August 2026
Forwarded from @fclokomotivPhoto

Поздравляем с Днём семьи, любви и верности! ❤️💚 Желаем всем счастья, мира и гармонии! 🙌

custom 51907849543924073235custom 52402254353331866422custom 53234703153705852851

4 Jul 2026, 09:38 UTC355 views6 reactionsread 8 August 2026

браво парни❤️

custom 51907849543924073235custom 52402254353331866421

4 Jul 2026, 09:38 UTC275 views10 reactionsread 8 August 2026
Forwarded from @lokomotivacademyPhoto

ЭТО ДЕРБИ ЗА НАМИ ❤️💚 С победой, «Локомотив»!

custom 52402254353331866426custom 51907849543924073234

20 Jun 2026, 09:04 UTC361 views15 reactionsread 8 August 2026
Forwarded from @lokomotivacademyPhoto

Есть «сухая» победа в Ростове у #Локо2011

custom 52402254353331866427custom 53234703153705852855custom 52403292747574908823

17 Jun 2026, 10:46 UTC357 views0 reactionsread 8 August 2026
Forwarded from @lokomotivacademyPhoto

Внимание! Внимание! Возвращается чемпионат ЮФЛ ⚡️ В субботу паровозы встретятся с соперниками на юге: #Локо2010 сыграет с «Краснодаром», а #Локо2011 — с «Ростовом» 🤜 #Локо2010: 🏆 7-й тур ЮФЛ U-16 📍Стадион Академии ФК «Краснодар» 🕐 17:00 📹 Трансляция будет в день матча #Локо2011: 🏆 21-й тур ЮФЛ U-15 📍Стадион «Локомотив» 🕐 10:00 📹 Трансляция будет в день матча Заряжены возобновить соревнование успешно 🔥

27 May 2026, 13:40 UTC427 views15 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 524022543533318664210custom 51907849543924073235

23 May 2026, 10:03 UTC412 views9 reactionsread 8 August 2026
Forwarded from @lokomotivacademyPhoto

Солнечная, яркая и тёплая (и совсем не из-за погоды 🤫) победная фотография #Локо2011 ❤️💚

custom 52402254353331866426custom 52403292747574908823

17 May 2026, 10:29 UTC426 views9 reactionsread 8 August 2026
Forwarded from @yflrussiaPhoto

САМАЯ КРУПНАЯ ПОБЕДА ЭТОГО СЕЗОНА 🔥 «Локомотив» отправил в сетку ворот МФА ДЕСЯТЬ мячей 🫣

custom 53234703153705852856custom 52831957627908997353

17 May 2026, 09:47 UTC326 views1 reactionsread 8 August 2026
Forwarded from @lokomotivacademyPhoto

Впечатляющий разгром Московской футбольной академии от #Локо2011 💥 Браво, команда!

custom 52402254353331866421

Showing the 12 most recent of 20 posts we hold for @yaraloko14. 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.

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.

Mentions

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

“Yara_3” (@yaraloko14), 228 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/yaraloko14.

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.