BIZTRAC BETA
COMPANY REGISTER PROFILE
932451476 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

HEIN EIENDOM AS

Org. no. 932451476 Limited company (AS) Øvre Eiker Incorporated 1977 Active
Ownership graph ↗
Revenue 2025 NOK 833,000
Operating profit NOK 87,000
Equity NOK 2.2m
Incorporated 1977
Share capital NOK 100,000

HEIN EIENDOM AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 932451476. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1977. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Kjøp og utleie av fast eiendom, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 833,000 in revenue and NOK 87,000 in operating profit.

Former names: AUTO LACK AS, AUTO-LACK EIENDOM AS

Key figures · 2025

Revenue
NOK 833,000
▲ +2 %
Operating profit
NOK 87,000
▼ −46 %
Equity
NOK 2.2m
▲ +4 %
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
3.15
Very good
Current assets ÷ current liabilities
Profitability
3.5%
Weak
Return on total assets
Solidity
89.4%
Very good
Equity as a share of total capital

Who owns HEIN EIENDOM AS?

HEIN EIENDOM AS
NOK 833,000 rev. · NOK 87,000 profit

HEIN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HEIN EIENDOM AS

Who owns HEIN EIENDOM AS?

JAN HEIN GUNDERSEN is the largest registered owner, with 50.0%.

What is the revenue of HEIN EIENDOM AS?

HEIN EIENDOM AS had revenue of NOK 833,000 in 2025.

Who is the general manager of HEIN EIENDOM AS?

Jan Hein Gundersen is registered as general manager of HEIN EIENDOM AS.

Where is HEIN EIENDOM AS based?

HEIN EIENDOM AS has its business address in Hokksund.

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

Report a problem

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