BIZTRAC BETA
Construction of residential and non-residential buildings

EMBLEM BYGG AS

Org. no. 981090802 Limited company (AS) Ålesund Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 5.8m
Operating profit NOK 1.4m
Equity NOK 10.7m
Incorporated 1999
Share capital NOK 100,000

EMBLEM BYGG AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 981090802. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive byggmesterfirma medtilhørende aktiviteter samt gjennom aksjekjøp delta i andre selskap som har økonomiske formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.8m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 5.8m
Operating profit
NOK 1.4m
Equity
NOK 10.7m
Est. value
NOK 7.9m

Financial health · 2024

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

Who owns EMBLEM BYGG AS?

GUNNAR KARL EMBLEM
EMBLEM BYGG AS
NOK 5.8m rev. · NOK 1.4m profit

EMBLEM BYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EMBLEM BYGG AS own?

EMBLEM BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EMBLEM BYGG AS

Who owns EMBLEM BYGG AS?

GUNNAR KARL EMBLEM is the largest registered owner, with 100.0%.

What is the revenue of EMBLEM BYGG AS?

EMBLEM BYGG AS had revenue of NOK 5.8m in 2024.

Who is the general manager of EMBLEM BYGG AS?

Gunnar Karl Emblem is registered as general manager of EMBLEM BYGG AS.

Where is EMBLEM BYGG AS based?

EMBLEM 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.