BIZTRAC BETA
Business and other management consultancy activities

FRYDEN AS

Org. no. 997454421 Limited company (AS) Lørenskog Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK 3.7m
Equity NOK 92,000
Incorporated 2011
Share capital NOK 100,000

FRYDEN AS is registered as a limited company in Lørenskog, Akershus with organisation number 997454421. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Bedriftsrådgivning, forretningsmessig tjenesteyting, investeringsvirksomhet samt alt som hører naturlig til dette samt andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også kjøpe og selge eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK 3.7m in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
Operating profit
NOK 3.7m
Equity
NOK 92,000
Est. value
NOK 11.5m

Financial health · 2025

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FRYDEN AS?

ODDGEIR HANSEN
FRYDEN AS
NOK 3.7m rev. · NOK 3.7m profit

FRYDEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRYDEN AS

Who owns FRYDEN AS?

ODDGEIR HANSEN is the largest registered owner, with 100.0%.

What is the revenue of FRYDEN AS?

FRYDEN AS had revenue of NOK 3.7m in 2025.

Where is FRYDEN AS based?

FRYDEN AS has its business address in Fjellhamar.

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.