BIZTRAC BETA
Business and other management consultancy activities

ENNIMATO INVEST AS

Org. no. 914629632 Limited company (AS) Trondheim Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −5,000
Equity NOK 1.9m
Incorporated 2014
Share capital NOK 30,000

Signals

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

ENNIMATO INVEST AS is registered as a limited company in Trondheim, Trøndelag with organisation number 914629632. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, foreta kjøp og salg av verdipapir, drive konsulentvirksomhet samt delta i tilstøtende virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 1.9m
Est. value
NOK 4.8m

Financial health · 2024

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

Who owns ENNIMATO INVEST AS?

MARIA SÆTHER
ENNIMATO INVEST AS
NOK 0 rev. · NOK −5,000 profit

ENNIMATO INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ENNIMATO INVEST AS own?

ENNIMATO INVEST AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about ENNIMATO INVEST AS

Who owns ENNIMATO INVEST AS?

MARIA SÆTHER is the largest registered owner, with 50.0%.

What is the revenue of ENNIMATO INVEST AS?

ENNIMATO INVEST AS had revenue of NOK 0 in 2024.

Where is ENNIMATO INVEST AS based?

ENNIMATO INVEST AS has its business address in Ranheim.

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.