biztrac. BETA
COMPANY REGISTER PROFILE
921153082 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠EKSPERTEN INVEST AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Rental and operating of own or leased real estate

EKSPERTEN INVEST AS

Org. no. 921153082 Limited company (AS) Trondheim Incorporated 2018 In liquidation
Ownership graph ↗
Operating profit NOK −55,000
Equity NOK 255,000
Incorporated 2018
Share capital NOK 80,000

Signals

2 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−55k kr).

EKSPERTEN INVEST AS is registered as a limited company in Trondheim, Trøndelag with organisation number 921153082. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 80,000, divided into 200 shares. The company's stated purpose is: “Å eie aksjer og andeler i andre selskaper, samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −55,000
▼ −72 %
Equity
NOK 255,000
▼ −92 %

Financial health · 2025

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

Who owns EKSPERTEN INVEST AS?

EKSPERTEN INVEST AS
· NOK −55,000 profit

EKSPERTEN INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does EKSPERTEN INVEST AS own?

EKSPERTEN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EKSPERTEN INVEST AS

Who owns EKSPERTEN INVEST AS?

SVINNDAL HOLDING AS is the largest registered owner, with 50.5%.

Where is EKSPERTEN INVEST AS based?

EKSPERTEN INVEST AS has its business address in Trondheim.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.