Napco Security Technologies, Inc: retained earnings or deficit

At a glance

Napco Security Technologies reported retained earnings or deficit of $221.4 million at 2026-06-30, up 11.2% from $199.1 million a year earlier. From 2011 to 2026 it grew at a compound 15.1% a year, from $26.8 million to $221.4 million. Across the last five reported years it ranged from $112.9 million (2022-06-30) to $221.4 million (2026-06-30). That was 92.8% of total assets ($238.7 million) at the same date.

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

What this measure means

Accumulated undistributed earnings or deficit at the reporting date. This balance is not cash available for distribution.

Exact concept: us-gaap:RetainedEarningsAccumulatedDeficit. 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 2011-06-30 to 2026-06-30. The SEC response was captured on 2026-09-19.

Selected filing history

Related NAPCO SECURITY TECHNOLOGIES, INC histories

• Stockholders equity
• Total assets
• Total liabilities
• Revenue
• Operating cash flow
• Diluted earnings per share
• Current assets
• Basic earnings per share

All 58 Napco Security Technologies histories

Inspect the source

Entity

NAPCO SECURITY TECHNOLOGIES, INC / CIK 0000069633

Captured

2026-09-19 14:50 UTC

SEC response SHA-256

9a89c6d9353dd55963a97c5c5a6dab4c9dd12afc1691e2ec134b84fd252af4e7

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/0000069633.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"])))