BIZTRAC BETA
Support services to forestry

AH TEKNIKK AS

Org. no. 833376322 Limited company (AS) Ullensvang Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 343,000
Operating profit NOK −16,000
Equity NOK −20,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−20k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−16k kr).

AH TEKNIKK AS is registered as a limited company in Ullensvang, Vestland with organisation number 833376322. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Skogstjenester, vedsalg og brøyting. Transport og utleie av maskiner. Elektrikertjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 343,000 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 343,000
Operating profit
NOK −16,000
Equity
NOK −20,000

Financial health · 2025

Liquidity
0.32
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-2.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns AH TEKNIKK AS?

ARVE HAGEN
AH TEKNIKK AS
NOK 343,000 rev. · NOK −16,000 profit

AH TEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AH TEKNIKK AS

Who owns AH TEKNIKK AS?

ARVE HAGEN is the largest registered owner, with 100.0%.

What is the revenue of AH TEKNIKK AS?

AH TEKNIKK AS had revenue of NOK 343,000 in 2025.

Who is the general manager of AH TEKNIKK AS?

Arve Hagen is registered as general manager of AH TEKNIKK AS.

Where is AH TEKNIKK AS based?

AH TEKNIKK AS has its business address in Røldal.

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.