Channel
IBM Oa Help | Oa Exam Helper
@codeforces_codechef_cp
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,139subscribers
-28 since we began measuring on 21 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002176897351 |
|---|---|
| Type | Channel |
| Username | @codeforces_codechef_cp |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 October 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/codeforces_codechef_cp |
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 5 October 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 |
|---|---|---|
| 9 Nov 2026, 06:56 | 1,139 | -2 |
| 3 Nov 2026, 15:19 | 1,141 | +1 |
| 31 Oct 2026, 07:31 | 1,140 | -1 |
| 28 Oct 2026, 14:46 | 1,141 | +1 |
| 18 Oct 2026, 06:55 | 1,140 | +1 |
| 15 Oct 2026, 04:27 | 1,139 | -2 |
| 12 Oct 2026, 10:01 | 1,141 | -4 |
| 5 Oct 2026, 18:32 | 1,145 | no change |
| 27 Sept 2026, 12:02 | 1,145 | -8 |
| 18 Sept 2026, 03:37 | 1,153 | -3 |
| 13 Sept 2026, 17:16 | 1,156 | -4 |
| 9 Sept 2026, 12:35 | 1,160 | -1 |
| 3 Sept 2026, 22:01 | 1,161 | -2 |
| 31 Aug 2026, 23:59 | 1,163 | -3 |
| 28 Aug 2026, 15:52 | 1,166 | -1 |
| 21 Aug 2026, 10:15 | 1,167 | 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.
@jobsandinternshipsupdates · 43,179
Telegram ranks this channel #3 of 72 here — alongside 71 others — read 28 August 2026
@jobs_tcs_infosys_wipro_cognizant · 63,315
Telegram ranks this channel #59 of 73 here — alongside 72 others — read 21 August 2026
This channel appears in 2 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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“IBM Oa Help | Oa Exam Helper” (@codeforces_codechef_cp), 1,139 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/codeforces_codechef_cp.
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.