BIZTRAC BETA
Other real estate activities on a fee or contract basis

HUSTADVIKA TAKST AS

Org. no. 929481224 Limited company (AS) Hustadvika Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 623,000
Operating profit NOK 43,000
Equity NOK 320,000
Incorporated 2022
Share capital NOK 30,000

HUSTADVIKA TAKST AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 929481224. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Taksering av eiendom, og annet som står i naturlig forbindelse med dette, herunder å delta i andre selskaper med slikt formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 623,000 in revenue and NOK 43,000 in operating profit.

Key figures · 2025

Revenue
NOK 623,000
Operating profit
NOK 43,000
Equity
NOK 320,000
Est. value
NOK 339,000

Financial health · 2025

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

Who owns HUSTADVIKA TAKST AS?

HELGE ROAR ÅNDAL
HUSTADVIKA TAKST AS
NOK 623,000 rev. · NOK 43,000 profit

HUSTADVIKA TAKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HUSTADVIKA TAKST AS

Who owns HUSTADVIKA TAKST AS?

HELGE ROAR ÅNDAL is the largest registered owner, with 100.0%.

What is the revenue of HUSTADVIKA TAKST AS?

HUSTADVIKA TAKST AS had revenue of NOK 623,000 in 2025.

Who is the general manager of HUSTADVIKA TAKST AS?

Helge Roar Åndal is registered as general manager of HUSTADVIKA TAKST AS.

Where is HUSTADVIKA TAKST AS based?

HUSTADVIKA TAKST AS has its business address in Malmefjorden.

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.