Telegram RegisterThe public register of Telegram
Telegram profile photo for Mathongo 2026 test series | quizzer full test series 2026 | qft 2026 | mathango | mothango

Channel

Mathongo 2026 test series | quizzer full test series 2026 | qft 2026 | mathango | mothango

@methongo26

On this record: Topic · Growth · Engagement · Cite this entry

2,310subscribers

+229 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003607079742
TypeChannel
Username@methongo26
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded18 September 2026
Last confirmed live12 October 2026
Measurements held18
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/methongo26

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 18 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

2,0812,3102,195.57 August 2026 — 2,081 subscribers8 August 2026 — 2,083 subscribers10 August 2026 — 2,105 subscribers13 August 2026 — 2,126 subscribers16 August 2026 — 2,174 subscribers19 August 2026 — 2,170 subscribers23 August 2026 — 2,168 subscribers26 August 2026 — 2,175 subscribers29 August 2026 — 2,174 subscribers1 September 2026 — 2,179 subscribers5 September 2026 — 2,199 subscribers10 September 2026 — 2,215 subscribers13 September 2026 — 2,220 subscribers18 September 2026 — 2,240 subscribers18 September 2026 — 2,240 subscribers27 September 2026 — 2,256 subscribers5 October 2026 — 2,294 subscribers12 October 2026 — 2,310 subscribers7 August 202612 October 2026
18 measurements spanning 65 days, net +229. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,047–2,344 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 00:172,310+16
5 Oct 2026, 11:392,294+38
27 Sept 2026, 10:562,256+16
18 Sept 2026, 02:252,240no change
18 Sept 2026, 02:192,240+20
13 Sept 2026, 21:362,220+5
10 Sept 2026, 05:372,215+16
5 Sept 2026, 04:222,199+20
1 Sept 2026, 06:142,179+5
29 Aug 2026, 09:282,174-1
26 Aug 2026, 13:382,175+7
23 Aug 2026, 12:082,168-2
19 Aug 2026, 13:022,170-4
16 Aug 2026, 19:142,174+48
13 Aug 2026, 17:462,126+21
10 Aug 2026, 15:512,105+22
8 Aug 2026, 00:402,083+2
7 Aug 2026, 18:502,081first 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.

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 12 October 2026 — this entry's latest reading, not the date you are reading this.

“Mathongo 2026 test series | quizzer full test series 2026 | qft 2026 | mathango | mothango” (@methongo26), 2,310 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/methongo26.

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.