Every figure this model derived for TANH, 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
0
PaymentsToAcquirePropertyPlantAndEquipment
2025-12-31
cash
33,019,289
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
73,990,681
AssetsCurrent
2025-12-31
current liabilities
11,226,980
LiabilitiesCurrent
2025-12-31
equity
110,349,376
StockholdersEquity
2025-12-31
interest expense
279,564
InterestExpense
2025-12-31
ocf
-5,816,139
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
38,359,163
Revenues
2025-12-31
sbc
0
ShareBasedCompensation
2023-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
TANH on one particular measure came for.
Ratio
Value
cash operating margin
-31.77
current ratio
6.59
current ratio reported
6.59
dilution pct
445.03
fcf margin
-15.16
interest cover
-43.66
operating margin
-31.82
owner earnings margin
-15.16
revenue growth
-10.67
revenue growth per share
-83.61
roic
-12.47
rule of 40
-42.49
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about TANH'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 (last tagged 2023-12-31); treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-04-30 (122 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 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