Every figure this model derived for TIGR, 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
5,482,918
PaymentsToAcquireProductiveAssets
2025-12-31
cash
791,016,893
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
8,151,927,209
AssetsCurrent
2025-12-31
current liabilities
7,299,458,972
LiabilitiesCurrent
2025-12-31
equity
865,507,397
StockholdersEquity
2025-12-31
interest expense
73,355,788
InterestExpense
2025-12-31
ocf
1,316,684,703
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
612,064,917
Revenues
2025-12-31
sbc
15,609,141
AllocatedShareBasedCompensationExpense
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
TIGR on one particular measure came for.
Ratio
Value
cash operating margin
49.05
current ratio
1.12
current ratio reported
1.12
deferred revenue growth
230.97
dilution pct
10.81
ebit cagr
67.31
ebit yoy
102.3
fcf margin
214.23
growth cv
0.9
interest cover
3.84
operating margin
46.03
owner earnings margin
211.68
revenue growth
56.32
revenue growth per share
41.08
roic
177.36
rule of 40
102.35
sbc pct revenue
2.55
What to be careful about
What this model itself distrusts about TIGR's figures. Written by the
derivation as it ran, not added afterwards.
no operating income tagged; derived as revenue minus CostsAndExpenses
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, weighted average diluted); 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 DROPPED from the total: only 2 of 4 inputs could be computed (contracted coverage, gross margin stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
2 of 5 dimensions could not be measured (valuation, durability -- 35% of the model), so this row is not comparable with the others; its total rests on what was left