BIZTRAC BETA
Plumbing installation

MIDTSVEEN HOLDING AS

Org. no. 926531808 Limited company (AS) Flesberg Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −24,000
Equity NOK 713,000
Incorporated 2020
Share capital NOK 70,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−24k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MIDTSVEEN HOLDING AS is registered as a limited company in Flesberg, Buskerud with organisation number 926531808. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2020. Registered share capital is NOK 70,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”.

Key figures · 2025

Operating profit
NOK −24,000
Equity
NOK 713,000
Est. value
NOK 730,000

Financial health · 2025

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

Who owns MIDTSVEEN HOLDING AS?

OLE HELGE SØNÅSEN
MIDTSVEEN HOLDING AS
· NOK −24,000 profit

MIDTSVEEN HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does MIDTSVEEN HOLDING AS own?

MIDTSVEEN HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about MIDTSVEEN HOLDING AS

Who owns MIDTSVEEN HOLDING AS?

OLE HELGE SØNÅSEN is the largest registered owner, with 26.0%.

Who is the general manager of MIDTSVEEN HOLDING AS?

Ole Helge Sønåsen is registered as general manager of MIDTSVEEN HOLDING AS.

Where is MIDTSVEEN HOLDING AS based?

MIDTSVEEN HOLDING AS has its business address in Lyngdal I Numedal.

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.