Channel
LBS JAIPUR RU
@LBSJAIPUR_RU
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,726subscribers
-126 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002089293678 |
|---|---|
| Type | Channel |
| Username | @LBSJAIPUR_RU |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/LBSJAIPUR_RU |
Topic
Education — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 07:47 | 2,726 | -3 |
| 4 Nov 2026, 09:39 | 2,729 | +2 |
| 1 Nov 2026, 16:39 | 2,727 | -8 |
| 29 Oct 2026, 12:15 | 2,735 | -5 |
| 26 Oct 2026, 19:08 | 2,740 | -3 |
| 23 Oct 2026, 23:56 | 2,743 | -4 |
| 20 Oct 2026, 18:21 | 2,747 | -4 |
| 17 Oct 2026, 15:06 | 2,751 | -6 |
| 14 Oct 2026, 12:05 | 2,757 | -5 |
| 10 Oct 2026, 19:00 | 2,762 | -9 |
| 4 Oct 2026, 16:56 | 2,771 | -24 |
| 24 Sept 2026, 22:19 | 2,795 | -9 |
| 16 Sept 2026, 13:18 | 2,804 | +1 |
| 13 Sept 2026, 00:25 | 2,803 | no change |
| 12 Sept 2026, 09:55 | 2,803 | -8 |
| 8 Sept 2026, 03:38 | 2,811 | -10 |
| 2 Sept 2026, 20:39 | 2,821 | -6 |
| 31 Aug 2026, 00:14 | 2,827 | -1 |
| 28 Aug 2026, 00:24 | 2,828 | -13 |
| 24 Aug 2026, 16:43 | 2,841 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
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.
@kuldeepyadav123 · 19,323
Telegram ranks this channel #13 of 77 here — alongside 76 others — read 2 October 2026
@KalamAcademyJaipurClassTime · 70,671
Telegram ranks this channel #50 of 87 here — alongside 86 others — read 20 August 2026
@HarendraMaths · 23,191
Telegram ranks this channel #72 of 77 here — alongside 76 others — read 18 September 2026
@samyakiasjaipur · 45,105
Telegram ranks this channel #75 of 77 here — alongside 76 others — read 27 August 2026
This channel appears in 4 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“LBS JAIPUR RU” (@LBSJAIPUR_RU), 2,726 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/LBSJAIPUR_RU.
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.