Channel
सरकारी सुविधा व सरकारी नौकरी
@sarkarijob3501
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,736subscribers
-75 since we began measuring on 3 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001680489303 |
|---|---|
| Type | Channel |
| Username | @sarkarijob3501 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 23 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/sarkarijob3501 |
Topic
Job listings — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 66% 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, 18:29 | 1,736 | -2 |
| 4 Nov 2026, 14:27 | 1,738 | -1 |
| 2 Nov 2026, 00:54 | 1,739 | -5 |
| 30 Oct 2026, 00:56 | 1,744 | -5 |
| 27 Oct 2026, 04:15 | 1,749 | -3 |
| 24 Oct 2026, 04:51 | 1,752 | -4 |
| 20 Oct 2026, 22:27 | 1,756 | -6 |
| 18 Oct 2026, 02:19 | 1,762 | -4 |
| 15 Oct 2026, 02:09 | 1,766 | -1 |
| 11 Oct 2026, 17:20 | 1,767 | -11 |
| 5 Oct 2026, 14:15 | 1,778 | -9 |
| 27 Sept 2026, 12:56 | 1,787 | -9 |
| 23 Sept 2026, 15:20 | 1,796 | no change |
| 18 Sept 2026, 03:17 | 1,796 | -4 |
| 13 Sept 2026, 18:42 | 1,800 | -3 |
| 9 Sept 2026, 18:36 | 1,803 | -8 |
| 3 Sept 2026, 18:17 | 1,811 | 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.
@banknifty_nifty_live · 38,372
Telegram ranks this channel #5 of 52 here — alongside 51 others — read 15 September 2026
@THEBULLOPTIONSSS · 23,125
Telegram ranks this channel #22 of 69 here — alongside 68 others — read 17 September 2026
@THETA_GAINERS_NEHA_JAREDA · 17,445
Telegram ranks this channel #25 of 51 here — alongside 50 others — read 3 September 2026
@CrudeOil_Options_Sureshot_Calls · 16,312
Telegram ranks this channel #60 of 70 here — alongside 69 others — read 28 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.
“सरकारी सुविधा व सरकारी नौकरी” (@sarkarijob3501), 1,736 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/sarkarijob3501.
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.