BIZTRAC BETA
Restaurant activities

LEIF HOVLAND AS

Org. no. 989069993 Limited company (AS) Stavanger Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −124,000
Equity NOK 50.2m
Incorporated 2005
Share capital NOK 55,000

Signals

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

LEIF HOVLAND AS is registered as a limited company in Stavanger, Rogaland with organisation number 989069993. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2005. Registered share capital is NOK 55,000, divided into 1 shares. The company's stated purpose is: “Investering i verdipapirer, eiendom og annen investeringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −124,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −124,000
Equity
NOK 50.2m
Est. value
NOK 94.1m

Financial health · 2024

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

Who owns LEIF HOVLAND AS?

LEIF BIRGER HOVLAND
LEIF HOVLAND AS
NOK 0 rev. · NOK −124,000 profit

LEIF HOVLAND AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LEIF HOVLAND AS own?

LEIF HOVLAND AS holds stakes in 13 companies:

See the full ownership structure →

Frequently asked questions about LEIF HOVLAND AS

Who owns LEIF HOVLAND AS?

LEIF BIRGER HOVLAND is the largest registered owner, with 100.0%.

What is the revenue of LEIF HOVLAND AS?

LEIF HOVLAND AS had revenue of NOK 0 in 2024.

Where is LEIF HOVLAND AS based?

LEIF HOVLAND AS has its business address in Hafrsfjord.

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.