Nippon Telegraph & Telephone Corp: cash and cash equivalents

At a glance

Nippon Telegraph & Telephone reported cash and cash equivalents of 925.2 billion JPY at 2017-03-31, down 15.0% from 1.09 trillion JPY a year earlier. From 2007 to 2017 it grew at a compound 1.5% a year, from 796.3 billion JPY to 925.2 billion JPY. Across the last five reported years it ranged from 849.2 billion JPY (2015-03-31) to 1.09 trillion JPY (2016-03-31).

Computed from the values in the table below, in JPY; each links to the filing it came from.

What this measure means

Cash and qualifying short-term liquid investments under the filer’s accounting policy. Restricted cash and longer-term investments may be reported separately.

Exact concept: us-gaap:CashAndCashEquivalentsAtCarryingValue. Each value is a balance at the reporting date, not a flow earned over a year. Different units remain separate; no currency conversion or interpolation is applied.

Coverage of this history

Selected reporting periods run from 2007-03-31 to 2017-03-31. The SEC response was captured on 2026-09-19.

This selected history ends more than two years before capture. Do not treat its final value as a current balance or current annual result. More recent filings may use another accounting tag; inspect the filings before drawing conclusions about the company.

Selected filing history

Related NIPPON TELEGRAPH & TELEPHONE CORP histories

• Total assets
• Current assets
• Net inventory
• Prepaid expenses and other current assets
• Net property, plant and equipment
• Gross property, plant and equipment
• Stockholders equity
• Revenue

All 41 Nippon Telegraph & Telephone histories

Inspect the source

Entity

NIPPON TELEGRAPH & TELEPHONE CORP / CIK 0000769594

Captured

2026-09-19 15:03 UTC

SEC response SHA-256

188ea57ae66f214794312487af3d77afa92bce90684490b5540f88e19d6a7954

Current SEC company facts · Download the original response snapshot (gzip) · Download the selected JSON

Latest-filed annual-report facts per unit and reporting period at capture time. Duration facts cover 300 to 400 days. This selection can include restatements and is not a point-in-time backtest dataset. Missing concepts are omitted, never zero-filled. Values retain original units and are not currency converted. Extended concepts require compatible unit shapes and at least three reporting ends with changing values within one unit. Constant or incompatible added histories are omitted.

Public company accounting reference, not market prices, returns, an investment recommendation, or ALPHAC performance. Validate a separately constructed return series with the validation API; accounting values are not returns.

Use this in research

A financial period ends before its results become public. Use the filing date as a minimum availability boundary, inspect amendments, and retain the original filing vintage when testing historical signals. This latest-filed selection can contain information unavailable at the time.

These pages do not supply prices, total-return histories, corporate-action adjustments or a tradable universe. Build those inputs separately before evaluating a strategy. A profitable backtest can still reflect selection bias or costs that were left out.

Research methodology · Execution and cost assumptions · Check backtest overfitting

Build with the open-source tools

Use these accounting records as inspectable inputs. When you have constructed a return series, the validation tools can help test its statistical evidence and preserve the result with its limitations.

• Get an API key and run your first validation
• Connect the MCP server to your coding assistant
• Inspect the ALPHAC engine on GitHub
• Read the MCP server source and integration examples

The MCP server is free and MIT-licensed: npx -y canli-mcp. If these records help your research, a star on GitHub helps other researchers find them.

import json
from urllib.request import urlopen

with urlopen("https://canlicapital.com/company-data/0000769594.json") as response:
    record = json.load(response)
print(record["fetched_at"])
print(record["policy"])
for concept in record["concepts"]:
    print(concept["tag"], next(iter(concept["observations"])))