BIZTRAC BETA
Development of building projects

AKTIV VEKST AS

Org. no. 978670237 Limited company (AS) Nesna Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −1.4m
Equity NOK 36.2m
Incorporated 1997
Share capital NOK 375,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,4 mill kr).

AKTIV VEKST AS is registered as a limited company in Nesna, Nordland with organisation number 978670237. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1997. Registered share capital is NOK 375,000, divided into 7500 shares. The company's stated purpose is: “Investeringer og aktiv deltakelse gjennom konsulentvirksomhet i investerte selskaper og andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −1.4m in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −1.4m
Equity
NOK 36.2m
Est. value
NOK 30.6m

Financial health · 2024

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

Who owns AKTIV VEKST AS?

JON NEERAAS
AKTIV VEKST AS
NOK 0 rev. · NOK −1.4m profit

AKTIV VEKST AS has 5 registered shareholders:

All shareholders and roles →

Which companies does AKTIV VEKST AS own?

AKTIV VEKST AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about AKTIV VEKST AS

Who owns AKTIV VEKST AS?

JON NEERAAS is the largest registered owner, with 34.0%.

What is the revenue of AKTIV VEKST AS?

AKTIV VEKST AS had revenue of NOK 0 in 2024.

Who is the general manager of AKTIV VEKST AS?

Jon Neeraas is registered as general manager of AKTIV VEKST AS.

Where is AKTIV VEKST AS based?

AKTIV VEKST AS has its business address in Nesna.

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.