Telegram RegisterThe public register of Telegram
Telegram profile photo for Ind. Cum Foundation Batch 7Am to 12Pm

Channel

Ind. Cum Foundation Batch 7Am to 12Pm

@HM7to12Pm

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

3,487subscribers

+33 since we began measuring on 1 September 2026

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

Register entry

Telegram ID-1001634050119
TypeChannel
Username@HM7to12Pm
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 September 2026
Last confirmed live17 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/HM7to12Pm

Topic

Other / unclassifiable — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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

3,4543,4873,470.51 September 2026 — 3,454 subscribers4 September 2026 — 3,455 subscribers8 September 2026 — 3,455 subscribers9 September 2026 — 3,467 subscribers13 September 2026 — 3,470 subscribers17 September 2026 — 3,487 subscribers1 September 202617 September 2026
6 measurements spanning 16 days, net +33. 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 3,449–3,492 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 08:553,487+17
13 Sept 2026, 11:183,470+3
9 Sept 2026, 09:403,467+12
8 Sept 2026, 13:553,455no change
4 Sept 2026, 10:573,455+1
1 Sept 2026, 08:303,454first 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.

Result Mitra
@rresultmitraofficial · 33,456
Telegram ranks this channel #8 of 40 here — alongside 39 others — read 4 September 2026
Target UPSI TargetOn- Ravi Sir
@uppwithravisir · 36,673
Telegram ranks this channel #33 of 76 here — alongside 75 others — read 1 September 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“Ind. Cum Foundation Batch 7Am to 12Pm” (@HM7to12Pm), 3,487 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/HM7to12Pm.

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.