BIZTRAC BETA
Silviculture and other forestry activities

HUSTADVIKA SKOGRYDDING AS

Org. no. 923133631 Limited company (AS) Hustadvika Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 5.3m
Operating profit NOK 753,000
Equity NOK 1.1m
Incorporated 2019
Employees 6
Share capital NOK 30,000

HUSTADVIKA SKOGRYDDING AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 923133631. The business is classified under silviculture and other forestry activities (NACE 02.100). The company was incorporated in 2019 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Skogrydding og tjenester tilknyttet skogbruk, som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.3m in revenue and NOK 753,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.3m
Operating profit
NOK 753,000
Equity
NOK 1.1m
Est. value
NOK 3.1m

Financial health · 2025

Liquidity
1.38
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
52.1%
Very good
Equity as a share of total capital

Who owns HUSTADVIKA SKOGRYDDING AS?

IVER BREVIK
HUSTADVIKA SKOGRYDDING AS
NOK 5.3m rev. · NOK 753,000 profit

HUSTADVIKA SKOGRYDDING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HUSTADVIKA SKOGRYDDING AS

Who owns HUSTADVIKA SKOGRYDDING AS?

IVER BREVIK is the largest registered owner, with 50.0%.

What is the revenue of HUSTADVIKA SKOGRYDDING AS?

HUSTADVIKA SKOGRYDDING AS had revenue of NOK 5.3m in 2025.

Who is the general manager of HUSTADVIKA SKOGRYDDING AS?

Iver Brevik is registered as general manager of HUSTADVIKA SKOGRYDDING AS.

Where is HUSTADVIKA SKOGRYDDING AS based?

HUSTADVIKA SKOGRYDDING AS has its business address in Vevang.

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.