biztrac. BETA
COMPANY REGISTER PROFILE
967539082 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

EIKER HUSBYGG AS

Org. no. 967539082 Limited company (AS) Drammen Incorporated 1993 Active
Revenue 2025 NOK 23.2m
Operating profit NOK 490,000
Equity NOK 2.0m
Incorporated 1993
Employees 13
Share capital NOK 100,000

EIKER HUSBYGG AS is registered as a limited company in Drammen, Buskerud with organisation number 967539082. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1993 and has 13 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Byggevirksomhet samt andre tjenester som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 23.2m in revenue and NOK 490,000 in operating profit.

Key figures · 2025

Revenue
NOK 23.2m
▼ −19 %
Operating profit
NOK 490,000
▼ −46 %
Equity
NOK 2.0m
▲ +8 %
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
1.75
Good
Current assets ÷ current liabilities
Profitability
4.6%
Weak
Return on total assets
Solidity
18.1%
Good
Equity as a share of total capital

Who owns EIKER HUSBYGG AS?

EIKER HUSBYGG AS
NOK 23.2m rev. · NOK 490,000 profit

EIKER HUSBYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EIKER HUSBYGG AS

Who owns EIKER HUSBYGG AS?

EIKER HUSBYGG HOLDING AS is the largest registered owner, with 80.0%.

What is the revenue of EIKER HUSBYGG AS?

EIKER HUSBYGG AS had revenue of NOK 23.2m in 2025.

Who is the general manager of EIKER HUSBYGG AS?

Roger Hagen is registered as general manager of EIKER HUSBYGG AS.

Where is EIKER HUSBYGG AS based?

EIKER HUSBYGG AS has its business address in Mjøndalen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.