BIZTRAC BETA
Silviculture and other forestry activities

INGENIØR RAVN HUNSTAD AS

Org. no. 926395319 Limited company (AS) Vågan Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 219,000
Equity NOK 742,000
Incorporated 2021
Employees 11
Share capital NOK 60,000

INGENIØR RAVN HUNSTAD AS is registered as a limited company in Vågan, Nordland with organisation number 926395319. The business is classified under silviculture and other forestry activities (NACE 02.100). The company was incorporated in 2021 and has 11 registered employees. Registered share capital is NOK 60,000, divided into 300 shares. The company's stated purpose is: “Trepleie, ingeniørtjenester og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 219,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 219,000
Equity
NOK 742,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns INGENIØR RAVN HUNSTAD AS?

BJARNE RAVN HUNSTAD
INGENIØR RAVN HUNSTAD AS
NOK 2.9m rev. · NOK 219,000 profit

INGENIØR RAVN HUNSTAD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INGENIØR RAVN HUNSTAD AS

Who owns INGENIØR RAVN HUNSTAD AS?

BJARNE RAVN HUNSTAD is the largest registered owner, with 100.0%.

What is the revenue of INGENIØR RAVN HUNSTAD AS?

INGENIØR RAVN HUNSTAD AS had revenue of NOK 2.9m in 2025.

Who is the general manager of INGENIØR RAVN HUNSTAD AS?

Bjarne Ravn Hunstad is registered as general manager of INGENIØR RAVN HUNSTAD AS.

Where is INGENIØR RAVN HUNSTAD AS based?

INGENIØR RAVN HUNSTAD AS has its business address in Kabelvåg.

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.