BIZTRAC BETA
Activities of adventure companies

SERIOUS FUN AS

Org. no. 988340588 Limited company (AS) Hol Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK −38,000
Equity NOK 176,000
Incorporated 2005
Share capital NOK 400,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−38k kr).

SERIOUS FUN AS is registered as a limited company in Hol, Buskerud with organisation number 988340588. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2005. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Etablere og videreutvikle samt selge aktiviteter med base på Geilo. Serious Fun AS skal også leie ut utstyr og personell. Virksomhetsområde og formål er alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK −38,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK −38,000
Equity
NOK 176,000
Est. value
NOK 4.4m

Financial health · 2024

Liquidity
0.53
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.5%
Good
Equity as a share of total capital

Who owns SERIOUS FUN AS?

WILLIAM FRANCIS ROSE
SERIOUS FUN AS
NOK 4.3m rev. · NOK −38,000 profit

SERIOUS FUN AS has 13 registered shareholders:

All shareholders and roles →

Which companies does SERIOUS FUN AS own?

SERIOUS FUN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SERIOUS FUN AS

Who owns SERIOUS FUN AS?

WILLIAM FRANCIS ROSE is the largest registered owner, with 51.2%.

What is the revenue of SERIOUS FUN AS?

SERIOUS FUN AS had revenue of NOK 4.3m in 2024.

Where is SERIOUS FUN AS based?

SERIOUS FUN AS has its business address in Geilo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.