Telegram RegisterThe public register of Telegram
Telegram profile photo for OF LiBeRTY FooTBall

Channel

OF LiBeRTY FooTBall

@FooTballFreeOFLiBeRTY

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

760subscribers

-144 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1002288221380
TypeChannel
Username@FooTballFreeOFLiBeRTY
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live5 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/FooTballFreeOFLiBeRTY

Growth

76090483213 August 2026 — 904 subscribers14 August 2026 — 904 subscribers21 August 2026 — 773 subscribers28 August 2026 — 770 subscribers5 September 2026 — 760 subscribers13 August 20265 September 2026
5 measurements spanning 22 days, net -144. 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 738–926 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 07:16760-10
28 Aug 2026, 05:25770-3
21 Aug 2026, 06:23773-131
14 Aug 2026, 12:15904no change
13 Aug 2026, 19:18904first reading

Engagement

20 posts held, back to 8 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
15.9%
avg views ÷ 760 subscribers
Avg views / post
121
6 posts measured
Reaction rate
0.767%
reactions ÷ views · ER floor
Posts in window
6
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 3 of 6 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 13 August 2026
Posts held20 (8 August 202613 August 2026)
Views total726
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 19:18 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 5 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
7100.0%

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 6 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 7 reactions 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 8 August 2026 to 13 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

13 Aug 2026, 13:20 UTC78 viewsread 13 August 2026
Photo

歐協聯 01:00 哈馬比 - 琴斯托霍瓦 哈馬比-0.5/1 歐霸盃 02:45 赫斯 - 賓菲加 全場9.5角細

Signed Free

13 Aug 2026, 02:27 UTC129 viewsread 13 August 2026
Photo

解放者杯 08:30 高士路 - 法林明高 法林明高 0💦💦💦走水 解放者杯 08:30 高士路 - 法林明高 全場8.5角細✅✅✅

Signed Free

13 Aug 2026, 02:11 UTC128 viewsread 13 August 2026
Photo

中北美杯 10:30 洛杉磯FC - 克雷塔羅 洛杉磯FC-1.5

Signed Free

12 Aug 2026, 22:44 UTC126 views1 reactionsread 13 August 2026
Photo

解放者杯 08:30 高士路 - 法林明高 法林明高 0 解放者杯 08:30 高士路 - 法林明高 全場8.5角細

1

Signed Free

12 Aug 2026, 22:43 UTC122 views1 reactionsread 13 August 2026
Photo

歐超杯 03:00 巴黎聖日門(中) - 阿士東維拉 巴黎聖日門-0.5/1✅✅✅

1

Signed Free

12 Aug 2026, 12:58 UTC143 views1 reactionsread 13 August 2026
Photo

歐超杯 03:00 巴黎聖日門(中) - 阿士東維拉 巴黎聖日門-0.5/1

1

Signed Free

11 Aug 2026, 02:42 UTC108 viewsread 13 August 2026
Forwarded from @GodofWealthFooTbAllPhoto

歐冠盃 00:00 波杜基林特 - 聖吉羅斯 波杜基林特-0.5/1 歐冠盃 02:00 貝爾格萊德紅星 - 比爾舒華夏普爾 貝爾格萊德紅星-1.5/2 歐冠盃 03:00 里昂 - 布拉格斯巴達 全場10角大 財神3串1心水🔥

11 Aug 2026, 02:40 UTC163 viewsread 13 August 2026
Photo

歐冠盃 23:00 卡拉特 - 索菲亞利夫斯基 全場2/2.5細 歐冠盃 00:00 波杜基林特 - 聖吉羅斯 波杜基林特-0.5/1 歐冠盃 02:00 貝爾格萊德紅星 - 比爾舒華夏普爾 貝爾格萊德紅星-1.5/2 歐冠盃 02:30 格拉茨 - 費倫巴治 全場9.5細 歐冠盃 03:00 里昂 - 布拉格斯巴達 全場10角大

Signed Free

10 Aug 2026, 13:40 UTC162 viewsread 13 August 2026
Photo

荷乙 02:00 PSV燕豪芬青年隊 - 華倫丹 華倫丹-0.5 羅甲 02:30 聖格奧爾基塞普西 - 布格勒斯特星隊 布格勒斯特星隊-0.5

Signed Free

9 Aug 2026, 15:27 UTC177 viewsread 13 August 2026
Photo

芬超 22:00 英特杜古 0-0 拉迪 全場0.5/1大

Signed Free

9 Aug 2026, 14:50 UTC184 viewsread 13 August 2026
Photo

瑞典超 22:30 咸史泰斯 0-0 加爾斯 半場0.5/1大

Signed Free

9 Aug 2026, 13:28 UTC190 views1 reactionsread 13 August 2026
Photo

日職聯 17:00 東京綠茵 - 川崎前鋒 全場2/2.5細✅✅✅ 中超 19:00 河南隊 - 青島西海岸 青島西海岸+1✅✅✅ 德乙 19:30 紐倫堡 - 特雷斯登 全場2.5/3細❌💦輸半 俄超 19:30 莫斯科戴拿模 - 馬哈奇卡拉 莫斯科戴拿模-0.5/1✅✅✅

1

Signed Free

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

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 35 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“OF LiBeRTY FooTBall” (@FooTballFreeOFLiBeRTY), 760 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/FooTballFreeOFLiBeRTY.

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.