BIZTRAC BETA
Development of building projects

ØSTMARKA PANORAMA AS

Org. no. 925677647 Limited company (AS) Aurskog-Høland Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −1.2m
Equity NOK −88.2m
Incorporated 2020
Share capital NOK 55,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−88,2 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,2 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ØSTMARKA PANORAMA AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 925677647. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 55,000, divided into 55000 shares. The company's stated purpose is: “Tilrettelegging, finansieringsbistand, prosjektledelse, rådgivning, forretningsførsel, forvaltning, utvikling, kjøp, utleie og salg av eiendom, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −1.2m
Equity
NOK −88.2m

Financial health · 2024

Liquidity
157.01
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-211.2%
Weak
Equity as a share of total capital

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

Who owns ØSTMARKA PANORAMA AS?

ØSTMARKA PANORAMA HOLDING AS
ØSTMARKA PANORAMA AS
· NOK −1.2m profit

ØSTMARKA PANORAMA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØSTMARKA PANORAMA AS

Who owns ØSTMARKA PANORAMA AS?

ØSTMARKA PANORAMA HOLDING AS is the largest registered owner, with 100.0%.

Where is ØSTMARKA PANORAMA AS based?

ØSTMARKA PANORAMA 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.