Every figure this model derived for GLW, 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 2026-03-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
0
PaymentsToAcquireProductiveAssets
2020-09-30
cash
1,755,000,000
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
9,526,000,000
AssetsCurrent
2026-03-31
current liabilities
5,916,000,000
LiabilitiesCurrent
2026-03-31
equity
11,812,000,000
StockholdersEquity
2026-03-31
interest expense
346,000,000
InterestExpenseNonoperating
2026-03-31
ocf
2,906,000,000
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
16,321,000,000
Revenues
2026-03-31
sbc
347,000,000
ShareBasedCompensation
2026-03-31
The ratios
The figures themselves rather than their scores — what somebody looking up
GLW on one particular measure came for.
Ratio
Value
cash operating margin
25.12
current ratio
1.66
current ratio reported
1.61
deferred revenue growth
7.65
dilution pct
0.23
ebit cagr
18.17
ebit yoy
86.5
fcf margin
17.81
growth cv
1.73
interest cover
7.15
net debt ebitda
1.8
operating margin
15.15
owner earnings margin
15.68
revenue growth
20.05
revenue growth per share
19.78
roic
10.52
rule of 40
35.2
sbc pct revenue
2.13
What to be careful about
What this model itself distrusts about GLW's figures. Written by the
derivation as it ran, not added afterwards.
no current capital expenditure tagged (last tagged 2020-09-30); treated as zero, so free cash flow is overstated and equals operating cash flow
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-04-24 (128 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