Telegram RegisterThe public register of Telegram
Telegram profile photo for InformaticaCGT

Channel

InformaticaCGT

@InformaticaCGT

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

505subscribers

+0 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001011792121
TypeChannel
Username@InformaticaCGT
CreatedBetween 1 December 2015 and 31 March 2016— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/InformaticaCGT

Growth

504505504.55 August 2026 — 505 subscribers6 August 2026 — 505 subscribers6 August 2026 — 504 subscribers22 August 2026 — 505 subscribers5 August 202622 August 2026
4 measurements spanning 16 days. 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 504–505 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 01:48505+1
6 Aug 2026, 22:21504-1
6 Aug 2026, 18:34505no change
5 Aug 2026, 21:19505first reading

Engagement

19 posts held, back to 30 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
31.9%
avg views ÷ 505 subscribers
Avg views / post
161
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 19 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 July 2026
Posts held19 (30 April 202630 July 2026)
Views total161
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 18:34 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

30 Jul 2026, 08:27 UTC161 viewsread 6 August 2026

Bienvenida a las personas readmitidas a Global Rosetta 🤗 Este lunes se llevaron a cabo las reincorporaciones de las personas afectadas por el despido colectivo, tal y como indicaba la sentencia del juicio de la demanda interpuesta por CGT y ELA. Queremos daros la bienvenida a todas y todos y esperamos que la empresa se haga cargo de daros un proyecto acorde a vuestro perfil, proporcionando la correspondiente formac

16 Jul 2026, 22:12 UTC300 viewsread 6 August 2026

La presencia de CGT en la negociación del Plan de Igualdad sigue demostrando que su acción sindical sirve para conseguir mejoras reales y concretas para la plantilla. Gracias a las propuestas y a la defensa mantenida por CGT durante la negociación, a partir del 16 de julio, las personas trabajadoras que se acojan a la modalidad Flex Choice podrán decidir si desean disfrutar o no de los festivos de empresa, en las mi

15 Jul 2026, 11:43 UTC497 viewsread 6 August 2026

⚠️⚠️⚠️⚠️⚠️¡¡ATENCIÓN!!⚠️⚠️⚠️⚠️⚠️ El ERE en Global Rosetta es NULO La Audiencia Nacional nos da la razón y declara nulos todos los despidos realizados y tiene que readmitir a todas las personas trabajadoras que fueron despedidas https://globalrosettacgt.blogspot.com/2026/07/comunicado-cgt-el-despido-colectivo-es.html

22 Jun 2026, 08:42 UTC389 viewsread 6 August 2026
Forwarded from @cgtenbbvatechPhoto

A LA HUELGA — Lunes 22 de junio, 11:30 h Este lunes salimos a la calle. Huelga y concentración por una compensación justa, por un convenio justo y por una mesa de negociación. Nos concentramos en: - Bilbao — Gran Vía 12 - Madrid — Paseo de Recoletos 10 - Barcelona — Antoni Maura 6 Acude, trae a tus compañeras y compañeros y haz correr la voz. Cuantas más seamos, más fuerza haremos. https://x.com/CGTenBBVATech/sta

10 Jun 2026, 13:27 UTC391 viewsread 6 August 2026
Photo

📵 CHARLA / TALLER “Desconexión digital: un derecho a conquistar” Vivimos conectadas permanentemente. El trabajo invade nuestro tiempo, el móvil elimina fronteras y la disponibilidad constante se convierte en una obligación no escrita. Desde CGT Metal Madrid abrimos un espacio para reflexionar y debatir sobre el derecho a la desconexión digital, sus implicaciones en la salud laboral y cómo organizarnos para defender

8 Jun 2026, 16:54 UTC304 viewsread 6 August 2026
Photo

BBVA Tech 📢 CCOO aplaza, CGT moviliza ✊ CCOO ha movido la huelga estatal del 8 al 22 de junio. ¿El motivo? La visita del Papa. Mientras unos buscan la fecha perfecta para la foto, la pérdida de poder adquisitivo no espera. Nosotras tampoco. Concentración: "Sus millones, nuestras lamentaciones. Techies en lucha." 📅 Jueves 18 de junio 🕑 14:00 h — descanso de la comida, fuera de horario laboral 📍 Gran Vía 12, Bilbao

5 Jun 2026, 11:04 UTC410 viewsread 6 August 2026

Compañeras, compañeros: Hemos leído la nota de la RLPT explicando por qué se ha movido la huelga del 8J. Se agradece el tono conciliador, pero hablemos claro: la transparencia llega tarde y, sobre todo, llega después de haber decidido por toda la plantilla. En esa nota se confiesan tres cosas, y las tres retratan a quien las firma. https://cgtinformatica.org/es/contenido/comunicado-cgt-bbva-technology-la-dignidad-no-

4 Jun 2026, 09:15 UTC427 viewsread 6 August 2026
Photo

CCoo BBVA Technology ya NO va a la huelga porque #ElPapaEnMadrid https://t.me/cgtenbbvatech

3 Jun 2026, 15:01 UTC295 viewsread 6 August 2026
Photo

El próximo 14 de junio manifestación en Madrid contra el rearme, la guerra y el militarismo. A las 12 horas en Atocha para ir al Ministerio de Asuntos Exteriores.

25 May 2026, 14:56 UTC421 viewsread 6 August 2026

Firmado ERE en Capgemini. Tal y como hemos dicho desde el principio, este proceso estaba decidido de antemano y pensamos que además de lo grave que siempre resulta el despido forzoso de tantos compañeros, ha sido también muy preocupante cómo se ha gestionado y quién lo ha avalado. https://capgeminitas.blogspot.com/2026/05/ere-capgemini-nuestra-vision-del-proceso.html

21 May 2026, 09:11 UTC425 viewsread 6 August 2026

Más de 700 personas despedidas en Capgemini y todo sigue como si nada. No hay asambleas, no hay oposición visible, no hay movilizaciones previstas. Se intenta imponer la normalidad, quieren que lo asumamos como algo lógico, inevitable y quieren que pensemos que no nos va a tocar. https://capgeminitas.blogspot.com/2026/05/mas-de-700-despidos-y-aqui-no-pasa-nada.html

20 May 2026, 16:51 UTC657 viewsread 6 August 2026

Como recordaréis, una demanda de la CGT en Zara abrió el camino del reconocimiento para que cuando un festivo coincidiera en un descanso semanal en trabajo a turnos, pudiera disfrutarse otro día. Necesitábamos un precedente para el caso más habitual, es decir, cuando un festivo coincidiera en sábado para trabajadores/as con jornada laboral de lunes a viernes (o lunes a sábado con descanso esa semana en sábado). Pue

Showing the 12 most recent of 19 posts we hold for @InformaticaCGT. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 1,588,180 of 1,602,822entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

Names

Channels on the register whose handles appear in this channel's posts.

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.

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

“InformaticaCGT” (@InformaticaCGT), 505 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/InformaticaCGT.

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.