Channel
Railway engineer
@rrbexams2025
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,711subscribers
-46 since we began measuring on 30 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001403386763 |
|---|---|
| Type | Channel |
| Username | @rrbexams2025 |
| Created | Between 1 February 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 24 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/rrbexams2025 |
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 24 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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, 10:49 | 1,711 | -3 |
| 4 Nov 2026, 04:47 | 1,714 | -3 |
| 31 Oct 2026, 22:40 | 1,717 | -1 |
| 28 Oct 2026, 13:19 | 1,718 | -2 |
| 25 Oct 2026, 07:27 | 1,720 | -2 |
| 22 Oct 2026, 00:41 | 1,722 | -2 |
| 18 Oct 2026, 19:26 | 1,724 | -2 |
| 16 Oct 2026, 03:14 | 1,726 | -2 |
| 13 Oct 2026, 06:11 | 1,728 | -5 |
| 7 Oct 2026, 03:57 | 1,733 | -4 |
| 30 Sept 2026, 15:57 | 1,737 | -5 |
| 24 Sept 2026, 02:19 | 1,742 | no change |
| 16 Sept 2026, 02:37 | 1,742 | -4 |
| 12 Sept 2026, 19:18 | 1,746 | -4 |
| 9 Sept 2026, 04:39 | 1,750 | -4 |
| 4 Sept 2026, 02:56 | 1,754 | -3 |
| 30 Aug 2026, 18:30 | 1,757 | 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.
@TrulyEngineers · 38,538
Telegram ranks this channel #18 of 79 here — alongside 78 others — read 31 August 2026
@PrashantChaturvedi · 29,783
Telegram ranks this channel #20 of 73 here — alongside 72 others — read 8 September 2026
@officialresultbharat · 39,717
Telegram ranks this channel #36 of 53 here — alongside 52 others — read 30 August 2026
@uppscaelectrical · 21,489
Telegram ranks this channel #37 of 85 here — alongside 84 others — read 24 September 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.
“Railway engineer” (@rrbexams2025), 1,711 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/rrbexams2025.
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.