Telegram RegisterThe public register of Telegram
Telegram profile photo for 📣 Yerevan Run [ENG]

Channel

📣 Yerevan Run [ENG]

@YerevanRunEngNews

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

282subscribers

+10 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-1002477081760
TypeChannel
Username@YerevanRunEngNews
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/YerevanRunEngNews

Growth

2722822776 August 2026 — 272 subscribers6 August 2026 — 272 subscribers7 August 2026 — 273 subscribers14 August 2026 — 282 subscribers6 August 202614 August 2026
4 measurements spanning 8 days, net +10. 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 271–284 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 22:27282+9
7 Aug 2026, 21:46273+1
6 Aug 2026, 23:33272no change
6 Aug 2026, 23:18272first reading

Engagement

20 posts held, back to 28 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
23.1%
avg views ÷ 282 subscribers
Avg views / post
65.0
20 posts measured
Reaction rate
2.45%
reactions ÷ views · ER floor
Posts in window
20
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 5 of 20 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 held20 (28 July 20266 August 2026)
Views total1,301
Reactions total7
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 23:33 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

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
685.7%
🔥114.3%

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 5 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 7reactions 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 28 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:50 UTC21 views1 reactionsread 6 August 2026
Photo

Turtle Joggers #37 When: August 7 (Friday), 7:30 AM Distance: ~4 km Route: https://www.strava.com/routes/3426213206200822346 Pace: the mellowest (slightly faster than a walk). 🧦Dress appropriately to the weather. 📍Start: https://yandex.com/maps/-/CLWKn6Kh - here will be a warmup. 🫖☕️ After the finish, you can stay for a coffee break. There will be coffee, cups, boiling water, and cookies. You can bring your own

🔥1

Signed Andrew Roshchupkin

6 Aug 2026, 03:41 UTC48 viewsread 6 August 2026
Photo

Today (06.08), we're meeting for our "Circles" / "Kruzhochki" run at Hamalir! Distance: 5-7 km Pace: 6-6:30 min/km Start: 20:00 Meeting point: Sports & Concert Complex (meet at the top of the stairs | 📍Yandex Maps) Hosted by @eastrage 🙆‍♀️ 🙆 🙆‍♂️ 🙆‍♀️ 🙆 🙆‍♂️ 🙆‍♀️ 🙆 ❗️ Throughout August, Circles Help the Bari Mard project. After the charity market held on July 4–5, the Bari Mard team raised funds to renovate a s

Signed Евгений Истюков

5 Aug 2026, 18:39 UTC49 viewsread 6 August 2026
Photo

07.08 - 07:15 - ERAZ run SECOND TIME IN YEREVAN! Route: near Zeytun, which changes every time you look at it, from 4 to 7 km ➡️ https://www.strava.com/routes/3517605123330185926 Meeting: at 07:10 (morning) Where: Santa's house in Eraz Park | 📍Yandex.Maps Start: at 7.15 Pace: friendly (for beginners and everyone everyone everyone) Finish: same place as the start 🎒 If necessary, you can leave your belongings at the

5 Aug 2026, 11:55 UTC58 views2 reactionsread 6 August 2026
Photo

Thursday, Aug 6, 7:30 AM — Interval Training #1 🤗 Based on the poll results, we've decided to make our interval sessions as beginner-friendly as possible. The goal is to help newer runners safely improve their speed while keeping the workouts engaging for experienced runners too. If you can run 5 km continuously at any pace, this workout is definitely for you! 🏁 Training plan We'll start with a warm-up, do some run

2

Signed Andrew Roshchupkin

5 Aug 2026, 07:00 UTC61 viewsread 6 August 2026
Photo

05.08 Wednesday 20:00 - #BeerRun 5,5k - 9k Distances and pace: 🏊‍♂️ ~ risk group 5:30 - 6:00 min/km (led by @demkalkov) 9k route link 🐣 ~ health group 7:00 - 7:30 min/km ❗️UPDATED 5.5k route link Latecomers can catch the group in 6-8 minutes near the EMS station https://yandex.com/maps/-/CTrSYF2o 🕙 Gathering 19:50 You can change and leave your stuff at the bar (no valuables, pl

Signed Dementii

4 Aug 2026, 13:05 UTC70 viewsread 6 August 2026
Photo

