BIZTRAC BETA
Construction of residential and non-residential buildings

MØREBYGG AS

Org. no. 927418169 Limited company (AS) Ålesund Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 37,000
Equity NOK 87,000
Incorporated 2021
Employees 5
Share capital NOK 30,000

MØREBYGG AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 927418169. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Bygge og vaktmestertjenester”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 37,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 37,000
Equity
NOK 87,000
Est. value
NOK 165,000

Financial health · 2024

Liquidity
0.78
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MØREBYGG AS?

MARIUSZ PAWEL MYTLEWSKI
MØREBYGG AS
NOK 2.2m rev. · NOK 37,000 profit

MØREBYGG AS has 4 registered shareholders:

All shareholders and roles →

Which companies does MØREBYGG AS own?

MØREBYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MØREBYGG AS

Who owns MØREBYGG AS?

MARIUSZ PAWEL MYTLEWSKI is the largest registered owner, with 30.0%.

What is the revenue of MØREBYGG AS?

MØREBYGG AS had revenue of NOK 2.2m in 2024.

Who is the general manager of MØREBYGG AS?

Trond Klokkersund is registered as general manager of MØREBYGG AS.

Where is MØREBYGG AS based?

MØREBYGG 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.