BIZTRAC BETA
Site preparation

ELMA ENTREPRENØR AS

Org. no. 933664791 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 22.9m
Operating profit NOK 820,000
Equity NOK 1.4m
Incorporated 2024
Employees 5
Share capital NOK 200,000

ELMA ENTREPRENØR AS is registered as a limited company in Bergen, Vestland with organisation number 933664791. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2024 and has 5 registered employees. Registered share capital is NOK 200,000, divided into 200000 shares. The company's stated purpose is: “Entreprenørvirksomhet innen bygg og anlegg og det som naturlig har tilknytning til dette, investering i aksjer og andeler i andre foretak, samt investering og utvikling av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 22.9m in revenue and NOK 820,000 in operating profit.

Key figures · 2025

Revenue
NOK 22.9m
Operating profit
NOK 820,000
Equity
NOK 1.4m
Est. value
NOK 3.2m

Financial health · 2025

Liquidity
1.50
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.6%
Good
Equity as a share of total capital

Who owns ELMA ENTREPRENØR AS?

ELMA BYGG OG EIENDOM AS
ELMA ENTREPRENØR AS
NOK 22.9m rev. · NOK 820,000 profit

ELMA ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELMA ENTREPRENØR AS

Who owns ELMA ENTREPRENØR AS?

ELMA BYGG OG EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of ELMA ENTREPRENØR AS?

ELMA ENTREPRENØR AS had revenue of NOK 22.9m in 2025.

Who is the general manager of ELMA ENTREPRENØR AS?

Svein-Åge Sivertsen is registered as general manager of ELMA ENTREPRENØR AS.

Where is ELMA ENTREPRENØR AS based?

ELMA ENTREPRENØR AS has its business address in Indre Arna.

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.