TELEPHONE AND DATA SYSTEMS, INC.: interest expense

What this measure means

Borrowing costs recognized as interest expense. This is distinct from cash interest paid and may not include every capitalized borrowing cost.

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

Selected filing history

Related financial histories

• TELEPHONE AND DATA SYSTEMS, INC.: total assets
• TELEPHONE AND DATA SYSTEMS, INC.: stockholders equity
• TELEPHONE AND DATA SYSTEMS, INC.: cash and cash equivalents
• TELEPHONE AND DATA SYSTEMS, INC.: net income or loss
• TELEPHONE AND DATA SYSTEMS, INC.: operating cash flow
• TELEPHONE AND DATA SYSTEMS, INC.: capital expenditure payments
• TELEPHONE AND DATA SYSTEMS, INC.: revenue
• TELEPHONE AND DATA SYSTEMS, INC.: contract revenue excluding tax
• TELEPHONE AND DATA SYSTEMS, INC.: financing cash flow
• TELEPHONE AND DATA SYSTEMS, INC.: investing cash flow
• TELEPHONE AND DATA SYSTEMS, INC.: retained earnings or deficit
• TELEPHONE AND DATA SYSTEMS, INC.: basic weighted-average shares
• TELEPHONE AND DATA SYSTEMS, INC.: diluted weighted-average shares
• TELEPHONE AND DATA SYSTEMS, INC.: basic earnings per share
• TELEPHONE AND DATA SYSTEMS, INC.: diluted earnings per share
• TELEPHONE AND DATA SYSTEMS, INC.: income tax expense or benefit
• TELEPHONE AND DATA SYSTEMS, INC.: net property, plant and equipment
• TELEPHONE AND DATA SYSTEMS, INC.: share-based compensation expense
• TELEPHONE AND DATA SYSTEMS, INC.: operating income or loss
• TELEPHONE AND DATA SYSTEMS, INC.: current assets
• TELEPHONE AND DATA SYSTEMS, INC.: current liabilities
• TELEPHONE AND DATA SYSTEMS, INC.: goodwill carrying amount
• TELEPHONE AND DATA SYSTEMS, INC.: net finite-lived intangible assets
• TELEPHONE AND DATA SYSTEMS, INC.: net current accounts receivable
• TELEPHONE AND DATA SYSTEMS, INC.: common-stock repurchase payments
• TELEPHONE AND DATA SYSTEMS, INC.: operating expenses
• TELEPHONE AND DATA SYSTEMS, INC.: net inventory
• TELEPHONE AND DATA SYSTEMS, INC.: selling, general and administrative expense

Inspect the source

Entity

TELEPHONE AND DATA SYSTEMS, INC. / CIK 0001051512

Captured

2026-09-20T05:17:25.720Z

SEC response SHA-256

060a655c6c300e9b1d2aed0b9cb5891389f987b73e88dab92611ff57c4b3e8c9

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