BIZTRAC BETA
Painting and glazing

HÅNDVERK OG EIENDOM AS

Org. no. 984660022 Limited company (AS) Larvik Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 678,000
Operating profit NOK 263,000
Equity NOK 109,000
Incorporated 2002
Share capital NOK 100,000

HÅNDVERK OG EIENDOM AS is registered as a limited company in Larvik, Vestfold with organisation number 984660022. The business is classified under painting and glazing (NACE 43.340). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Håndverksvirksomhet innen bygg og anlegg, kjøp og salg og drift av fast eiendom, og hva dermed står i forbindelse. Likeledes deltagelse i andre selskaper. ”. The most recent filed accounts, for the 2024 financial year, show NOK 678,000 in revenue and NOK 263,000 in operating profit.

Key figures · 2024

Revenue
NOK 678,000
Operating profit
NOK 263,000
Equity
NOK 109,000
Est. value
NOK 808,000

Financial health · 2024

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

Who owns HÅNDVERK OG EIENDOM AS?

ALVHILD VEBJØRG FONN-SUNDE
HÅNDVERK OG EIENDOM AS
NOK 678,000 rev. · NOK 263,000 profit

HÅNDVERK OG EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HÅNDVERK OG EIENDOM AS

Who owns HÅNDVERK OG EIENDOM AS?

ALVHILD VEBJØRG FONN-SUNDE is the largest registered owner, with 50.0%.

What is the revenue of HÅNDVERK OG EIENDOM AS?

HÅNDVERK OG EIENDOM AS had revenue of NOK 678,000 in 2024.

Who is the general manager of HÅNDVERK OG EIENDOM AS?

Terje Helgeland is registered as general manager of HÅNDVERK OG EIENDOM AS.

Where is HÅNDVERK OG EIENDOM AS based?

HÅNDVERK OG EIENDOM AS has its business address in Larvik.

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.