BIZTRAC BETA
Other manufacturing n.e.c.

HENNINGSVÆR LYSSTØPERI AS

Org. no. 918329900 Limited company (AS) Vågan Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 9.8m
Operating profit NOK 2.6m
Equity NOK 1.9m
Incorporated 2016
Employees 12
Share capital NOK 30,000

HENNINGSVÆR LYSSTØPERI AS is registered as a limited company in Vågan, Nordland with organisation number 918329900. The business is classified under other manufacturing n.e.c. (NACE 32.990). The company was incorporated in 2016 and has 12 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Produksjon og salg av lys. Drift av kafe og restuarant og det som naturlig tilhører dette, samt deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.8m in revenue and NOK 2.6m in operating profit.

Key figures · 2024

Revenue
NOK 9.8m
Operating profit
NOK 2.6m
Equity
NOK 1.9m
Est. value
NOK 9.2m

Financial health · 2024

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

Who owns HENNINGSVÆR LYSSTØPERI AS?

BONTOM HOLDING AS
HENNINGSVÆR LYSSTØPERI AS
NOK 9.8m rev. · NOK 2.6m profit

HENNINGSVÆR LYSSTØPERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HENNINGSVÆR LYSSTØPERI AS

Who owns HENNINGSVÆR LYSSTØPERI AS?

BONTOM HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HENNINGSVÆR LYSSTØPERI AS?

HENNINGSVÆR LYSSTØPERI AS had revenue of NOK 9.8m in 2024.

Who is the general manager of HENNINGSVÆR LYSSTØPERI AS?

Thea Tabita Bonde is registered as general manager of HENNINGSVÆR LYSSTØPERI AS.

Where is HENNINGSVÆR LYSSTØPERI AS based?

HENNINGSVÆR LYSSTØPERI AS has its business address in Henningsvær.

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.