BIZTRAC BETA
Manufacture of doors and windows of wood

HØIBY SNEKKERI AS

Org. no. 963614071 Limited company (AS) Selbu Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 17.3m
Operating profit NOK 1.7m
Equity NOK 3.3m
Incorporated 1992
Employees 10
Share capital NOK 240,000

HØIBY SNEKKERI AS is registered as a limited company in Selbu, Trøndelag with organisation number 963614071. The business is classified under manufacture of doors and windows of wood (NACE 16.250). The company was incorporated in 1992 and has 10 registered employees. Registered share capital is NOK 240,000. The company's stated purpose is: “Produksjon og salg av snekkeriprodukter og alt som dermed står i forbindelse, samt foreta investeringer, således kjøp og salg og utnyttelse av faste eiendommer, samt deltakelse som aksjonær eller på annen måte i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 17.3m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 17.3m
Operating profit
NOK 1.7m
Equity
NOK 3.3m
Est. value
NOK 8.2m

Financial health · 2025

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

Who owns HØIBY SNEKKERI AS?

HØIBY HOLDING AS
HØIBY SNEKKERI AS
NOK 17.3m rev. · NOK 1.7m profit

HØIBY SNEKKERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HØIBY SNEKKERI AS

Who owns HØIBY SNEKKERI AS?

HØIBY HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HØIBY SNEKKERI AS?

HØIBY SNEKKERI AS had revenue of NOK 17.3m in 2025.

Who is the general manager of HØIBY SNEKKERI AS?

Odd Ingar Høiby is registered as general manager of HØIBY SNEKKERI AS.

Where is HØIBY SNEKKERI AS based?

HØIBY SNEKKERI AS has its business address in Selbustrand.

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.