Every figure this model derived for YBGJ, 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
0
PaymentsToAcquirePropertyPlantAndEquipment
2022-12-31
cash
11,989
CashAndCashEquivalentsAtCarryingValue
2026-06-30
current assets
583,098
AssetsCurrent
2026-06-30
current liabilities
3,327,598
LiabilitiesCurrent
2026-06-30
equity
-2,622,591
StockholdersEquity
2026-06-30
interest expense
0
InterestPaidNet
2026-06-30
ocf
-727,992
NetCashProvidedByUsedInOperatingActivities
2026-06-30
revenue
12,353
Revenues
2026-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
YBGJ on one particular measure came for.
Ratio
Value
current ratio
0.18
current ratio reported
0.18
dilution pct
16.56
growth cv
1.8
revenue growth
-68727.78
revenue growth per share
-58979.14
rule of 40
-77824.64
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about YBGJ's figures. Written by the
derivation as it ran, not added afterwards.
WITHHELD: operating margin, cash operating margin, owner earnings margin, fcf margin, net margin, ocf margin, ebitda margin -- operating margin came out at -9,097% against a scale that tops out near 2,500%, which is arithmetic on a revenue figure of 12,353 rather than a margin. The figure is absent rather than corrected: there is no right value to put here.
no current stock compensation tagged; treated as zero, so owner earnings are overstated
no current capital expenditure tagged (last tagged 2022-12-31); 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-03-25 (158 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 debt and no profit, so interest cover cannot be measured; scored on cash runway instead: 0M of net cash against a 1M annual burn is 0.0 years
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`
quality DROPPED from the total: only 1 of 5 inputs could be computed (operating margin, roic, owner earnings, cash operating margin not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
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
2 of 5 dimensions could not be measured (quality, valuation -- 55% of the model), so this row is not comparable with the others; its total rests on what was left