Telegram RegisterThe public register of Telegram
Telegram profile photo for InPlay Alerts

Channel

InPlay Alerts

@inplayalertsmatt

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

259subscribers

+83 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-1003822211339
TypeChannel
Username@inplayalertsmatt
CreatedBetween 1 February 2026 and 24 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 October 2026
Measurements held10
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/inplayalertsmatt

Topic

Sports — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 76% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

174259216.57 August 2026 — 176 subscribers8 August 2026 — 175 subscribers8 August 2026 — 175 subscribers15 August 2026 — 174 subscribers22 August 2026 — 190 subscribers28 August 2026 — 205 subscribers5 September 2026 — 202 subscribers14 September 2026 — 201 subscribers28 September 2026 — 231 subscribers8 October 2026 — 259 subscribers7 August 20268 October 2026
10 measurements spanning 62 days, net +83. 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 161–272 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 05:41259+28
28 Sept 2026, 11:19231+30
14 Sept 2026, 05:01201-1
5 Sept 2026, 17:42202-3
28 Aug 2026, 12:52205+15
22 Aug 2026, 07:17190+16
15 Aug 2026, 03:55174-1
8 Aug 2026, 14:01175no change
8 Aug 2026, 06:31175-1
7 Aug 2026, 08:17176first reading

Engagement

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

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

6 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥6100.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 3 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 6 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 24 July 2026 to 7 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

7 Aug 2026, 17:47 UTC43 viewsread 8 August 2026

🏟️ Match : AIK (W) vs Brommapojkarna (W) 🏆 Ligue : Sweden Damallsvenskan ⏱️ Minute : 45 ⚽ Live score : 0-0 🥅 Premier but : Aucun 🎯 Hit Over 0.5 HT : 8.00 Résultat : ❌ Loss

7 Aug 2026, 17:47 UTC43 viewsread 8 August 2026

🏟️ Match : Polonia Sroda Wlkp vs Victoria Wrzesnia 🏆 Ligue : Poland III Liga ⏱️ Minute : 45 ⚽ Live score : 1-0 🥅 Premier but : 30' 🎯 Hit Over 0.5 HT : 2.25 Résultat : ✅ Win

7 Aug 2026, 16:50 UTC53 viewsread 8 August 2026

🏟️ Match : FCJ Blackbird vs JJK/2 🏆 Ligue : Finland Kolmonen ⏱️ Minute : 45 ⚽ Live score : 2-0 🥅 Deuxième but : 40' 🎯 Hit Over 1.5 HT : 3.00 Résultat : ✅ Win

7 Aug 2026, 16:50 UTC56 viewsread 8 August 2026

🏟️ Match : LTU vs ACF 🏆 Ligue : Finland Kolmonen ⏱️ Minute : 45 ⚽ Live score : 1-0 🥅 Premier but : 17' 🎯 Hit Over 0.5 HT : 1.53 Résultat : ✅ Win

7 Aug 2026, 16:24 UTC56 views1 reactionsread 8 August 2026

🇨🇵 Tout se passe ici si tu veux nous rejoindre : 📌 https://im.page/inplayalerts ✅ 20€ / mois. Les alertes arrivent de façon automatique 24h/24 et 7j/7 des qu un match en live correspond aux modèles prédéfinis. Bonnes vacances 🥳🥳🥳🥳🥳🥳 _ 🇬🇧 Everything happens here if you'd like to join us: 📌 https://im.page/inplayalerts ✅ €20/month. Alerts are sent automatically 24/7 as soon as a live match matches one of our …

🔥1

7 Aug 2026, 16:23 UTC50 viewsread 8 August 2026

🏟️ Match : EIF Academy vs EPS Reservi 🏆 Ligue : Finland Kolmonen ⏱️ Minute : 45 ⚽ Live score : 1-0 🥅 Deuxième but : Not scored 🎯 Hit Over 1.5 HT : 3.50 Résultat : ❌ Loss

7 Aug 2026, 16:23 UTC50 viewsread 8 August 2026

🏟️ Match : Portuguesa Desportos U20 vs Juventus SP U20 🏆 Ligue : Brazil Campeonato Paulista U20 ⏱️ Minute : 45 ⚽ Live score : 1-1 🥅 Premier but : 16' 🎯 Hit Over 0.5 HT : 1.67 Résultat : ✅ Win

7 Aug 2026, 16:23 UTC50 viewsread 8 August 2026

🏟️ Match : Gremio Prudente U20 vs Capivariano U20 🏆 Ligue : Brazil Campeonato Paulista U20 ⏱️ Minute : 45 ⚽ Live score : 0-1 🥅 Premier but : 8' 🎯 Hit Over 0.5 HT : 1.57 Résultat : ✅ Win

7 Aug 2026, 16:23 UTC41 viewsread 8 August 2026

🏟️ Match : Lanzarote vs Arenas Club de Getxo 🏆 Ligue : Europe Friendlies ⏱️ Minute : 45 ⚽ Live score : 1-0 🥅 Premier but : 23' 🎯 Hit Over 0.5 HT : 1.80 Résultat : ✅ Win

7 Aug 2026, 16:23 UTC42 viewsread 8 August 2026

🏟️ Match : Tlaxcala FC vs Oaxaca 🏆 Ligue : Mexico Liga de Expansion ⏱️ Minute : 45 ⚽ Live score : 0-0 🥅 Premier but : Aucun 🎯 Hit Over 0.5 HT : 7.00 Résultat : ❌ Loss

7 Aug 2026, 16:23 UTC47 viewsread 8 August 2026

🏟️ Match : Universidad Guadalajara vs Correcaminos 🏆 Ligue : Mexico Liga de Expansion ⏱️ Minute : 45 ⚽ Live score : 1-2 🥅 Premier but : 12' 🎯 Hit Over 0.5 HT : 1.50 Résultat : ✅ Win

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

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

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.

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

“InPlay Alerts” (@inplayalertsmatt), 259 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/inplayalertsmatt.

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.