BIZTRAC BETA
Construction of residential and non-residential buildings

ELVEBAKKEN BYGG AS

Org. no. 917239363 Limited company (AS) Alta Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 90.9m
Operating profit NOK 8.4m
Equity NOK 8.7m
Incorporated 2016
Employees 47
Share capital NOK 302,000

Signals

1 flags
  • Nylig endring 2026-07-13 Aksjekapital registrert 2026-07-13.

ELVEBAKKEN BYGG AS is registered as a limited company in Alta, Finnmark with organisation number 917239363. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016 and has 47 registered employees. Registered share capital is NOK 302,000, divided into 45000 shares. The company's stated purpose is: “Bygg og tømrervirksomhet og alt som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 90.9m in revenue and NOK 8.4m in operating profit.

Key figures · 2025

Revenue
NOK 90.9m
Operating profit
NOK 8.4m
Equity
NOK 8.7m
Est. value
NOK 31.7m

Financial health · 2025

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

Who owns ELVEBAKKEN BYGG AS?

GUNNAR OLSEN INVEST AS
ELVEBAKKEN BYGG AS
NOK 90.9m rev. · NOK 8.4m profit

ELVEBAKKEN BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ELVEBAKKEN BYGG AS

Who owns ELVEBAKKEN BYGG AS?

GUNNAR OLSEN INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of ELVEBAKKEN BYGG AS?

ELVEBAKKEN BYGG AS had revenue of NOK 90.9m in 2025.

Who is the general manager of ELVEBAKKEN BYGG AS?

Gunnar Olsen is registered as general manager of ELVEBAKKEN BYGG AS.

Where is ELVEBAKKEN BYGG AS based?

ELVEBAKKEN BYGG AS has its business address in Alta.

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.