BIZTRAC BETA
Construction of residential and non-residential buildings

MULTIBYGG MØRE AS

Org. no. 926582410 Limited company (AS) Ålesund Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 146,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

MULTIBYGG MØRE AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 926582410. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Oppføring og vedlikehold av bygninger og annet som måtte ha tilknytning til dette. Kjøp og salg av aksjer og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 146,000
Est. value
NOK 150,000

Financial health · 2025

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

Who owns MULTIBYGG MØRE AS?

ARNE GRØNVIK
MULTIBYGG MØRE AS
NOK 0 rev. · NOK −14,000 profit

MULTIBYGG MØRE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MULTIBYGG MØRE AS

Who owns MULTIBYGG MØRE AS?

ARNE GRØNVIK is the largest registered owner, with 100.0%.

What is the revenue of MULTIBYGG MØRE AS?

MULTIBYGG MØRE AS had revenue of NOK 0 in 2025.

Who is the general manager of MULTIBYGG MØRE AS?

Arne Grønvik is registered as general manager of MULTIBYGG MØRE AS.

Where is MULTIBYGG MØRE AS based?

MULTIBYGG MØRE AS has its business address in Ålesund.

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.