Every figure this model derived for SBLK, 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.
Figure
Value
XBRL tag
As at
capex
83,988,000
PaymentsToAcquirePropertyPlantAndEquipment
2025-12-31
cash
498,165,000
CashAndCashEquivalentsAtCarryingValue
2026-06-30
current assets
807,879,000
AssetsCurrent
2026-06-30
current liabilities
421,978,000
LiabilitiesCurrent
2026-06-30
equity
2,514,480,000
StockholdersEquity
2026-06-30
interest expense
71,225,000
InterestExpense
2025-12-31
ocf
295,936,000
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
1,042,499,000
Revenues
2025-12-31
sbc
17,798,000
ShareBasedCompensation
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
SBLK on one particular measure came for.
Ratio
Value
cash operating margin
30.98
current ratio
2.04
current ratio reported
1.91
deferred revenue growth
82.59
dilution pct
6.18
ebit cagr
-34.41
ebit yoy
-64.26
fcf margin
20.33
growth cv
2.8
interest cover
1.92
operating margin
13.13
owner earnings margin
18.62
revenue growth
-17.62
revenue growth per share
-22.42
roic
5.33
rule of 40
-4.49
sbc pct revenue
1.71
What to be careful about
What this model itself distrusts about SBLK'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 2025-12-31 (242 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.
gross profit not tagged; rebuilt from Revenues - CostOfPropertyRepairsAndMaintenance
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