Channel
RRB NTPC, GROUP-D, ALP, JE, SECTION CONTROLLER,TECNICIAN & All Railway exam gateway.
@railway_rrb_ntpc_rrb_group_d
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,633subscribers
-15 since we began measuring on 23 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001633247139 |
|---|---|
| Type | Channel |
| Username | @railway_rrb_ntpc_rrb_group_d |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/railway_rrb_ntpc_rrb_group_d |
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 99% 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, 15:07 | 2,633 | -4 |
| 4 Nov 2026, 09:20 | 2,637 | -2 |
| 1 Nov 2026, 10:36 | 2,639 | +3 |
| 29 Oct 2026, 09:19 | 2,636 | -5 |
| 26 Oct 2026, 00:59 | 2,641 | -1 |
| 22 Oct 2026, 23:40 | 2,642 | -5 |
| 20 Oct 2026, 02:06 | 2,647 | +8 |
| 16 Oct 2026, 15:35 | 2,639 | +3 |
| 13 Oct 2026, 10:09 | 2,636 | +10 |
| 7 Oct 2026, 03:39 | 2,626 | -3 |
| 30 Sept 2026, 00:57 | 2,629 | +7 |
| 16 Sept 2026, 11:41 | 2,622 | +1 |
| 14 Sept 2026, 14:55 | 2,621 | no change |
| 8 Sept 2026, 06:39 | 2,621 | -8 |
| 2 Sept 2026, 20:47 | 2,629 | -4 |
| 31 Aug 2026, 03:16 | 2,633 | -5 |
| 27 Aug 2026, 23:27 | 2,638 | -10 |
| 23 Aug 2026, 11:15 | 2,648 | 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.
@govjob_result · 23,695
Telegram ranks this channel #4 of 47 here — alongside 46 others — read 16 September 2026
@sarkarijobnews · 38,820
Telegram ranks this channel #23 of 60 here — alongside 59 others — read 30 August 2026
@Guideratul · 57,750
Telegram ranks this channel #56 of 72 here — alongside 71 others — read 23 August 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“RRB NTPC, GROUP-D, ALP, JE, SECTION CONTROLLER,TECNICIAN & All Railway exam gateway.” (@railway_rrb_ntpc_rrb_group_d), 2,633 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/railway_rrb_ntpc_rrb_group_d.
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.