BIZTRAC BETA
Floor and wall covering

HEKA BYGG EIENDOM AS

Org. no. 921429487 Limited company (AS) Gratangen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 14.2m
Operating profit NOK 230,000
Equity NOK 2.1m
Incorporated 2018
Employees 20
Share capital NOK 50,000

HEKA BYGG EIENDOM AS is registered as a limited company in Gratangen, Troms with organisation number 921429487. The business is classified under floor and wall covering (NACE 43.330). The company was incorporated in 2018 and has 20 registered employees. Registered share capital is NOK 50,000, divided into 2000 shares. The company's stated purpose is: “Drive med utleie og kjøp av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.2m in revenue and NOK 230,000 in operating profit.

Key figures · 2024

Revenue
NOK 14.2m
Operating profit
NOK 230,000
Equity
NOK 2.1m
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns HEKA BYGG EIENDOM AS?

HENRIK ANDRE PAULSEN
HEKA BYGG EIENDOM AS
NOK 14.2m rev. · NOK 230,000 profit

HEKA BYGG EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HEKA BYGG EIENDOM AS own?

HEKA BYGG EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HEKA BYGG EIENDOM AS

Who owns HEKA BYGG EIENDOM AS?

HENRIK ANDRE PAULSEN is the largest registered owner, with 50.0%.

What is the revenue of HEKA BYGG EIENDOM AS?

HEKA BYGG EIENDOM AS had revenue of NOK 14.2m in 2024.

Who is the general manager of HEKA BYGG EIENDOM AS?

Karolis Motiejunas is registered as general manager of HEKA BYGG EIENDOM AS.

Where is HEKA BYGG EIENDOM AS based?

HEKA BYGG EIENDOM AS has its business address in Gratangen.

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.