BIZTRAC BETA
COMPANY REGISTER PROFILE
925149616 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

BLID MIPCO AS

Org. no. 925149616 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 368,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

BLID MIPCO AS is registered as a limited company in Oslo, Oslo with organisation number 925149616. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 303798 shares. The company's stated purpose is: “Investere i og rådgi ulike selskaper.”.

Key figures · 2025

Operating profit
NOK −4,000
▼ −6 %
Equity
NOK 368,000
▼ −1 %
Est. value
NOK 432,000

Financial health · 2025

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

Who owns BLID MIPCO AS?

BLID MIPCO AS has 4 registered shareholders:

All shareholders and roles →

Which companies does BLID MIPCO AS own?

BLID MIPCO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BLID MIPCO AS

Who owns BLID MIPCO AS?

LANGE LØP AS is the largest registered owner, with 63.5%.

Where is BLID MIPCO AS based?

BLID MIPCO AS has its business address in Oslo.

Property

Business address Parkveien 12, 0350 Oslo
Cadastral unit 301-214/253/0/0
Building Hospits, pensjonat · 2 units

86 companies are registered at this address.

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.