BIZTRAC BETA
Fund management activities

FRØNNINGEN AS

Org. no. 993171786 Limited company (AS) Oslo Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −438,000
Equity NOK 39.9m
Incorporated 2008
Share capital NOK 1.6m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−438k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FRØNNINGEN AS is registered as a limited company in Oslo, Oslo with organisation number 993171786. The business is classified under fund management activities (NACE 66.300). The company was incorporated in 2008. Registered share capital is NOK 1.6m, divided into 16000 shares. The company's stated purpose is: “Erverv og forvaltning av aksjer og verdipapirer, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −438,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −438,000
Equity
NOK 39.9m
Est. value
NOK 40.5m

Financial health · 2025

Liquidity
1.57
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
87.8%
Very good
Equity as a share of total capital

Who owns FRØNNINGEN AS?

TORBJØRN HOLE FRØNNINGEN
FRØNNINGEN AS
NOK 0 rev. · NOK −438,000 profit

FRØNNINGEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FRØNNINGEN AS own?

FRØNNINGEN AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about FRØNNINGEN AS

Who owns FRØNNINGEN AS?

TORBJØRN HOLE FRØNNINGEN is the largest registered owner, with 100.0%.

What is the revenue of FRØNNINGEN AS?

FRØNNINGEN AS had revenue of NOK 0 in 2025.

Where is FRØNNINGEN AS based?

FRØNNINGEN AS has its business address in Oslo.

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.