Channel
NVIDIA EXAM HELP | NVIDIA OA HELP | NVIDIA TEST HELP
@codechefcodeforces
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,613subscribers
-44 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001818406540 |
|---|---|
| Type | Channel |
| Username | @codechefcodeforces |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/codechefcodeforces |
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 13 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 |
|---|---|---|
| 8 Nov 2026, 18:01 | 4,613 | -6 |
| 5 Nov 2026, 05:51 | 4,619 | +3 |
| 2 Nov 2026, 11:40 | 4,616 | -6 |
| 30 Oct 2026, 14:06 | 4,622 | -2 |
| 21 Oct 2026, 15:09 | 4,624 | -2 |
| 18 Oct 2026, 13:56 | 4,626 | -1 |
| 15 Oct 2026, 05:55 | 4,627 | -8 |
| 12 Oct 2026, 07:21 | 4,635 | -18 |
| 5 Oct 2026, 21:40 | 4,653 | -15 |
| 28 Sept 2026, 14:39 | 4,668 | -13 |
| 19 Sept 2026, 07:02 | 4,681 | -2 |
| 15 Sept 2026, 05:41 | 4,683 | +5 |
| 11 Sept 2026, 15:16 | 4,678 | -1 |
| 6 Sept 2026, 14:36 | 4,679 | +3 |
| 2 Sept 2026, 21:51 | 4,676 | no change |
| 2 Sept 2026, 03:15 | 4,676 | -7 |
| 29 Aug 2026, 19:36 | 4,683 | +4 |
| 26 Aug 2026, 17:58 | 4,679 | -1 |
| 23 Aug 2026, 23:57 | 4,680 | -1 |
| 19 Aug 2026, 22:48 | 4,681 | 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.
@infosys_hackwithinfy_help_exam · 19,257
Telegram ranks this channel #13 of 67 here — alongside 66 others — read 30 September 2026
@cpabhinav · 21,110
Telegram ranks this channel #40 of 57 here — alongside 56 others — read 23 September 2026
@offcampus_phodenge · 63,825
Telegram ranks this channel #64 of 76 here — alongside 75 others — read 21 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“NVIDIA EXAM HELP | NVIDIA OA HELP | NVIDIA TEST HELP” (@codechefcodeforces), 4,613 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/codechefcodeforces.
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.