🪢✨ Happy Raksha Bandhan ✨🪢 ♥️कुछ रिश्ते सिर्फ़ खून से नहीं, दिल से निभाए गए भरोसे से बनते हैं। ❤️ इस पावन पर्व पर हर भाई-बहन के रिश्ते में 🤝 प्यार बना रहे, 😊 खुशियाँ बनी रहें, 🌸 और जीवन हमेशा खूबसूरत यादों से भरा रहे। आप सभी को Raksha Bandhan की हार्दिक शुभकामनाएँ! 🙏❤️🪢

Channel
PAWAN JAIPUR™
@PAWAN_JAIPUR9
On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
13,216subscribers
-1,370 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001473466243 |
|---|---|
| Type | Channel |
| Username | @PAWAN_JAIPUR9 |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 23 October 2026 |
| Measurements held | 47 |
| Confirmed unchanged | 1 time, most recently 23 October 2026 |
| On Telegram | t.me/PAWAN_JAIPUR9 |
Topic
Memes & entertainment — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Oct 2026, 21:44 | 13,216 | -8 |
| 22 Oct 2026, 19:19 | 13,224 | -16 |
| 21 Oct 2026, 14:28 | 13,240 | -10 |
| 20 Oct 2026, 11:05 | 13,250 | -18 |
| 19 Oct 2026, 07:55 | 13,268 | -11 |
| 18 Oct 2026, 10:20 | 13,279 | -13 |
| 17 Oct 2026, 07:31 | 13,292 | -19 |
| 16 Oct 2026, 06:20 | 13,311 | -20 |
| 15 Oct 2026, 09:38 | 13,331 | -7 |
| 14 Oct 2026, 10:46 | 13,338 | -13 |
| 12 Oct 2026, 22:45 | 13,351 | -61 |
| 8 Oct 2026, 09:57 | 13,412 | -86 |
| 3 Oct 2026, 22:20 | 13,498 | -113 |
| 25 Sept 2026, 07:20 | 13,611 | -78 |
| 17 Sept 2026, 06:22 | 13,689 | -22 |
| 15 Sept 2026, 08:59 | 13,711 | -18 |
| 13 Sept 2026, 18:55 | 13,729 | -27 |
| 12 Sept 2026, 03:55 | 13,756 | -41 |
| 9 Sept 2026, 21:02 | 13,797 | -58 |
| 6 Sept 2026, 16:18 | 13,855 | first reading |
Engagement
22 posts held, back to 10 April 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 51 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 22 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Happy Independence Day 🫡
🇩🇪 MUMBAI (MI) 🇩🇪 WIN* ✅
28-29🇸🇾 MUMBAI 🇸🇾FAV.. LOSS CUT & BOOK SET 😍 CASHOUT KRO SABHI... ENJOY GUYS ❤️
66-7 🇩🇪 GUJARAT 🇩🇪 FAV TAKE YOUR 1ST ENTRY ✅
INDIAN PREMIER LEAGUE 2026 𓀬𓀬 MATCH WINNER 𓀬𓀬 ★ MUMBAI JEETAGA 💯 ★ ANGHUTA LAGWALO 👍 APNI TEAM LOW BHAW LAG JAYEGA TOH MERA GUARANTEE KHATAM!! 👉 PAWAN JAIPUR KO FOLLOW 👉 MERE OPPOSITE MAT JANA 👉 UPAR KE 2 RULE MAT BHULNA 𝐑𝐄𝐏𝐎𝐑𝐓 𝐒𝐄𝐀𝐋𝐄𝐃 𝐁𝐘, 𝐏𝐀𝐖𝐀𝐍 𝐉𝐀𝐈𝐏𝐔𝐑 sᴇᴀʀᴄʜ ᴏɴ ɢᴏᴏɢʟᴇ
🇩🇪 BENGALURU (RCB) 🇩🇪 WIN* ✅
INDIAN PREMIER LEAGUE 2026 𓀬𓀬 MATCH WINNER 𓀬𓀬 ★ BENGALURU JEETAGA 💯 ★ ANGHUTA LAGWALO 👍 APNI TEAM LOW BHAW LAG JAYEGA TOH MERA GUARANTEE KHATAM!! 👉 PAWAN JAIPUR KO FOLLOW 👉 MERE OPPOSITE MAT JANA 👉 UPAR KE 2 RULE MAT BHULNA 𝐑𝐄𝐏𝐎𝐑𝐓 𝐒𝐄𝐀𝐋𝐄𝐃 𝐁𝐘, 𝐏𝐀𝐖𝐀𝐍 𝐉𝐀𝐈𝐏𝐔𝐑 sᴇᴀʀᴄʜ ᴏɴ ɢᴏᴏɢʟᴇ
BENGALURU JEETAGA 🔥🔥 BENGALURU KE SAATH RAHENGE...❤️
🇩🇪 CHENNAI (CSK) 🇩🇪 WIN* ✅
INDIAN PREMIER LEAGUE 2026 𓀬𓀬 MATCH WINNER 𓀬𓀬 ★ CHENNAI JEETAGA 💯 ★ ANGHUTA LAGWALO 👍 APNI TEAM LOW BHAW LAG JAYEGA TOH MERA GUARANTEE KHATAM!! 👉 PAWAN JAIPUR KO FOLLOW 👉 MERE OPPOSITE MAT JANA 👉 UPAR KE 2 RULE MAT BHULNA 𝐑𝐄𝐏𝐎𝐑𝐓 𝐒𝐄𝐀𝐋𝐄𝐃 𝐁𝐘, 𝐏𝐀𝐖𝐀𝐍 𝐉𝐀𝐈𝐏𝐔𝐑 sᴇᴀʀᴄʜ ᴏɴ ɢᴏᴏɢʟᴇ
🇩🇪 BENGALURU 🇩🇪 WIN ✔️✔️
Showing the 12 most recent of 22 posts we hold for @PAWAN_JAIPUR9. 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.
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.
@SESSION_KING_CRICKET_DANIEL8 · 45,353
Telegram ranks this channel #2 of 51 here — alongside 50 others — read 26 August 2026
@pawan_jaipur · 84,538
Telegram ranks this channel #12 of 23 here — alongside 22 others — read 1 September 2026
@Vipin_Singh_Officiial · 26,077
Telegram ranks this channel #20 of 40 here — alongside 39 others — read 10 September 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists 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 23 October 2026 — this entry's latest reading, not the date you are reading this.
“PAWAN JAIPUR™” (@PAWAN_JAIPUR9), 13,216 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/PAWAN_JAIPUR9.
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.