BIZTRAC BETA
Other specialised construction activities n.e.c.

MØRE ENTREPRENØR BYGG AS

Org. no. 934354079 Limited company (AS) Ålesund Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −3,000
Equity NOK 21,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).

MØRE ENTREPRENØR BYGG AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 934354079. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Betongarbeid med fokus på små og mellomstore byggeprosjekter, samt det som naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 21,000
Est. value
NOK 21,000

Financial health · 2024

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

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

Who owns MØRE ENTREPRENØR BYGG AS?

MØRE ENTREPRENØR HOLDING AS
MØRE ENTREPRENØR BYGG AS
NOK 0 rev. · NOK −3,000 profit

MØRE ENTREPRENØR BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MØRE ENTREPRENØR BYGG AS

Who owns MØRE ENTREPRENØR BYGG AS?

MØRE ENTREPRENØR HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MØRE ENTREPRENØR BYGG AS?

MØRE ENTREPRENØR BYGG AS had revenue of NOK 0 in 2024.

Where is MØRE ENTREPRENØR BYGG AS based?

MØRE ENTREPRENØR BYGG 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.