Telegram RegisterThe public register of Telegram
Telegram profile photo for ᅟ 𝓑εyond thε 𝓡uƞwαy

Channel

ᅟ 𝓑εyond thε 𝓡uƞwαy

@beyondrunway

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

128subscribers

-6 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1002685045186
TypeChannel
Username@beyondrunway
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live31 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/beyondrunway

Growth

12814013414 August 2026 — 134 subscribers15 August 2026 — 135 subscribers24 August 2026 — 140 subscribers31 August 2026 — 128 subscribers14 August 202631 August 2026
4 measurements spanning 17 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 126–142 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 08:37128-12
24 Aug 2026, 01:25140+5
15 Aug 2026, 18:35135+1
14 Aug 2026, 16:02134first reading

Engagement

18 posts held, back to 10 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
39.4%
avg views ÷ 128 subscribers
Avg views / post
50.4
18 posts measured
Reaction rate
45.4%
reactions ÷ views · ER floor
Posts in window
18
of 18 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 3 of 18 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 14 August 2026
Posts held18 (10 August 202614 August 2026)
Views total907
Reactions total84
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 16: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

84 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 50623072483200221612833.3%
custom 50623843043282808492833.3%
custom 50646084445525784522833.3%

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 are Telegram’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 3 of the 18 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 84 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 10 August 2026 to 14 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

14 Aug 2026, 13:56 UTC10 viewsread 14 August 2026

⁣֖֥ ׄ ׅ ۪𝐌 ᩡ ׅ⠀𝖮𝗅𝖺‌ 𝗊𝗎𝖾𝗋𝗂𝖽𝗈 𝖼𝖺‌𝗈 𝖾 𝖺𝗇𝗍𝗂𝗀𝗈 𝖺𝗆𝗎𝗅𝖾𝗍𝗈, 𝖼𝗈𝗆𝗈 𝖾𝗌𝗍𝖺‌? 𝖤𝗎 𝖾𝗌𝗉𝖾𝗋𝗈 𝗊𝗎𝖾 𝗆𝗎𝗂𝗍𝗂‌𝗌𝗌𝗂𝗆𝗈 𝖻𝖾𝗆. 𝖵𝖾𝗇𝗁𝗈 𝗇𝖾𝗌𝗌𝖺 𝗌𝖾𝗑𝗍𝖺 𝗍𝖾 𝗍𝗋𝖺𝗓𝖾𝗋 𝗎𝗆 𝗉𝖾𝗊𝗎𝖾𝗇𝗈 𝗆𝗂𝗆𝗈, 𝖺𝖿𝗂𝗇𝖺𝗅, 𝗇𝖺𝖽𝖺 𝗆𝖾𝗅𝗁𝗈𝗋 𝗉𝖺𝗋𝖺 𝗂𝗇𝗂𝖼𝗂𝖺𝗋 𝗈 𝖿𝗂𝗆 𝖽𝖾 𝗌𝖾𝗆𝖺𝗇𝖺 𝖼𝗈𝗆 𝗎𝗆 𝖻𝗈𝗆 𝖽𝗈𝖼𝖾. 𝖠𝗉𝗋𝗈𝗏𝖾𝗂𝗍𝖺𝗇𝖽𝗈 𝗉𝖺𝗋𝖺 𝖼𝗈𝗆𝗎𝗇𝗂𝖼𝖺𝗋 𝗊𝗎𝖾 𝗈 𝖺𝗇𝗍𝗂𝗀𝗈 "𝗌𝗁𝖺𝖽𝗈𝗐𝗈𝗆𝖺𝗇" 𝗏𝖾𝗂𝗈 𝖺𝗈 𝗌𝖾𝗎 𝖽𝖾𝗏𝗂𝖽𝗈 𝖽𝖾𝗌𝖼𝖺𝗇𝗌𝗈 𝖾 𝖺𝗀𝗈𝗋𝖺 𝗌𝗈𝗆𝗈𝗌 𝗀𝗈𝗅𝖾 𝖽𝖾 𝗌𝖺𝗇𝗀𝗋𝗂𝖺, 𝖾𝗌𝗉𝖾𝗋𝗈 𝗊𝗎𝖾 𝖽𝖾𝗌𝖿𝗋𝗎𝗍𝖾 𝖽𝖾 𝗇𝗈𝗌𝗌𝖺 𝗃𝗈𝗋𝗇𝖺𝖽𝖺 𝗉𝗈𝗂𝗌 𝗌𝖾𝗋𝖾𝗂 𝖾𝗎 𝗊𝗎𝖾 𝗀𝗎𝗂𝖺𝗋𝖾𝗂 𝗌𝖾𝗎 𝖽𝖾𝗌𝖼𝖺𝗇𝗌𝗈 𝖾𝗍𝖾𝗋𝗇𝗈. ᅠᅠᅠᅠᅠᅠ𝘥𝘢 𝘴𝘶𝘢 𝘲𝘶𝘦𝘳𝘪

14 Aug 2026, 13:56 UTC9 viewsread 14 August 2026

Estou com uma leve preguiça de começar a arrumar os resultados 😭

13 Aug 2026, 23:04 UTC141 viewsread 14 August 2026

ㅤㅤ ㅤ ㅤㅤ 🤩✒️✒️✒️✒️✒️✒️✒️✒️✒️ 🤩 𝐂𝐫𝐢𝐞 𝐚 𝐬𝐮𝐚 𝐈𝐝𝐞𝐧𝐭𝐢𝐝𝐚𝐝𝐞 𝐅𝐚𝐬𝐡𝐢𝐨𝐧 🍓 ✒️ Estilo não é apenas aquilo que vestimos. É a forma como escolhemos ser vistos, as referências que carregamos e os detalhes que fazem algo ter a nossa cara. Para a RAW, cada identidade possui uma linguagem própria. ✒️gora é a sua vez de construir a sua. ⠀ 🍓⠀me diga: @ (da sua preferência) + sua esté

12 Aug 2026, 23:39 UTC52 views24 reactionsread 14 August 2026
Photo

⁣ ⁣ ⁣ ⁣ ⁣ ⁣ ⁣⁣ ⁣⁣ 🤩 ⁣𝐃𝐀𝐕𝐈𝐒 🍒 𝗦𝗧𝗢𝗥𝗬 나오미 🍒 𝗳𝖺𝗌𝗁𝗂𝗈𝗇 𝗀𝗈𝖾𝗌 𝗼𝗎𝗍 𝗈𝖿 𝘀𝗍𝗒𝗅𝖾, 𝖻𝗎𝗍 𝘀𝗍𝗒𝗅𝖾 𝗇𝖾𝗏𝖾𝗋 𝗱𝗈𝖾𝗌.

custom 50623072483200221618custom 50623843043282808498custom 50646084445525784528

Showing the 12 most recent of 18 posts we hold for @beyondrunway. 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 — 313,065 of 1,629,452 entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“ᅟ 𝓑εyond thε 𝓡uƞwαy” (@beyondrunway), 128 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/beyondrunway.

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.