BIZTRAC BETA
Business and other management consultancy activities

ENERVITAE AS

Org. no. 992744693 Limited company (AS) Bærum Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −92,000
Equity NOK 4.3m
Incorporated 2008
Share capital NOK 177,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−92k kr).

ENERVITAE AS is registered as a limited company in Bærum, Akershus with organisation number 992744693. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2008. Registered share capital is NOK 177,000, divided into 176924 shares. The company's stated purpose is: “Delta i andre selskaper med egenkapital og lån samt yte industriell rådgiving.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −92,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −92,000
Equity
NOK 4.3m
Est. value
NOK 7.0m

Financial health · 2025

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

Who owns ENERVITAE AS?

KNUD HANS NØRVE
ENERVITAE AS
NOK 0 rev. · NOK −92,000 profit

ENERVITAE AS has 4 registered shareholders:

All shareholders and roles →

Which companies does ENERVITAE AS own?

ENERVITAE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ENERVITAE AS

Who owns ENERVITAE AS?

KNUD HANS NØRVE is the largest registered owner, with 73.7%.

What is the revenue of ENERVITAE AS?

ENERVITAE AS had revenue of NOK 0 in 2025.

Who is the general manager of ENERVITAE AS?

Knud Hans Nørve is registered as general manager of ENERVITAE AS.

Where is ENERVITAE AS based?

ENERVITAE AS has its business address in Haslum.

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.