BIZTRAC BETA
Rental and operating of own or leased real estate

PRESTERØDÅSEN PANORAMA AS

Org. no. 920611796 Limited company (AS) Tønsberg Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 216,000
Operating profit NOK 124,000
Equity NOK 475,000
Incorporated 2018
Share capital NOK 1.0m

Signals

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

PRESTERØDÅSEN PANORAMA AS is registered as a limited company in Tønsberg, Vestfold with organisation number 920611796. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Investering, utvikling, oppføring, utleie og salg av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 216,000 in revenue and NOK 124,000 in operating profit.

Key figures · 2025

Revenue
NOK 216,000
Operating profit
NOK 124,000
Equity
NOK 475,000
Est. value
NOK 607,000

Financial health · 2025

Liquidity
214.68
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.7%
Not satisfactory
Equity as a share of total capital

Who owns PRESTERØDÅSEN PANORAMA AS?

ESPELUNDEN AS
PRESTERØDÅSEN PANORAMA AS
NOK 216,000 rev. · NOK 124,000 profit

PRESTERØDÅSEN PANORAMA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PRESTERØDÅSEN PANORAMA AS

Who owns PRESTERØDÅSEN PANORAMA AS?

ESPELUNDEN AS is the largest registered owner, with 95.0%.

What is the revenue of PRESTERØDÅSEN PANORAMA AS?

PRESTERØDÅSEN PANORAMA AS had revenue of NOK 216,000 in 2025.

Where is PRESTERØDÅSEN PANORAMA AS based?

PRESTERØDÅSEN PANORAMA AS has its business address in Barkåker.

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.