Telegram RegisterThe public register of Telegram
Telegram profile photo for REGex Software | DATASCIENCE | ML-DL & Gen-AI | BigData | Competitive Programming | MERN | AWS | JAVA | PLACEMENT OPPORTUNITY

Supergroup

REGex Software | DATASCIENCE | ML-DL & Gen-AI | BigData | Competitive Programming | MERN | AWS | JAVA | PLACEMENT OPPORTUNITY

@REGexSoftware

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

4,256members

-152 since we began measuring on 6 August 2026

29 online right now

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

Register entry

Telegram ID-1001169206547
TypeSupergroup
Username@REGexSoftware
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 September 2026
Last confirmed live12 October 2026
Measurements held17
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/REGexSoftware

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 13 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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

4,2564,4084,3326 August 2026 — 4,408 members10 August 2026 — 4,397 members13 August 2026 — 4,378 members16 August 2026 — 4,372 members19 August 2026 — 4,366 members22 August 2026 — 4,358 members25 August 2026 — 4,355 members28 August 2026 — 4,349 members31 August 2026 — 4,345 members3 September 2026 — 4,341 members3 September 2026 — 4,341 members8 September 2026 — 4,322 members12 September 2026 — 4,315 members16 September 2026 — 4,311 members29 September 2026 — 4,296 members6 October 2026 — 4,276 members12 October 2026 — 4,256 members6 August 202612 October 2026
17 measurements spanning 67 days, net -152. 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 4,233–4,431 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
12 Oct 2026, 20:184,256-20
6 Oct 2026, 17:414,276-20
29 Sept 2026, 10:374,296-15
16 Sept 2026, 00:004,311-4
12 Sept 2026, 09:014,315-7
8 Sept 2026, 09:184,322-19
3 Sept 2026, 23:224,341no change
3 Sept 2026, 08:474,341-4
31 Aug 2026, 04:074,345-4
28 Aug 2026, 00:584,349-6
25 Aug 2026, 11:334,355-3
22 Aug 2026, 22:074,358-8
19 Aug 2026, 19:344,366-6
16 Aug 2026, 21:334,372-6
13 Aug 2026, 04:574,378-19
10 Aug 2026, 12:154,397-11
6 Aug 2026, 22:554,408first 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.

“REGex Software | DATASCIENCE | ML-DL & Gen-AI | BigData | Competitive Programming | MERN | AWS | JAVA | PLACEMENT OPPORTUNITY” (@REGexSoftware), 4,256 members as measured 12 October 2026. Telegram Register, tgregister.com/channel/REGexSoftware.

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.