Channel
UP board class 10 to 12(notes, previous year question,exam date..etc)
@upboard_class10to12
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,766subscribers
+41 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 | -1001933010768 |
|---|---|
| Type | Channel |
| Username | @upboard_class10to12 |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/upboard_class10to12 |
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 100% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 02:18 | 2,766 | +14 |
| 13 Sept 2026, 14:11 | 2,752 | no change |
| 13 Sept 2026, 13:38 | 2,752 | +10 |
| 9 Sept 2026, 14:59 | 2,742 | +6 |
| 3 Sept 2026, 20:38 | 2,736 | +8 |
| 31 Aug 2026, 08:54 | 2,728 | -2 |
| 28 Aug 2026, 08:08 | 2,730 | +3 |
| 25 Aug 2026, 01:36 | 2,727 | +2 |
| 23 Aug 2026, 16:30 | 2,725 | 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.
@catalystsoni · 25,121
Telegram ranks this channel #6 of 49 here — alongside 48 others — read 14 September 2026
@Upboardhindimediumvidyakul · 71,041
Telegram ranks this channel #9 of 54 here — alongside 53 others — read 23 August 2026
@class_12th_physics_notess · 26,132
Telegram ranks this channel #11 of 68 here — alongside 67 others — read 13 September 2026
@ideasikhoupdate · 27,058
Telegram ranks this channel #13 of 53 here — alongside 52 others — read 11 September 2026
@ashishsinghlecturestelegram · 29,149
Telegram ranks this channel #26 of 70 here — alongside 69 others — read 8 September 2026
@learn_and_share_education · 54,391
Telegram ranks this channel #38 of 62 here — alongside 61 others — read 23 August 2026
This channel appears in 6 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“UP board class 10 to 12(notes, previous year question,exam date..etc)” (@upboard_class10to12), 2,766 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/upboard_class10to12.
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.