BIZTRAC BETA
Architectural activities

PANORAMA BOLIGUTVIKLING AS

Org. no. 931553321 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −16,000
Equity NOK 14,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

PANORAMA BOLIGUTVIKLING AS is registered as a limited company in Oslo, Oslo with organisation number 931553321. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, utvikling og salg av boliger.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 14,000
Est. value
NOK 22,000

Financial health · 2024

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

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

Who owns PANORAMA BOLIGUTVIKLING AS?

AEVI EIENDOM AS
PANORAMA BOLIGUTVIKLING AS
NOK 0 rev. · NOK −16,000 profit

PANORAMA BOLIGUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PANORAMA BOLIGUTVIKLING AS

Who owns PANORAMA BOLIGUTVIKLING AS?

AEVI EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of PANORAMA BOLIGUTVIKLING AS?

PANORAMA BOLIGUTVIKLING AS had revenue of NOK 0 in 2024.

Where is PANORAMA BOLIGUTVIKLING AS based?

PANORAMA BOLIGUTVIKLING 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.