Every figure this model derived for BIDU, 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.
The figures themselves rather than their scores — what somebody looking up
BIDU on one particular measure came for.
Ratio
Value
cash operating margin
4.25
current ratio
1.76
current ratio reported
1.76
fcf margin
-11.69
growth cv
3.36
interest cover
-2.09
operating margin
-4.51
owner earnings margin
-14.49
revenue growth
1.21
revenue growth per share
1.21
roic
-2.37
rpo growth
-57.37
rule of 40
-3.31
sbc pct revenue
2.8
What to be careful about
What this model itself distrusts about BIDU's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
no market cap; set `market_cap` in overrides.yaml
share count is from 2010-12-31 (5721 days old, weighted average diluted); 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
gross profit not tagged; rebuilt from RevenueFromContractWithCustomerExcludingAssessedTax - 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