biztrac. BETA
COMPANY REGISTER PROFILE
919395788 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Civil engineering activities

MIKALSEN BYGGADMINISTRASJON AS

Org. no. 919395788 Limited company (AS) Stavanger Incorporated 2017 Active
Operating profit NOK −14,000
Equity NOK 104,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

MIKALSEN BYGGADMINISTRASJON AS is registered as a limited company in Stavanger, Rogaland with organisation number 919395788. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Prosjektledelse og byggadministrasjon.”.

Key figures · 2025

Operating profit
NOK −14,000
▲ +61 %
Equity
NOK 104,000
▼ −12 %
Est. value
NOK 169,000

Financial health · 2025

Liquidity
0.63
Weak
Current assets ÷ current liabilities
Profitability
-3.4%
Not satisfactory
Return on total assets
Solidity
26.0%
Good
Equity as a share of total capital

Who owns MIKALSEN BYGGADMINISTRASJON AS?

MIKALSEN BYGGADMINISTRASJON AS
· NOK −14,000 profit

MIKALSEN BYGGADMINISTRASJON AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MIKALSEN BYGGADMINISTRASJON AS own?

MIKALSEN BYGGADMINISTRASJON AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MIKALSEN BYGGADMINISTRASJON AS

Who owns MIKALSEN BYGGADMINISTRASJON AS?

Bjørn Inge Mikalsen is the largest registered owner, with 100.0%.

Who is the general manager of MIKALSEN BYGGADMINISTRASJON AS?

Bjørn Inge Mikalsen is registered as general manager of MIKALSEN BYGGADMINISTRASJON AS.

Where is MIKALSEN BYGGADMINISTRASJON AS based?

MIKALSEN BYGGADMINISTRASJON AS has its business address in Hafrsfjord.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.