biztrac. BETA
COMPANY REGISTER PROFILE
992812206 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and leasing of other machinery, equipment and tangible goods n.e.c.

GUNNAR HAUGE AS

Org. no. 992812206 Limited company (AS) Birkenes Incorporated 2008 Active
Revenue 2025 NOK 251,000
Operating profit NOK 94,000
Equity NOK 812,000
Incorporated 2008
Share capital NOK 100,000

GUNNAR HAUGE AS is registered as a limited company in Birkenes, Agder with organisation number 992812206. The business is classified under rental and leasing of other machinery, equipment and tangible goods n.e.c. (NACE 77.390). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av annet landtransportmateriell, utleie av bygninger, kjøp og salg av aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 251,000 in revenue and NOK 94,000 in operating profit.

Key figures · 2025

Revenue
NOK 251,000
▲ +2 %
Operating profit
NOK 94,000
▼ −36 %
Equity
NOK 812,000
▲ +2 %
Est. value
NOK 684,000

Financial health · 2025

Liquidity
0.89
Weak
Current assets ÷ current liabilities
Profitability
6.5%
Satisfactory
Return on total assets
Solidity
35.5%
Good
Equity as a share of total capital

Who owns GUNNAR HAUGE AS?

GUNNAR HAUGE AS
NOK 251,000 rev. · NOK 94,000 profit

GUNNAR HAUGE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GUNNAR HAUGE AS

Who owns GUNNAR HAUGE AS?

J. HÅKEDAL INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of GUNNAR HAUGE AS?

GUNNAR HAUGE AS had revenue of NOK 251,000 in 2025.

Who is the general manager of GUNNAR HAUGE AS?

Jarle Håkedal is registered as general manager of GUNNAR HAUGE AS.

Where is GUNNAR HAUGE AS based?

GUNNAR HAUGE AS has its business address in Birkeland.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.