Telegram RegisterThe public register of Telegram
Telegram profile photo for EduBack - CLASS 6th 7th 8th 9th 10th 11th 12th JEE NEET

Channel

EduBack - CLASS 6th 7th 8th 9th 10th 11th 12th JEE NEET

@EduBack

Has discussion group

On this record: Topic · Growth · Engagement · Citations · Telegram's recommendations · Cite this entry

6,172subscribers

-100 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-1001458398994
TypeChannel
Username@EduBack
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded28 August 2026
Last confirmed live21 October 2026
Measurements held17
Confirmed unchanged1 time, most recently 21 October 2026
On Telegramt.me/EduBack

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

6,1656,2726,218.57 August 2026 — 6,272 subscribers8 August 2026 — 6,271 subscribers13 August 2026 — 6,263 subscribers19 August 2026 — 6,259 subscribers25 August 2026 — 6,251 subscribers28 August 2026 — 6,251 subscribers29 August 2026 — 6,249 subscribers31 August 2026 — 6,238 subscribers9 September 2026 — 6,236 subscribers13 September 2026 — 6,229 subscribers17 September 2026 — 6,220 subscribers26 September 2026 — 6,200 subscribers5 October 2026 — 6,177 subscribers12 October 2026 — 6,170 subscribers15 October 2026 — 6,165 subscribers18 October 2026 — 6,177 subscribers21 October 2026 — 6,172 subscribers6,1727 August 202621 October 2026
17 measurements spanning 75 days, net -100. 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 6,149–6,288 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Oct 2026, 09:276,172-5
18 Oct 2026, 10:496,177+12
15 Oct 2026, 02:566,165-5
12 Oct 2026, 02:366,170-7
5 Oct 2026, 05:416,177-23
26 Sept 2026, 07:226,200-20
17 Sept 2026, 13:386,220-9
13 Sept 2026, 10:206,229-7
9 Sept 2026, 20:556,236-2
31 Aug 2026, 22:386,238-11
29 Aug 2026, 08:066,249-2
28 Aug 2026, 22:296,251no change
25 Aug 2026, 22:296,251-8
19 Aug 2026, 13:186,259-4
13 Aug 2026, 11:256,263-8
8 Aug 2026, 04:526,271-1
7 Aug 2026, 13:066,272first 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.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 12 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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.

Biology Notes Class 11th 12th
@biology_Notes_Class_11_12th_NEET · 27,702
Telegram ranks this channel #15 of 50 here — alongside 49 others — read 9 September 2026
CLASS 12 CBSE
@Class_12_CBSE_Study_Material · 43,393
Telegram ranks this channel #19 of 57 here — alongside 56 others — read 28 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 21 October 2026 — this entry's latest reading, not the date you are reading this.

“EduBack - CLASS 6th 7th 8th 9th 10th 11th 12th JEE NEET” (@EduBack), 6,172 subscribers as measured 21 October 2026. Telegram Register, tgregister.com/channel/EduBack.

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.