Tactile Systems Technology, Inc.: 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 2014-01-01 to 2025-12-31. The SEC response was captured on 2026-09-20.

Selected filing history

Related financial histories

• Tactile Systems Technology, Inc.: total assets
• Tactile Systems Technology, Inc.: total liabilities
• Tactile Systems Technology, Inc.: stockholders equity
• Tactile Systems Technology, Inc.: cash and cash equivalents
• Tactile Systems Technology, Inc.: net income or loss
• Tactile Systems Technology, Inc.: operating cash flow
• Tactile Systems Technology, Inc.: capital expenditure payments
• Tactile Systems Technology, Inc.: contract revenue excluding tax
• Tactile Systems Technology, Inc.: financing cash flow
• Tactile Systems Technology, Inc.: investing cash flow
• Tactile Systems Technology, Inc.: retained earnings or deficit
• Tactile Systems Technology, Inc.: basic weighted-average shares
• Tactile Systems Technology, Inc.: diluted weighted-average shares
• Tactile Systems Technology, Inc.: basic earnings per share
• Tactile Systems Technology, Inc.: income tax expense or benefit
• Tactile Systems Technology, Inc.: net property, plant and equipment
• Tactile Systems Technology, Inc.: share-based compensation expense
• Tactile Systems Technology, Inc.: operating income or loss
• Tactile Systems Technology, Inc.: current assets
• Tactile Systems Technology, Inc.: current liabilities
• Tactile Systems Technology, Inc.: current accounts payable
• Tactile Systems Technology, Inc.: net finite-lived intangible assets
• Tactile Systems Technology, Inc.: net current accounts receivable
• Tactile Systems Technology, Inc.: common-stock repurchase payments
• Tactile Systems Technology, Inc.: operating expenses
• Tactile Systems Technology, Inc.: net inventory
• Tactile Systems Technology, Inc.: gross profit
• Tactile Systems Technology, Inc.: cost of revenue
• Tactile Systems Technology, Inc.: research and development expense

Inspect the source

Entity

Tactile Systems Technology, Inc. / CIK 0001027838

Captured

2026-09-20T05:14:23.334Z

SEC response SHA-256

15f9b668f20378192a78906ca3886e3429e7ee2aec2226f9aa858a7bbf568392

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