BIZTRAC BETA
Growing of vegetables and melons, roots and tubers

POLARHAGEN LOFOTEN AS

Org. no. 928833798 Limited company (AS) Ås Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 547,000
Operating profit NOK −83,000
Equity NOK −3,000
Incorporated 2022
Share capital NOK 225,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−83k kr).
  • Nylig endring 2026-05-04 Adresseendring registrert 2026-05-04.

POLARHAGEN LOFOTEN AS is registered as a limited company in Ås, Akershus with organisation number 928833798. The business is classified under growing of vegetables and melons, roots and tubers (NACE 01.130). The company was incorporated in 2022. Registered share capital is NOK 225,000, divided into 15 shares. The company's stated purpose is: “Økologisk grønnsaksgård.”. The most recent filed accounts, for the 2024 financial year, show NOK 547,000 in revenue and NOK −83,000 in operating profit.

Key figures · 2024

Revenue
NOK 547,000
Operating profit
NOK −83,000
Equity
NOK −3,000

Financial health · 2024

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

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

Who owns POLARHAGEN LOFOTEN AS?

PARSA MASSAHI
POLARHAGEN LOFOTEN AS
NOK 547,000 rev. · NOK −83,000 profit

POLARHAGEN LOFOTEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about POLARHAGEN LOFOTEN AS

Who owns POLARHAGEN LOFOTEN AS?

PARSA MASSAHI is the largest registered owner, with 53.3%.

What is the revenue of POLARHAGEN LOFOTEN AS?

POLARHAGEN LOFOTEN AS had revenue of NOK 547,000 in 2024.

Where is POLARHAGEN LOFOTEN AS based?

POLARHAGEN LOFOTEN AS has its business address in Ås.

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.