Channel
@nttdata
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
33subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002051704244 |
|---|---|
| Type | Channel |
| Username | @nttdata |
| Created | Between 1 November 2023 and 26 January 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/nttdata |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 14:48 | 33 | +1 |
| 11 Aug 2026, 02:15 | 32 | no change |
| 7 Aug 2026, 02:04 | 32 | first reading |
20 posts held, back to 26 January 2024 — the 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 18 December 2024. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 30 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
Search results for "Nttdata" The monitoring task had failed 100 consecutive times. Your subscription to the RSS feed has been deactivated. To reactivate it, please use the /activate_subs command. ERROR: Network error (TimeoutError)
NTT DATA Business Solutions Announces a Global Center of Excellence for Generative AI Centered on IBM watsonx: NTT DATA Business Solutions taps IBM watsonx AI and data platform to create new customer solutions for application modernization, finance,… newsroom.ibm.com/2024-01-24-… via Search results for "Nttdata" (author: @MichaelNishiki)
This year NTT DATA was one of only 17 Global Top Employers to be recognized for their outstanding people policies and practices worldwide. #NTTDATALife bit.ly/3UgBGN7 via Search results for "Nttdata" (author: @AmandaPRecruit)
Gartner recognized NTT DATA as a Leader in the 2023 Gartner® Magic Quadrant™ for Managed Network Services report. We’re also a Leader in the in 2023 Gartner® Magic Quadrant™ for Network Services, Global. bit.ly/3ShWPE8 via Search results for "Nttdata" (author: @AmandaPRecruit)
bit.ly/3OighiK via Search results for "Nttdata" (author: @nttdata_mlw)
Analyze the keywords of 20 million or more on X with NTT data, generated AI and predict trends -Mynavi News japantrendmedia.tokyo/trend/… via Search results for "Nttdata" (author: @JTM1234567899)
bit.ly/3HAdbmv via Search results for "Nttdata" (author: @nttdata_mlw)
日本のIT企業はGAFAM+IBMに対抗する前にNTTdataを超えてみろちゅーの via Search results for "Nttdata" (author: @E_H_352)
bit.ly/3OkSejn via Search results for "Nttdata" (author: @nttdata_mlw)
¡Somos GLOBAL TOP EMPLOYER 2024! 👏 En NTT DATA, estamos muy orgullosos de haber sido por el Top Employers Institute. Y somos uno de los únicos 17 Top Employers Globales que han sido reconocidos por sus destacadas políticas y prácticas de personal en todo el mundo. via Search results for "Nttdata" (author: @woollenfiddle)
NTT Data apuesta por la región norte del Perú con centro de alto rendimiento en Trujillo. #centroaltorendimiento #capacitacion #innovacion #gobiernodigital #nttdataperu #trujillo #peru #empleos Lea la nota completa en ecosdigitales. com via Search results for "Nttdata" (author: @ecosdigitales_)
Showing the 12 most recent of 20 posts we hold for @nttdata. 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.
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.
@nttdata named 12 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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.
“NTT DATA” (@nttdata), 33 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/nttdata.
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.