Every figure this model derived for FVRR, 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
647,000
PaymentsToAcquirePropertyPlantAndEquipment
2025-12-31
cash
242,920,000
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
480,643,000
AssetsCurrent
2025-12-31
current liabilities
248,893,000
LiabilitiesCurrent
2025-12-31
equity
411,984,000
StockholdersEquity
2025-12-31
interest expense
2,140,000
InterestExpenseDebt
2025-12-31
ocf
104,589,000
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
430,909,000
Revenues
2025-12-31
sbc
51,389,000
ShareBasedCompensation
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
FVRR on one particular measure came for.
Ratio
Value
cash operating margin
15.06
current ratio
2.09
current ratio reported
1.93
deferred revenue growth
-7.58
dilution pct
-1.76
fcf margin
24.12
growth cv
0.99
interest cover
-0.55
operating margin
-0.27
owner earnings margin
12.2
revenue growth
10.07
revenue growth per share
12.04
roic
-0.55
rule of 40
9.8
sbc pct revenue
11.93
What to be careful about
What this model itself distrusts about FVRR'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.
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