BIZTRAC BETA
Construction of residential and non-residential buildings

PÅL MIKKEL DALSBOTTEN AS

Org. no. 995081393 Limited company (AS) Aurland Incorporated 2010 Active
Ownership graph ↗
Operating profit NOK −457,000
Equity NOK 3.7m
Incorporated 2010
Share capital NOK 100,000

Signals

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

PÅL MIKKEL DALSBOTTEN AS is registered as a limited company in Aurland, Vestland with organisation number 995081393. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Entreprenørverksemd med oppføring og reparasjon av hus og hytter, taksering, og anna tenesteyting som naturleg høyrer saman.”.

Key figures · 2025

Operating profit
NOK −457,000
Equity
NOK 3.7m
Est. value
NOK 3.8m

Financial health · 2025

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

Who owns PÅL MIKKEL DALSBOTTEN AS?

PÅL MIKKEL DALSBOTTEN
PÅL MIKKEL DALSBOTTEN AS
· NOK −457,000 profit

PÅL MIKKEL DALSBOTTEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PÅL MIKKEL DALSBOTTEN AS own?

PÅL MIKKEL DALSBOTTEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PÅL MIKKEL DALSBOTTEN AS

Who owns PÅL MIKKEL DALSBOTTEN AS?

PÅL MIKKEL DALSBOTTEN is the largest registered owner, with 100.0%.

Who is the general manager of PÅL MIKKEL DALSBOTTEN AS?

Pål Mikkel Dalsbotten is registered as general manager of PÅL MIKKEL DALSBOTTEN AS.

Where is PÅL MIKKEL DALSBOTTEN AS based?

PÅL MIKKEL DALSBOTTEN AS has its business address in Flåm.

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.