Channel
SACHIN JAIPUR
@sachin_jaipur
On this record: Growth · Engagement · Telegram's recommendations · Cite this entry
7,845subscribers
-3,193 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001201448491 |
|---|---|
| Type | Channel |
| Username | @sachin_jaipur |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/sachin_jaipur |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 11:02 | 7,845 | -27 |
| 1 Sept 2026, 18:23 | 7,872 | -51 |
| 30 Aug 2026, 01:25 | 7,923 | -1,253 |
| 27 Aug 2026, 04:08 | 9,176 | -1,707 |
| 26 Aug 2026, 02:27 | 10,883 | -1 |
| 25 Aug 2026, 04:55 | 10,884 | -7 |
| 24 Aug 2026, 05:52 | 10,891 | -15 |
| 22 Aug 2026, 10:23 | 10,906 | -5 |
| 21 Aug 2026, 21:21 | 10,911 | no change |
| 20 Aug 2026, 21:57 | 10,911 | -8 |
| 19 Aug 2026, 22:08 | 10,919 | -16 |
| 18 Aug 2026, 22:36 | 10,935 | -13 |
| 17 Aug 2026, 19:23 | 10,948 | -15 |
| 16 Aug 2026, 16:56 | 10,963 | -20 |
| 15 Aug 2026, 02:13 | 10,983 | -7 |
| 12 Aug 2026, 15:43 | 10,990 | -23 |
| 11 Aug 2026, 19:15 | 11,013 | -25 |
| 11 Aug 2026, 11:45 | 11,038 | first reading |
Engagement
No public post preview. We read this entry on 22 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.
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.
@ipl_t20_toss_king · 65,187
Telegram ranks this channel #10 of 45 here — alongside 44 others — read 21 August 2026
@Monukumarsingh · 98,151
Telegram ranks this channel #11 of 39 here — alongside 38 others — read 15 August 2026
@harman_preet_kaur1 · 96,136
Telegram ranks this channel #18 of 39 here — alongside 38 others — read 16 August 2026
@BIG_BASH_LEAGUE_BBL_2024 · 143,470
Telegram ranks this channel #18 of 51 here — alongside 50 others — read 12 August 2026
@Mahakal_Cricket_Prediction_01 · 309,056
Telegram ranks this channel #18 of 41 here — alongside 40 others — read 11 August 2026
@Bk_Roy_vipin_Singh · 208,242
Telegram ranks this channel #19 of 41 here — alongside 40 others — read 11 August 2026
@shera_session_report_match_ipl · 48,380
Telegram ranks this channel #26 of 47 here — alongside 46 others — read 25 August 2026
@BadshahCricketkings · 102,470
Telegram ranks this channel #35 of 54 here — alongside 53 others — read 15 August 2026
This channel appears in 9 seed channels' Telegram-generated recommendation lists in total, of which the 8 where it ranks highest are shown above. 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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“SACHIN JAIPUR” (@sachin_jaipur), 7,845 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/sachin_jaipur.
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.