Every figure this model derived for FTS, the value it took, and
the element in the company's own XBRL it was read from — so any of it can be checked
against the filing rather than taken on trust.
As at 2025-12-31.
The figures, and where each came from
This is the part no other screener shows. Each figure below names the XBRL element it
was read from, so it can be checked against the filing itself.
Figure
Value
XBRL tag
As at
capex
5,942,000,000
PaymentsToAcquirePropertyPlantAndEquipment
2025-12-31
cash
367,000,000
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
3,805,000,000
AssetsCurrent
2025-12-31
current liabilities
7,513,000,000
LiabilitiesCurrent
2025-12-31
equity
23,810,000,000
StockholdersEquity
2025-12-31
interest expense
1,478,000,000
InterestExpenseNonoperating
2025-12-31
ocf
4,062,000,000
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
12,170,000,000
Revenues
2025-12-31
sbc
0
AllocatedShareBasedCompensationExpense
2017-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
FTS on one particular measure came for.
Ratio
Value
cash operating margin
45.6
current ratio
0.51
current ratio reported
0.51
dilution pct
1.72
fcf margin
-15.45
interest cover
2.36
net debt ebitda
6.1
operating margin
28.69
owner earnings margin
-15.45
revenue growth
5.75
revenue growth per share
3.97
roic
4.78
rule of 40
34.45
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about FTS's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
no current stock compensation tagged (last tagged 2017-06-30); treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
reports in CAD and no currency is recorded for its share price, so the two cannot be shown to match. The price refresh records one; until it has run for this company the multiples are left out rather than assumed comparable
share count is from 2025-12-31 (242 days old, dei cover page); a stock split since then would make the market cap wrong. Set `market_cap` in overrides.yaml to be sure.
no forward EPS estimate; growth rests on filings only. Analyst consensus is not published in XBRL, so it has to be fetched from a data provider or set by hand in overrides.yaml as `eps_growth_2y`
valuation DROPPED from the total: only 0 of 2 inputs could be computed (ev sales, ev owner earnings not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
durability DROPPED from the total: only 0 of 4 inputs could be computed (worst year, contracted coverage, gross margin stability, cash flow stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
growth DROPPED from the total: only 1 of 4 inputs could be computed (sustained growth, margin trend, margin recent not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
3 of 5 dimensions could not be measured (valuation, durability, growth -- 55% of the model), so this row is not comparable with the others; its total rests on what was left