BIZTRAC BETA
Development of building projects

FROGNER PROSJEKTUTVIKLING AS

Org. no. 898998622 Limited company (AS) Aurskog-Høland Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 85.4m
Operating profit NOK 15.2m
Equity NOK 13.5m
Incorporated 2012
Share capital NOK 100,000

FROGNER PROSJEKTUTVIKLING AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 898998622. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Selskapets virksomhet er investering i, utvikling, utbygging, forvaltning, kjøp og salg av fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 85.4m in revenue and NOK 15.2m in operating profit.

Key figures · 2024

Revenue
NOK 85.4m
Operating profit
NOK 15.2m
Equity
NOK 13.5m
Est. value
NOK 37.6m

Financial health · 2024

Liquidity
12.06
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.5%
Satisfactory
Equity as a share of total capital

Who owns FROGNER PROSJEKTUTVIKLING AS?

BAKKE LEILIGHETER AS
FROGNER PROSJEKTUTVIKLING AS
NOK 85.4m rev. · NOK 15.2m profit

FROGNER PROSJEKTUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FROGNER PROSJEKTUTVIKLING AS

Who owns FROGNER PROSJEKTUTVIKLING AS?

BAKKE LEILIGHETER AS is the largest registered owner, with 100.0%.

What is the revenue of FROGNER PROSJEKTUTVIKLING AS?

FROGNER PROSJEKTUTVIKLING AS had revenue of NOK 85.4m in 2024.

Where is FROGNER PROSJEKTUTVIKLING AS based?

FROGNER PROSJEKTUTVIKLING AS has its business address in Aurskog.

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.