Skip to content

NetApp, Inc.: revenue

Revenue for NetApp, Inc. Inspect selected reporting periods, original units and SEC filing links; download the financial history.

All NetApp, Inc. financial histories

What this measure means

Revenue under this specific accounting concept. A missing value is not zero; filers can use other revenue concepts.

Exact concept: us-gaap:Revenues. Each value covers an annual-duration reporting interval, shown with both start and end dates. Different units remain separate; no currency conversion or interpolation is applied.

Coverage of this history

Selected reporting periods run from 2008-04-26 to 2026-04-24. The SEC response was captured on 2026-09-20.

Selected filing history

Revenue in original reported units, latest-filed observation per period
Period startPeriod endValueUnitFiledSource filing
2025-04-262026-04-246,237,000,000USD2026-06-0510-K · 0001193125-26-259683
2024-04-272025-04-255,907,000,000USD2026-06-0510-K · 0001193125-26-259683
2023-04-292024-04-265,657,000,000USD2026-06-0510-K · 0001193125-26-259683
2011-04-302012-04-276,233,200,000USD2012-06-1910-K · 0001193125-12-275547
2010-05-012011-04-295,122,600,000USD2012-06-1910-K · 0001193125-12-275547
2009-04-252010-04-303,931,400,000USD2012-06-1910-K · 0001193125-12-275547
2008-04-262009-04-243,406,400,000USD2011-06-2310-K · 0001193125-11-171858

Related financial histories

Inspect the source

Entity
NetApp, Inc. / CIK 0001002047
Captured
2026-09-20T05:11:26.485Z
SEC response SHA-256
544e1e648485597c97423e20161c693df3b6ee55c6a2d38a1e8e2539bedfbfdb

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.

Read the published dataset with Python
import json
from urllib.request import urlopen

with urlopen("https://canlicapital.com/company-data/0001002047.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"])))