
Channel
COMPUTER LEVEL 4
@COMPUTERRLEVEL4
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,191subscribers
-83 since we began measuring on 24 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002215043694 |
|---|---|
| Type | Channel |
| Username | @COMPUTERRLEVEL4 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 October 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/COMPUTERRLEVEL4 |
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 4 October 2026 and assigned it the closest of 31 fixed categories, at 75% 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 |
|---|---|---|
| 16 Nov 2026, 09:56 | 1,191 | -1 |
| 11 Nov 2026, 07:46 | 1,192 | -6 |
| 7 Nov 2026, 11:57 | 1,198 | -4 |
| 1 Nov 2026, 20:21 | 1,202 | -3 |
| 26 Oct 2026, 10:46 | 1,205 | +2 |
| 21 Oct 2026, 04:57 | 1,203 | +1 |
| 17 Oct 2026, 21:20 | 1,202 | -1 |
| 15 Oct 2026, 02:29 | 1,203 | -3 |
| 11 Oct 2026, 11:22 | 1,206 | -2 |
| 4 Oct 2026, 19:18 | 1,208 | +9 |
| 4 Oct 2026, 04:30 | 1,199 | no change |
| 25 Sept 2026, 10:20 | 1,199 | -1 |
| 16 Sept 2026, 23:20 | 1,200 | -1 |
| 12 Sept 2026, 19:37 | 1,201 | -2 |
| 9 Sept 2026, 02:37 | 1,203 | -6 |
| 3 Sept 2026, 08:47 | 1,209 | -28 |
| 31 Aug 2026, 03:14 | 1,237 | -33 |
| 25 Aug 2026, 12:23 | 1,270 | -4 |
| 24 Aug 2026, 21:01 | 1,274 | 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.
@ayedstep · 53,458
Telegram ranks this channel #43 of 83 here — alongside 82 others — read 24 August 2026
@electAll2 · 40,305
Telegram ranks this channel #51 of 85 here — alongside 84 others — read 5 September 2026
@Qassim_QU · 33,398
Telegram ranks this channel #51 of 83 here — alongside 82 others — read 5 September 2026
@Dailk4ielts_quizzes · 18,959
Telegram ranks this channel #56 of 84 here — alongside 83 others — read 4 October 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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“COMPUTER LEVEL 4” (@COMPUTERRLEVEL4), 1,191 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/COMPUTERRLEVEL4.
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.