DUKE Robotics Corp.: diluted earnings per share

What this measure means

Reported earnings or loss per share under dilution rules. Antidilutive instruments may be excluded. A diluted value can equal the basic value without implying no potential dilution.

Exact concept: us-gaap:EarningsPerShareDiluted. 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 2021-01-01 to 2025-12-31. The SEC response was captured on 2026-09-21.

Reading these values

This selected numerical history matches Basic earnings per share for the same reporting intervals and original units. The accounting definitions remain distinct. Equal values do not establish that the concepts are interchangeable or explain why they match; filing dates and accessions may differ. Compare the definitions and source filings before combining them.

Selected filing history

Related financial histories

• DUKE Robotics Corp.: total assets
• DUKE Robotics Corp.: total liabilities
• DUKE Robotics Corp.: stockholders equity
• DUKE Robotics Corp.: cash and cash equivalents
• DUKE Robotics Corp.: net income or loss
• DUKE Robotics Corp.: operating cash flow
• DUKE Robotics Corp.: capital expenditure payments
• DUKE Robotics Corp.: revenue
• DUKE Robotics Corp.: financing cash flow
• DUKE Robotics Corp.: investing cash flow
• DUKE Robotics Corp.: retained earnings or deficit
• DUKE Robotics Corp.: basic weighted-average shares
• DUKE Robotics Corp.: diluted weighted-average shares
• DUKE Robotics Corp.: basic earnings per share
• DUKE Robotics Corp.: net property, plant and equipment
• DUKE Robotics Corp.: share-based compensation expense
• DUKE Robotics Corp.: operating income or loss
• DUKE Robotics Corp.: current assets
• DUKE Robotics Corp.: interest expense
• DUKE Robotics Corp.: current liabilities
• DUKE Robotics Corp.: current accounts payable
• DUKE Robotics Corp.: operating expenses
• DUKE Robotics Corp.: net inventory
• DUKE Robotics Corp.: gross profit
• DUKE Robotics Corp.: cost of revenue
• DUKE Robotics Corp.: research and development expense

Inspect the source

Entity

DUKE Robotics Corp. / CIK 0001638911

Captured

2026-09-21T17:22:43.528Z

SEC response SHA-256

da203cd94583c255c4a286ccbad7371238a76e0ec4dc978a02d2f9ac22796a58

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