HIGH WIRE NETWORKS, INC.: research and development expense

What this measure means

Research and development costs recognized as expense. Capitalization policies and acquired projects can make this differ from total cash invested in development.

Exact concept: us-gaap:ResearchAndDevelopmentExpense. 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 2010-06-01 to 2016-05-31. The SEC response was captured on 2026-09-20.

This selected history ends more than two years before capture. Do not treat its final value as a current balance or current annual result. More recent filings may use another accounting tag; inspect the filings before drawing conclusions about the company.

Selected filing history

Related financial histories

• HIGH WIRE NETWORKS, INC.: total assets
• HIGH WIRE NETWORKS, INC.: total liabilities
• HIGH WIRE NETWORKS, INC.: stockholders equity
• HIGH WIRE NETWORKS, INC.: cash and cash equivalents
• HIGH WIRE NETWORKS, INC.: net income or loss
• HIGH WIRE NETWORKS, INC.: operating cash flow
• HIGH WIRE NETWORKS, INC.: capital expenditure payments
• HIGH WIRE NETWORKS, INC.: revenue
• HIGH WIRE NETWORKS, INC.: financing cash flow
• HIGH WIRE NETWORKS, INC.: investing cash flow
• HIGH WIRE NETWORKS, INC.: retained earnings or deficit
• HIGH WIRE NETWORKS, INC.: basic weighted-average shares
• HIGH WIRE NETWORKS, INC.: diluted weighted-average shares
• HIGH WIRE NETWORKS, INC.: basic earnings per share
• HIGH WIRE NETWORKS, INC.: diluted earnings per share
• HIGH WIRE NETWORKS, INC.: income tax expense or benefit
• HIGH WIRE NETWORKS, INC.: net property, plant and equipment
• HIGH WIRE NETWORKS, INC.: share-based compensation expense
• HIGH WIRE NETWORKS, INC.: operating income or loss
• HIGH WIRE NETWORKS, INC.: current assets
• HIGH WIRE NETWORKS, INC.: interest expense
• HIGH WIRE NETWORKS, INC.: current liabilities
• HIGH WIRE NETWORKS, INC.: goodwill carrying amount
• HIGH WIRE NETWORKS, INC.: net finite-lived intangible assets
• HIGH WIRE NETWORKS, INC.: net current accounts receivable
• HIGH WIRE NETWORKS, INC.: operating expenses
• HIGH WIRE NETWORKS, INC.: net inventory
• HIGH WIRE NETWORKS, INC.: gross profit
• HIGH WIRE NETWORKS, INC.: cost of revenue

Inspect the source

Entity

HIGH WIRE NETWORKS, INC. / CIK 0001413891

Captured

2026-09-20T08:02:14.471Z

SEC response SHA-256

71d51cfc7c0107ea0e83fca1225c3e53b0dc6e13d118420d045f36663d49e91e

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