BIZTRAC BETA
Joinery installation

HOLTLEITE SNEKKERSERVICE AS

Org. no. 935713412 Limited company (AS) Ålesund Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 384,000
Operating profit NOK 107,000
Equity NOK 109,000
Incorporated 2025
Share capital NOK 30,000

HOLTLEITE SNEKKERSERVICE AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 935713412. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Snekkerarbeid, rehabilitering, vedlikehold og montering og annet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 384,000 in revenue and NOK 107,000 in operating profit.

Key figures · 2025

Revenue
NOK 384,000
Operating profit
NOK 107,000
Equity
NOK 109,000
Est. value
NOK 362,000

Financial health · 2025

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
40.2%
Very good
Equity as a share of total capital

Who owns HOLTLEITE SNEKKERSERVICE AS?

FRODE VAD HOLTLEITE
HOLTLEITE SNEKKERSERVICE AS
NOK 384,000 rev. · NOK 107,000 profit

HOLTLEITE SNEKKERSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOLTLEITE SNEKKERSERVICE AS

Who owns HOLTLEITE SNEKKERSERVICE AS?

FRODE VAD HOLTLEITE is the largest registered owner, with 100.0%.

What is the revenue of HOLTLEITE SNEKKERSERVICE AS?

HOLTLEITE SNEKKERSERVICE AS had revenue of NOK 384,000 in 2025.

Who is the general manager of HOLTLEITE SNEKKERSERVICE AS?

Frode Vad Holtleite is registered as general manager of HOLTLEITE SNEKKERSERVICE AS.

Where is HOLTLEITE SNEKKERSERVICE AS based?

HOLTLEITE SNEKKERSERVICE AS has its business address in Ålesund.

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.