BIZTRAC BETA
Other captive investment companies

MIISMO AS

Org. no. 916863179 Limited company (AS) Bamble Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK 68,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

MIISMO AS is registered as a limited company in Bamble, Telemark with organisation number 916863179. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og andeler samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 68,000
Est. value
NOK 62,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MIISMO AS?

SIGNE MARIE GRAVE OLAND
MIISMO AS
NOK 0 rev. · NOK −3,000 profit

MIISMO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MIISMO AS own?

MIISMO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MIISMO AS

Who owns MIISMO AS?

SIGNE MARIE GRAVE OLAND is the largest registered owner, with 100.0%.

What is the revenue of MIISMO AS?

MIISMO AS had revenue of NOK 0 in 2025.

Who is the general manager of MIISMO AS?

Signe Marie Grave Oland is registered as general manager of MIISMO AS.

Where is MIISMO AS based?

MIISMO AS has its business address in Langesund.

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.