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

DIGG MIPCO AS

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

Signals

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

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

Key figures · 2025

Operating profit
NOK −4,000
Equity
NOK 385,000
Est. value
NOK 2.6m

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 DIGG MIPCO AS?

DIGG MIPCO AS has 6 registered shareholders:

All shareholders and roles →

Which companies does DIGG MIPCO AS own?

DIGG MIPCO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DIGG MIPCO AS

Who owns DIGG MIPCO AS?

GAUTE HODLING AS is the largest registered owner, with 64.1%.

Where is DIGG MIPCO AS based?

DIGG 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.