BIZTRAC BETA
COMPANY REGISTER PROFILE
889186402 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

HARTVEIT HOLDING AS

Org. no. 889186402 Limited company (AS) Bergen Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −110,000
Equity NOK 1.1m
Incorporated 2005
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−110k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HARTVEIT HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 889186402. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer i andre selskaper samt forvalte eierinteressene av disse. Selskapet skal også kunne forestå administrative tjenester for andre selskaper.”.

Key figures · 2025

Operating profit
NOK −110,000
Equity
NOK 1.1m
Est. value
NOK 4.2m

Financial health · 2025

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

Who owns HARTVEIT HOLDING AS?

ESPEN HARTVEIT
HARTVEIT HOLDING AS
· NOK −110,000 profit

HARTVEIT HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does HARTVEIT HOLDING AS own?

HARTVEIT HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HARTVEIT HOLDING AS

Who owns HARTVEIT HOLDING AS?

ESPEN HARTVEIT is the largest registered owner, with 45.0%.

Where is HARTVEIT HOLDING AS based?

HARTVEIT HOLDING 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.