Channel
Locorajan
@locorajan
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
6,976subscribers
-240 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002119092680 |
|---|---|
| Type | Channel |
| Username | @locorajan |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/locorajan |
Topic
Other / unclassifiable — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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 |
|---|---|---|
| 16 Sept 2026, 14:19 | 6,976 | -20 |
| 13 Sept 2026, 00:37 | 6,996 | -34 |
| 8 Sept 2026, 17:19 | 7,030 | -36 |
| 3 Sept 2026, 17:57 | 7,066 | -19 |
| 31 Aug 2026, 10:36 | 7,085 | -18 |
| 28 Aug 2026, 16:12 | 7,103 | -10 |
| 26 Aug 2026, 22:28 | 7,113 | no change |
| 25 Aug 2026, 23:41 | 7,113 | -17 |
| 23 Aug 2026, 07:54 | 7,130 | -23 |
| 19 Aug 2026, 12:52 | 7,153 | -17 |
| 16 Aug 2026, 21:05 | 7,170 | -20 |
| 13 Aug 2026, 05:06 | 7,190 | -21 |
| 9 Aug 2026, 19:11 | 7,211 | -5 |
| 8 Aug 2026, 21:01 | 7,216 | 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.
@sarkariresult2409 · 47,701
Telegram ranks this channel #11 of 37 here — alongside 36 others — read 26 August 2026
@World_Geo_politcs · 27,920
Telegram ranks this channel #19 of 30 here — alongside 29 others — read 10 September 2026
@mvatika · 23,053
Telegram ranks this channel #20 of 53 here — alongside 52 others — read 19 September 2026
@adda247railway · 85,335
Telegram ranks this channel #25 of 46 here — alongside 45 others — read 18 August 2026
@Railway_Jobs_NTPC_JE_ALP_Group_D · 146,893
Telegram ranks this channel #31 of 86 here — alongside 85 others — read 12 August 2026
@WinnersInstituteIndoreAdityaSir · 698,533
Telegram ranks this channel #72 of 94 here — alongside 93 others — read 8 August 2026
This channel appears in 6 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Locorajan” (@locorajan), 6,976 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/locorajan.
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.