BIZTRAC BETA
Construction of residential and non-residential buildings

HYEN BYGG AS

Org. no. 983480411 Limited company (AS) Gloppen Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK 106,000
Equity NOK 1.0m
Incorporated 2001
Share capital NOK 330,000

HYEN BYGG AS is registered as a limited company in Gloppen, Vestland with organisation number 983480411. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2001. Registered share capital is NOK 330,000, divided into 660 shares. The company's stated purpose is: “Entreprenørverksemd og rådgjevande ingeniørverksemd innanfor byggfaga, handel med byggvarer og maskinutleige.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK 106,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK 106,000
Equity
NOK 1.0m
Est. value
NOK 950,000

Financial health · 2024

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

Who owns HYEN BYGG AS?

BJØRN KRISTIAN EGGESVIK HOLME
HYEN BYGG AS
NOK 2.3m rev. · NOK 106,000 profit

HYEN BYGG AS has 7 registered shareholders:

All shareholders and roles →

Which companies does HYEN BYGG AS own?

HYEN BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HYEN BYGG AS

Who owns HYEN BYGG AS?

BJØRN KRISTIAN EGGESVIK HOLME is the largest registered owner, with 18.2%.

What is the revenue of HYEN BYGG AS?

HYEN BYGG AS had revenue of NOK 2.3m in 2024.

Who is the general manager of HYEN BYGG AS?

Bjørn Kristian Eggesvik Holme is registered as general manager of HYEN BYGG AS.

Where is HYEN BYGG AS based?

HYEN BYGG AS has its business address in Hyen.

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.