BIZTRAC BETA
Buying and selling of own real estate

BO UTVIKLING AS

Org. no. 930064564 Limited company (AS) Alta Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −243,000
Equity NOK 130,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

BO UTVIKLING AS is registered as a limited company in Alta, Finnmark with organisation number 930064564. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom. Selskapet kan også investere i aksjer, verdipapirer, og andeler, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −243,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −243,000
Equity
NOK 130,000
Est. value
NOK 119,000

Financial health · 2025

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

Who owns BO UTVIKLING AS?

BO EIENDOMSSELSKAP AS
BO UTVIKLING AS
NOK 0 rev. · NOK −243,000 profit

BO UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BO UTVIKLING AS

Who owns BO UTVIKLING AS?

BO EIENDOMSSELSKAP AS is the largest registered owner, with 100.0%.

What is the revenue of BO UTVIKLING AS?

BO UTVIKLING AS had revenue of NOK 0 in 2025.

Where is BO UTVIKLING AS based?

BO UTVIKLING AS has its business address in Alta.

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.