Channel
@GROUND_IPL_LIVE_LINE
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
47,335subscribers
+22,062 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001122920782 |
|---|---|
| Type | Channel |
| Username | @GROUND_IPL_LIVE_LINE |
| Description | TV SE 3 BALLS PEHLE 😍 🏆 Latest Updates & Cricket News 📅 Match Schedule & Teams Only For Entertainment Purposes 🏏 https://t.me/+x0hkXpJISG80N2Q1 |
| Created | Between 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/GROUND_IPL_LIVE_LINE |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 05:54 | 47,335 | -140 |
| 2 Sept 2026, 04:16 | 47,475 | -286 |
| 1 Sept 2026, 05:12 | 47,761 | -759 |
| 31 Aug 2026, 03:17 | 48,520 | -698 |
| 30 Aug 2026, 05:14 | 49,218 | -422 |
| 29 Aug 2026, 01:47 | 49,640 | -302 |
| 27 Aug 2026, 22:56 | 49,942 | +24,845 |
| 27 Aug 2026, 00:23 | 25,097 | -21 |
| 26 Aug 2026, 02:22 | 25,118 | +54 |
| 25 Aug 2026, 02:13 | 25,064 | -27 |
| 23 Aug 2026, 17:07 | 25,091 | -28 |
| 22 Aug 2026, 02:48 | 25,119 | -15 |
| 20 Aug 2026, 21:53 | 25,134 | -4 |
| 19 Aug 2026, 23:53 | 25,138 | -20 |
| 18 Aug 2026, 20:18 | 25,158 | -13 |
| 17 Aug 2026, 23:22 | 25,171 | -53 |
| 16 Aug 2026, 19:44 | 25,224 | -35 |
| 15 Aug 2026, 05:43 | 25,259 | -14 |
| 13 Aug 2026, 23:33 | 25,273 | first reading |
513 posts held, back to 12 August 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 42 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 513 (12 August 2026 – 3 September 2026) |
| Views total | 29,893 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 4 Sept 2026, 09:49 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.
Lifetime counters from Telegram’s own channel header, read 4 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
🎁Cricket, Tenis, Football, 700+ Casino, Aviator Khelo Aur Apna Loss Cover Karo 💘 Din Ho Ya Raat 24 Hours Withdrawal Only On With In 15 Minutes ✅ ⚡️ 24 Hour Service ⚡️ ❤️ FIRST LICENSED BOOK IN INDIA 🇮🇳 ⏩ Minimum ID 👉 Rs 100 📱📱Register New ID👇 https://fairplayexch365.vip https://fairplayexch365.vip 📱Whatsapp New ID..👇 😬https://wa.me/16803017906 ☺️https://wa.me/16803017906 📱Telegram Channel Link..👇 http…
WINNER✔️ 🇩🇪 AMSTERDAM 🇩🇪
RUN RATE REQD PER OVER ➡️ 5.56
38 RUNS REQD 41 BALLS ✔️
LAGANA LAGANA ✔️
13.1 OVER 134/3 📟📟
SIX!!! WOW, NICELY PLAYED THIS BALL 👌
6
HAWA ME ✔️
DAVID ON STRIKE ✔️✔️
13.1 🎾 128/3
SCORE CARD :-08 0 1 0 0 6 1 T-DAVID :-14(16) S-EDWARDS :-07(06)
Showing the 12 most recent of 513 posts we hold for @GROUND_IPL_LIVE_LINE. 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.
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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 27 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“Gʀᴏᴜɴᴅ Lɪɴᴇ™” (@GROUND_IPL_LIVE_LINE), 47,335 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/GROUND_IPL_LIVE_LINE.
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.