ESPEY MFG. & ELECTRONICS CORP.: retained earnings or deficit

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 2025-06-30. The SEC response was captured on 2026-09-19.

Selected filing history

Related financial histories

• ESPEY MFG. & ELECTRONICS CORP.: total assets
• ESPEY MFG. & ELECTRONICS CORP.: total liabilities
• ESPEY MFG. & ELECTRONICS CORP.: stockholders equity
• ESPEY MFG. & ELECTRONICS CORP.: cash and cash equivalents
• ESPEY MFG. & ELECTRONICS CORP.: net income or loss
• ESPEY MFG. & ELECTRONICS CORP.: operating cash flow
• ESPEY MFG. & ELECTRONICS CORP.: capital expenditure payments
• ESPEY MFG. & ELECTRONICS CORP.: revenue
• ESPEY MFG. & ELECTRONICS CORP.: financing cash flow
• ESPEY MFG. & ELECTRONICS CORP.: investing cash flow
• ESPEY MFG. & ELECTRONICS CORP.: basic weighted-average shares
• ESPEY MFG. & ELECTRONICS CORP.: diluted weighted-average shares
• ESPEY MFG. & ELECTRONICS CORP.: basic earnings per share
• ESPEY MFG. & ELECTRONICS CORP.: diluted earnings per share
• ESPEY MFG. & ELECTRONICS CORP.: income tax expense or benefit
• ESPEY MFG. & ELECTRONICS CORP.: net property, plant and equipment
• ESPEY MFG. & ELECTRONICS CORP.: share-based compensation expense
• ESPEY MFG. & ELECTRONICS CORP.: operating income or loss
• ESPEY MFG. & ELECTRONICS CORP.: current assets
• ESPEY MFG. & ELECTRONICS CORP.: current liabilities
• ESPEY MFG. & ELECTRONICS CORP.: current accounts payable
• ESPEY MFG. & ELECTRONICS CORP.: net current accounts receivable
• ESPEY MFG. & ELECTRONICS CORP.: common-stock repurchase payments
• ESPEY MFG. & ELECTRONICS CORP.: net inventory
• ESPEY MFG. & ELECTRONICS CORP.: gross profit
• ESPEY MFG. & ELECTRONICS CORP.: cost of revenue
• ESPEY MFG. & ELECTRONICS CORP.: selling, general and administrative expense

Inspect the source

Entity

ESPEY MFG. & ELECTRONICS CORP. / CIK 0000033533

Captured

2026-09-19T14:46:35.647Z

SEC response SHA-256

7f297aa88c005152d146bb0d18f2eb44888627bfbed06aad449dd71567077867

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

import json
from urllib.request import urlopen

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