BIZTRAC BETA
Rental and operating of own or leased real estate

POLARBAD VEST EIENDOM AS

Org. no. 928590070 Limited company (AS) Ålesund Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 929,000
Equity NOK 4.5m
Incorporated 2022
Share capital NOK 100,000

POLARBAD VEST EIENDOM AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 928590070. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Anskaffelse, drift og utleie av fast eiendom, samt deltakelse i andre selskap med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 929,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 929,000
Equity
NOK 4.5m
Est. value
NOK 5.2m

Financial health · 2025

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

Who owns POLARBAD VEST EIENDOM AS?

POLARBAD VEST HOLDING AS
POLARBAD VEST EIENDOM AS
NOK 1.3m rev. · NOK 929,000 profit

POLARBAD VEST EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about POLARBAD VEST EIENDOM AS

Who owns POLARBAD VEST EIENDOM AS?

POLARBAD VEST HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of POLARBAD VEST EIENDOM AS?

POLARBAD VEST EIENDOM AS had revenue of NOK 1.3m in 2025.

Who is the general manager of POLARBAD VEST EIENDOM AS?

Frank Vedeld is registered as general manager of POLARBAD VEST EIENDOM AS.

Where is POLARBAD VEST EIENDOM AS based?

POLARBAD VEST EIENDOM AS has its business address in Skodje.

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.