Telegram RegisterThe public register of Telegram
Telegram profile photo for IT Jobs In Bengaluru

Supergroup

IT Jobs In Bengaluru

@ITJobsinBengaluru

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

1,250members

-50 since we began measuring on 8 August 2026

23 online right now

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

Register entry

Telegram ID-1001451684379
TypeSupergroup
Username@ITJobsinBengaluru
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 October 2026
Last confirmed live11 October 2026
Measurements held16
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/ITJobsinBengaluru

Topic

Job listings — 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 3 October 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

1,2501,3001,2758 August 2026 — 1,300 members11 August 2026 — 1,297 members15 August 2026 — 1,295 members18 August 2026 — 1,294 members21 August 2026 — 1,291 members24 August 2026 — 1,288 members27 August 2026 — 1,284 members31 August 2026 — 1,281 members3 September 2026 — 1,279 members8 September 2026 — 1,276 members13 September 2026 — 1,274 members17 September 2026 — 1,272 members26 September 2026 — 1,265 members3 October 2026 — 1,265 members5 October 2026 — 1,254 members11 October 2026 — 1,250 members8 August 202611 October 2026
16 measurements spanning 64 days, net -50. 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 1,243–1,308 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
11 Oct 2026, 10:171,250-4
5 Oct 2026, 04:011,254-11
3 Oct 2026, 01:091,265no change
26 Sept 2026, 05:351,265-7
17 Sept 2026, 01:381,272-2
13 Sept 2026, 00:391,274-2
8 Sept 2026, 21:171,276-3
3 Sept 2026, 05:541,279-2
31 Aug 2026, 00:051,281-3
27 Aug 2026, 18:171,284-4
24 Aug 2026, 19:491,288-3
21 Aug 2026, 12:141,291-3
18 Aug 2026, 04:421,294-1
15 Aug 2026, 12:581,295-2
11 Aug 2026, 17:511,297-3
8 Aug 2026, 06:301,300first 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“IT Jobs In Bengaluru” (@ITJobsinBengaluru), 1,250 members as measured 11 October 2026. Telegram Register, tgregister.com/channel/ITJobsinBengaluru.

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.