Sunday, 08.09 — Run to Ijevan and kebab This Sunday, we will head to Tavush to run beautifully and visit the organizer of Yell Sport Fest, Ilya Tsygankov. Two routes are available—one for experienced runners and another for those for whom this trail will be one of their first. 🗺 Tracks: 🔸 10 km, 400 meters elevation gain—a circular route suitable for beginners; 🔸 27 km, 1600 meters elevation gain—a point-to-point r

4 Aug 2026, 09:39 UTC66 views0 reactionsread 6 August 2026
Photo

Wednesday, 05.08 - 07:30. Run 5 km 🛣 Distance: 5 km ⏰ Start: ~ 7:35 (meet up at 7:30) 🗺 Route 5 km: Strava ⚡️ "Healthy Risk" group 5 km — pace 6:15 – 6:30 min/km 🌱 Health group — pace 7:00 – 9:00 min/km This group is for the newest beginners, those who are just starting to run or want to start running regularly. We run with the slowest runner, and if needed, we switch to walking. Start and finish point: 📍 Kond's

Signed Sergey Stepanov

4 Aug 2026, 09:32 UTC60 viewsread 6 August 2026
Photo

20:00 August 4 - Haghtanak Park Run 🗓 When: Tuesday, August 4 ⏰ Time: 19:50 gathering, 20:00 start 📍 Where: Bridge on the lake in Victory Park 🆕 | Yandex.Maps | Google Maps 🛣 Distance: 5 km. (You can always do an extra lap) 🗾 Route - https://www.strava.com/activities/18029481001 🏓 After the run, stay for ping-pong if you wish 😎 Organizer: @ezhovme

3 Aug 2026, 16:30 UTC62 viewsread 6 August 2026
Photo

04.08 Tuesday 07:00 - Yerevan Run Club x Nike Run Club #CST at Cascade Attention, due to the heat, the session starts at 7:00 ⚠️ 🇬🇧 ENG Details - @YerevanRunEngNews The Common Strength Training workout is suitable for any fitness level 💪👟 You can leave your belongings, we will carry them up to the Cascade together with you ☀️ Bring water, hats, and sunglasses with you ⏱️ Duration: 1 hour 🕤 Starting at 7:00 AM a

3 Aug 2026, 09:49 UTC62 views3 reactionsread 6 August 2026

Schedule of other running clubs: Tuesday 22:00 - Run Baby Run Club Thursday 07:40 - Run Baby Run Club 20:00 - Nike Run Club Friday 08:00 - run with WeHike.Am Running club⛰ in Komitas Park Saturday 08:00 - Nike Run Club Sunday 08:30 - run with Founders Running Club Yerevan Run Club activities weekly schedule - https://t.me/YerevanRunEngNews/651

3

2 Aug 2026, 16:47 UTC67 viewsread 6 August 2026

Schedule for the week [August 03 - 09] = all workouts are free = Announcement for each session will be additional ================= Monday 08:00 - Surf & Run 4 km ☕️ 08:30 - Workout Morning Tuesday 07:00 - General Physical Training at Cascade YRC x NRC 20:00 - Park Pobeda Run Wednesday 07:30 - 5 km run from the tunnel ⛰ 20:00 - Beer Run Gargoyle Bar 🍻 Thursday 07:30 - Interval training 20:00 - Kruzhochki run Frid

2 Aug 2026, 16:46 UTC57 viewsread 6 August 2026
Photo

03.08, Monday - 8:00 - Surf & Run - 4 km #114 Run from Surf Coffee (led by @justblackbird ✨) #SurfRun 🗓 When: Monday, tomorrow! 7:50 meet up, 8:00 start 📍 Where: Surf Coffee Tumanyan, 13 🆕 | Yandex.Maps 🛣 Distance: ~ 4 km. (the most leisurely pace 🐢 — nobody will be left behind) Route - https://www.strava.com/routes/3265349619808514128 You can leave your things before the start. Afterwards, we'll drink delicio

Showing the 12 most recent of 20 posts we hold for @YerevanRunEngNews. 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 — 598,758 of 1,480,944entries 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 2 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.

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

“📣 Yerevan Run [ENG]” (@YerevanRunEngNews), 282 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/YerevanRunEngNews.

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.