Every figure this model derived for FOR, 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-06-30.
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
1,000,000
PaymentsToAcquirePropertyPlantAndEquipment
2026-06-30
cash
394,900,000
CashAndCashEquivalentsAtCarryingValue
2026-06-30
equity
1,856,600,000
StockholdersEquity
2026-06-30
ocf
-197,700,000
NetCashProvidedByUsedInOperatingActivities
2025-09-30
revenue
1,724,800,000
Revenues
2026-06-30
sbc
8,400,000
ShareBasedCompensation
2026-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
FOR on one particular measure came for.
Ratio
Value
cash operating margin
13.06
deferred revenue growth
95.65
dilution pct
0.52
fcf margin
-11.52
growth cv
1.2
net debt ebitda
1.84
operating margin
12.38
owner earnings margin
-12.01
revenue growth
11.76
revenue growth per share
11.18
roic
7.48
rule of 40
24.14
sbc pct revenue
0.49
What to be careful about
What this model itself distrusts about FOR's figures. Written by the
derivation as it ran, not added afterwards.
operating income last tagged 2018-09-30, 2830 days before the revenue period (2026-06-30); dropped rather than divided by current revenue
presents no operating result; summed as revenue minus the costs it does tag (CostOfGoodsAndServicesSold, SellingGeneralAndAdministrativeExpense). Checked against the company's own figures: the answer lands 0.7% of revenue from the 226M pre-tax profit it reports, which is its interest and other non-operating items
no market cap; set `market_cap` in overrides.yaml
gross profit not tagged since 2018-09-30; rebuilt from Revenues - CostOfGoodsAndServicesSold
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
resilience rests on 2 of 3 inputs; not tagged: liquidity
growth DROPPED from the total: only 2 of 4 inputs could be computed (margin trend, margin recent not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
2 of 5 dimensions could not be measured (valuation, growth -- 45% of the model), so this row is not comparable with the others; its total rests on what was left
no interest expense tagged while 794M of debt is on the balance sheet, so interest cover is unmeasured rather than perfect