BIZTRAC BETA
Wholesale of china and glassware and cleaning materials

HEYERDAHL HANDEL AS

Org. no. 993356921 Limited company (AS) Drammen Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 31.5m
Operating profit NOK 1.0m
Equity NOK 5.0m
Incorporated 2008
Share capital NOK 200,000

HEYERDAHL HANDEL AS is registered as a limited company in Drammen, Buskerud with organisation number 993356921. The business is classified under wholesale of china and glassware and cleaning materials (NACE 46.440). The company was incorporated in 2008. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Salg, handel og agentvirksomhet med dertil hørende aktiviteter. Det skal også være anledning til å eie aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 31.5m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 31.5m
Operating profit
NOK 1.0m
Equity
NOK 5.0m
Est. value
NOK 5.3m

Financial health · 2025

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

Who owns HEYERDAHL HANDEL AS?

CAROLINE CHRISTINE HEYERDAHL
HEYERDAHL HANDEL AS
NOK 31.5m rev. · NOK 1.0m profit

HEYERDAHL HANDEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEYERDAHL HANDEL AS

Who owns HEYERDAHL HANDEL AS?

CAROLINE CHRISTINE HEYERDAHL is the largest registered owner, with 100.0%.

What is the revenue of HEYERDAHL HANDEL AS?

HEYERDAHL HANDEL AS had revenue of NOK 31.5m in 2025.

Who is the general manager of HEYERDAHL HANDEL AS?

Caroline Christine Heyerdahl is registered as general manager of HEYERDAHL HANDEL AS.

Where is HEYERDAHL HANDEL AS based?

HEYERDAHL HANDEL AS has its business address in Drammen.

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.