BIZTRAC BETA
COMPANY REGISTER PROFILE
989276263 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

MISTY INVEST AS

Org. no. 989276263 Limited company (AS) Øygarden Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −17,000
Equity NOK 34.7m
Incorporated 2005
Share capital NOK 351,000

Signals

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

MISTY INVEST AS is registered as a limited company in Øygarden, Vestland with organisation number 989276263. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 351,000, divided into 175732 shares. The company's stated purpose is: “Å foreta kapitalforvaltning og aksjeinvestering, samt alt hva herved står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −17,000
▼ −247 %
Equity
NOK 34.7m
▼ −9 %
Est. value
NOK 23.4m

Financial health · 2025

Liquidity
94.64
Very good
Current assets ÷ current liabilities
Profitability
4.3%
Weak
Return on total assets
Solidity
99.0%
Very good
Equity as a share of total capital

Who owns MISTY INVEST AS?

MISTY INVEST AS
· NOK −17,000 profit

MISTY INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MISTY INVEST AS

Who owns MISTY INVEST AS?

GERD LIE is the largest registered owner, with 100.0%.

Where is MISTY INVEST AS based?

MISTY INVEST AS has its business address in Kolltveit.

Property

Business address Liaskjervegen 171, 5360 Kolltveit
Cadastral unit 4626-49/33/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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