Telegram RegisterThe public register of Telegram
Telegram profile photo for Sanjay

Channel

Sanjay

@Sanjay_Goyal_Cricket_Prediction

On this record: Growth · Engagement · Posts · Posts recorded as deleted · Telegram's recommendations · Cite this entry

1subscribers

-11,712 since we began measuring on 16 August 2026

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

Register entry

Telegram ID-1002127536225
TypeChannel
Username@Sanjay_Goyal_Cricket_Prediction
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 August 2026
Last confirmed live11 November 2026
Measurements held13
Confirmed unchanged10 times, most recently 11 November 2026
On Telegramt.me/Sanjay_Goyal_Cricket_Prediction

Growth

111,7135,85716 August 2026 — 11,713 subscribers16 August 2026 — 11,683 subscribers17 August 2026 — 11,619 subscribers18 August 2026 — 11,599 subscribers19 August 2026 — 11,572 subscribers20 August 2026 — 11,558 subscribers22 August 2026 — 11,465 subscribers23 August 2026 — 11,431 subscribers25 August 2026 — 11,374 subscribers26 August 2026 — 11,349 subscribers27 August 2026 — 11,341 subscribers28 August 2026 — 11,303 subscribers29 August 2026 — 1 subscribers16 August 202629 August 2026
13 measurements spanning 13 days, net -11,712. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 07:481-11,302
28 Aug 2026, 05:5411,303-38
27 Aug 2026, 02:4511,341-8
26 Aug 2026, 02:5211,349-25
25 Aug 2026, 04:5711,374-57
23 Aug 2026, 23:3411,431-34
22 Aug 2026, 09:1811,465-93
20 Aug 2026, 21:4811,558-14
19 Aug 2026, 23:3411,572-27
18 Aug 2026, 20:5311,599-20
17 Aug 2026, 20:5811,619-64
16 Aug 2026, 18:1711,683-30
16 Aug 2026, 03:4511,713first reading

Engagement

106 posts held, back to 10 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 24 pages 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 106 posts for this entry, the most recent from 27 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

27 Aug 2026, 14:06 UTC51 viewsread 28 August 2026

𝗘𝘂𝗿𝗼𝗽𝗲𝗮𝗻 𝗧𝟮𝟬 𝗟𝗲𝗮𝗴𝘂𝗲 𝟮𝟬𝟮𝟲 𝖬𝖺𝗍𝖼𝗁 :- 03 EDINBURGH ♈ GLASGOW 𝗪𝗶𝗻𝗻𝗲𝗿➖#EDINBURGH_ROCKERS ➥ 𝖯𝗅𝖺𝗒 𝖠𝗅𝗐𝖺𝗒𝗌 𝖲𝖺𝗆𝖾 𝖫𝗂𝗆𝗂𝗍. ➥ 𝖠𝗅𝗐𝖺𝗒𝗌 𝖥𝗈𝗅𝗅𝗈𝗐 𝖤𝗇𝗍𝗋𝗂𝖾𝗌. ➥ 𝖣𝗈 𝖭𝗈𝗍 𝖯𝗅𝖺𝗒 𝖲𝖾𝗌𝗌𝗂𝗈𝗇𝗌. ➥ 𝖡𝗈𝗈𝗄𝖲𝖾𝗍 𝖠𝗍 𝖫𝗈𝗐 𝖮𝖽𝖽𝗌. #𝗦𝗮𝗻𝗷𝗮𝘆 📲 +917877682035

27 Aug 2026, 10:44 UTC53 viewsread 28 August 2026

75-82 🇱🇻 DUBLIN 🇱🇻 ENTRY LENA START KRO ❤️✔️

27 Aug 2026, 09:22 UTC42 viewsread 28 August 2026

𝗘𝘂𝗿𝗼𝗽𝗲𝗮𝗻 𝗧𝟮𝟬 𝗟𝗲𝗮𝗴𝘂𝗲 𝟮𝟬𝟮𝟲 𝖬𝖺𝗍𝖼𝗁 :- 02 BELFAST ♈ DUBLIN 𝗪𝗶𝗻𝗻𝗲𝗿➖#BELFAST_WOLVES ➥ 𝖯𝗅𝖺𝗒 𝖠𝗅𝗐𝖺𝗒𝗌 𝖲𝖺𝗆𝖾 𝖫𝗂𝗆𝗂𝗍. ➥ 𝖠𝗅𝗐𝖺𝗒𝗌 𝖥𝗈𝗅𝗅𝗈𝗐 𝖤𝗇𝗍𝗋𝗂𝖾𝗌. ➥ 𝖣𝗈 𝖭𝗈𝗍 𝖯𝗅𝖺𝗒 𝖲𝖾𝗌𝗌𝗂𝗈𝗇𝗌. ➥ 𝖡𝗈𝗈𝗄𝖲𝖾𝗍 𝖠𝗍 𝖫𝗈𝗐 𝖮𝖽𝖽𝗌. #𝗦𝗮𝗻𝗷𝗮𝘆 📲 +917877682035

27 Aug 2026, 06:34 UTC45 viewsread 28 August 2026

Today 2 Match We Will Win ~ 2/2 In Open ❤️ #𝗦𝗮𝗻𝗷𝗮𝘆

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

Posts recorded as deleted after publishing

We recorded 7 posts on @Sanjay_Goyal_Cricket_Prediction as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
20 August 2026
Most recent seen missing
24 August 2026
Median time before seen missing
18 hours
Seen missing in the last 30 days
0

Appears in Telegram’s recommendations for other channels

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.

D BHAI D COMPANY ™ ORIGINAL
@DCOMPANY_OFFICIAL · 39,002
Telegram ranks this channel #18 of 51 here — alongside 50 others — read 16 August 2026

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.

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

“Sanjay” (@Sanjay_Goyal_Cricket_Prediction), 1 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/Sanjay_Goyal_Cricket_Prediction.

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.