BIZTRAC BETA
Rental and operating of own or leased real estate

FROSTAVEIEN UTVIKLING AS

Org. no. 925477265 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 291.5m
Operating profit NOK 40.5m
Equity NOK 176.7m
Incorporated 2020
Share capital NOK 70,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FROSTAVEIEN UTVIKLING AS is registered as a limited company in Oslo, Oslo with organisation number 925477265. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 70,000, divided into 1000 shares. The company's stated purpose is: “Investere i 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 291.5m in revenue and NOK 40.5m in operating profit.

Key figures · 2024

Revenue
NOK 291.5m
Operating profit
NOK 40.5m
Equity
NOK 176.7m
Est. value
NOK 192.4m

Financial health · 2024

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

Who owns FROSTAVEIEN UTVIKLING AS?

FREDENSBORG BOLIG AS
FROSTAVEIEN UTVIKLING AS
NOK 291.5m rev. · NOK 40.5m profit

FROSTAVEIEN UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FROSTAVEIEN UTVIKLING AS

Who owns FROSTAVEIEN UTVIKLING AS?

FREDENSBORG BOLIG AS is the largest registered owner, with 100.0%.

What is the revenue of FROSTAVEIEN UTVIKLING AS?

FROSTAVEIEN UTVIKLING AS had revenue of NOK 291.5m in 2024.

Where is FROSTAVEIEN UTVIKLING AS based?

FROSTAVEIEN UTVIKLING 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.