BIZTRAC BETA
Other real estate activities on a fee or contract basis

PROPELLEN AS

Org. no. 924373210 Limited company (AS) Harstad Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −27,000
Equity NOK 5.9m
Incorporated 2019
Share capital NOK 1.6m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−27k kr).

PROPELLEN AS is registered as a limited company in Harstad, Troms with organisation number 924373210. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2019. Registered share capital is NOK 1.6m, divided into 100 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter å forestå investeringsvirksomhet, eiendomsforvaltning, forretningsførsel og annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −27,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −27,000
Equity
NOK 5.9m
Est. value
NOK 4.9m

Financial health · 2024

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

Who owns PROPELLEN AS?

BENDIX KAPITAL AS
PROPELLEN AS
NOK 0 rev. · NOK −27,000 profit

PROPELLEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does PROPELLEN AS own?

PROPELLEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PROPELLEN AS

Who owns PROPELLEN AS?

BENDIX KAPITAL AS is the largest registered owner, with 50.0%.

What is the revenue of PROPELLEN AS?

PROPELLEN AS had revenue of NOK 0 in 2024.

Where is PROPELLEN AS based?

PROPELLEN AS has its business address in Harstad.

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.