BIZTRAC BETA
Support services to forestry

HÅTVEIT AS

Org. no. 931183427 Limited company (AS) Kristiansand Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 25,000
Operating profit NOK −12,000
Equity NOK 191,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−12k kr).

HÅTVEIT AS is registered as a limited company in Kristiansand, Agder with organisation number 931183427. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Skogbruk, jordbruk, utleie av fast eiendom, bygg og anlegg. Selskapets virksomhet er også å arbeide innenfor andre produkter/tjenester som naturlig hører innunder samme spekter samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 25,000 in revenue and NOK −12,000 in operating profit.

Key figures · 2024

Revenue
NOK 25,000
Operating profit
NOK −12,000
Equity
NOK 191,000
Est. value
NOK 105,000

Financial health · 2024

Liquidity
-2.80
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
135.7%
Very good
Equity as a share of total capital

Who owns HÅTVEIT AS?

BERIT INGUNN ÅNENSEN
HÅTVEIT AS
NOK 25,000 rev. · NOK −12,000 profit

HÅTVEIT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HÅTVEIT AS

Who owns HÅTVEIT AS?

BERIT INGUNN ÅNENSEN is the largest registered owner, with 100.0%.

What is the revenue of HÅTVEIT AS?

HÅTVEIT AS had revenue of NOK 25,000 in 2024.

Who is the general manager of HÅTVEIT AS?

Berit Ingunn Ånensen is registered as general manager of HÅTVEIT AS.

Where is HÅTVEIT AS based?

HÅTVEIT AS has its business address in Kristiansand S.

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.