Every figure this model derived for BGI, 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-03-29.
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
7,007,000
PaymentsToAcquirePropertyPlantAndEquipment
2025-03-29
cash
1,509,000
CashAndCashEquivalentsAtCarryingValue
2025-03-29
current assets
126,466,000
AssetsCurrent
2025-03-29
current liabilities
149,586,000
LiabilitiesCurrent
2025-03-29
equity
-18,011,000
StockholdersEquity
2025-03-29
interest expense
8,458,000
InterestPaidNet
2025-03-29
ocf
-1,912,000
NetCashProvidedByUsedInOperatingActivities
2025-03-29
revenue
177,807,000
Revenues
2025-03-29
sbc
222,000
ShareBasedCompensation
2025-03-29
The ratios
The figures themselves rather than their scores — what somebody looking up
BGI on one particular measure came for.
Ratio
Value
cash operating margin
1.36
current ratio
0.85
current ratio reported
0.85
dilution pct
1.26
fcf margin
-5.02
growth cv
7.35
interest cover
-0.65
net debt ebitda
11.25
operating margin
-3.11
owner earnings margin
-5.14
revenue growth
-4.03
revenue growth per share
-5.22
roic
-65.13
rule of 40
-7.14
sbc pct revenue
0.12
What to be careful about
What this model itself distrusts about BGI's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
revenue period ends 2025-03-29 (519 days ago) - the tag chain found nothing recent, so treat this row as unscored
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-03-28 (155 days old, balance sheet); 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 rests on 3 of 4 inputs; not tagged: contracted coverage