Cyberfort Software, Inc.: 10-K filed 2016-09-07

This filing

Form

10-K (annual report)

Filed

2016-09-07

Fiscal period

fiscal FY 2016

Accession

0001477932-16-012386 on SEC EDGAR

Values are as tagged in this filing. A later filing can restate them; each measure links to its history page, which shows the latest-filed value per period. All Cyberfort Software, Inc. filings.

Reported measures

Inspect the source

Entity

Cyberfort Software, Inc. / CIK 0001522787

Captured

2026-09-23 02:58 UTC

SEC response SHA-256

1612c431974ab6765117bb6bb7e7feb1cf9ff73622809316fe1ec71b673a3b8e

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

Every published concept a filing tagged, with the periods it covered, as reported in that filing at capture time. Forms 10-K, 10-K/A, 10-Q, 10-Q/A, 20-F, 20-F/A, 40-F, 40-F/A. A filing page needs at least 8 published concepts. Later filings can restate these values; the company history pages show the latest-filed value per period.

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