BIZTRAC BETA
Activities of psychiatrists

ERIK R. HAUGE AS

Org. no. 998889898 Limited company (AS) Bergen Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 226,000
Operating profit NOK −25,000
Equity NOK 9.3m
Incorporated 2012
Share capital NOK 30,000

Signals

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

ERIK R. HAUGE AS is registered as a limited company in Bergen, Vestland with organisation number 998889898. The business is classified under activities of psychiatrists (NACE 86.222). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Sakkyndigoppdrag, undervisningsoppdrag og konsulenttjenester innen ulike medisinske fagfelt, samt annen relatert virksomhet. ”. The most recent filed accounts, for the 2024 financial year, show NOK 226,000 in revenue and NOK −25,000 in operating profit.

Key figures · 2024

Revenue
NOK 226,000
Operating profit
NOK −25,000
Equity
NOK 9.3m
Est. value
NOK 20.7m

Financial health · 2024

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

Who owns ERIK R. HAUGE AS?

LEIF ERIK RØNNEBERG HAUGE
ERIK R. HAUGE AS
NOK 226,000 rev. · NOK −25,000 profit

ERIK R. HAUGE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ERIK R. HAUGE AS

Who owns ERIK R. HAUGE AS?

LEIF ERIK RØNNEBERG HAUGE is the largest registered owner, with 70.0%.

What is the revenue of ERIK R. HAUGE AS?

ERIK R. HAUGE AS had revenue of NOK 226,000 in 2024.

Who is the general manager of ERIK R. HAUGE AS?

Leif Erik Rønneberg Hauge is registered as general manager of ERIK R. HAUGE AS.

Where is ERIK R. HAUGE AS based?

ERIK R. HAUGE AS has its business address in Bergen.

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.