Telegram RegisterThe public register of Telegram
Telegram profile photo for Trabajo IT Argentina

Supergroup

Trabajo IT Argentina

@ITArgentina

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

4,014members

-91 since we began measuring on 7 August 2026

94 online right now

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

Register entry

Telegram ID-1001243592533
TypeSupergroup
Username@ITArgentina
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 September 2026
Last confirmed live7 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/ITArgentina

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

Growth

4,0144,1104,0627 August 2026 — 4,105 members7 August 2026 — 4,100 members11 August 2026 — 4,098 members14 August 2026 — 4,097 members17 August 2026 — 4,093 members20 August 2026 — 4,102 members24 August 2026 — 4,103 members27 August 2026 — 4,110 members30 August 2026 — 4,101 members2 September 2026 — 4,083 members4 September 2026 — 4,083 members6 September 2026 — 4,095 members10 September 2026 — 4,089 members14 September 2026 — 4,083 members19 September 2026 — 4,076 members29 September 2026 — 4,069 members13 October 2026 — 4,051 members16 October 2026 — 4,053 members19 October 2026 — 4,042 members22 October 2026 — 4,044 members25 October 2026 — 4,043 members27 October 2026 — 4,036 members31 October 2026 — 4,030 members3 November 2026 — 4,020 members7 November 2026 — 4,014 members7 August 20267 November 2026
25 measurements spanning 92 days, net -91. 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,000–4,124 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 25
Measured (UTC)MembersChange
7 Nov 2026, 00:304,014-6
3 Nov 2026, 17:304,020-10
31 Oct 2026, 08:194,030-6
27 Oct 2026, 23:094,036-7
25 Oct 2026, 05:094,043-1
22 Oct 2026, 09:284,044+2
19 Oct 2026, 05:084,042-11
16 Oct 2026, 02:074,053+2
13 Oct 2026, 06:454,051-18
29 Sept 2026, 23:574,069-7
19 Sept 2026, 08:414,076-7
14 Sept 2026, 17:164,083-6
10 Sept 2026, 23:184,089-6
6 Sept 2026, 02:404,095+12
4 Sept 2026, 23:544,083no change
2 Sept 2026, 06:114,083-18
30 Aug 2026, 10:044,101-9
27 Aug 2026, 06:374,110+7
24 Aug 2026, 06:354,103+1
20 Aug 2026, 13:274,102first 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 7 November 2026 — this entry's latest reading, not the date you are reading this.

“Trabajo IT Argentina” (@ITArgentina), 4,014 members as measured 7 November 2026. Telegram Register, tgregister.com/channel/ITArgentina.

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.