Every figure this model derived for GDS.PA, 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-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
cash
366,500,000
CashAndCashEquivalents
2025-07-01
current assets
1,466,600,000
CurrentAssets
2024-07-01
current liabilities
1,686,000,000
CurrentLiabilities
2024-07-01
equity
1,145,200,000
EquityAttributableToOwnersOfParent
2025-07-01
ocf
693,700,000
CashFlowsFromUsedInOperatingActivities
2025-06-30
revenue
5,242,000,000
Revenue
2025-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
GDS.PA on one particular measure came for.
Ratio
Value
cash operating margin
3.3
current ratio
0.87
current ratio reported
0.87
ev ebit
15.53
ev owner earnings
3.88
ev sales
0.51
fcf margin
13.23
net debt ebitda
8.51
operating margin
3.3
owner earnings margin
13.23
revenue growth
4.7
revenue growth per share
4.7
roic
5.22
rule of 40
8.01
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about GDS.PA'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; treated as zero, so owner earnings are overstated
no current capital expenditure tagged; treated as zero, so free cash flow is overstated and equals operating cash flow
share count is from 2025-06-30 (426 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 usable diluted share count, so growth is measured on total revenue rather than per share; a company issuing shares to fund that growth reads better than it is
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`
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
resilience rests on 2 of 3 inputs; not tagged: interest cover
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
2 of 5 dimensions could not be measured (durability, growth -- 30% of the model), so this row is not comparable with the others; its total rests on what was left
no interest expense tagged while 1,841M of debt is on the balance sheet, so interest cover is unmeasured rather than perfect