biztrac. BETA
COMPANY REGISTER PROFILE
911969874 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

LILLEVIK HOLDING AS

Org. no. 911969874 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 7,000
Operating profit NOK −91,000
Equity NOK 16.1m
Incorporated 2013
Share capital NOK 150,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−91k kr).

LILLEVIK HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 911969874. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2013. Registered share capital is NOK 150,000, divided into 50000 shares. The company's stated purpose is: “Investeringsvirksomhet og hva som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 7,000 in revenue and NOK −91,000 in operating profit.

Key figures · 2025

Revenue
NOK 7,000
Operating profit
NOK −91,000
▲ +24 %
Equity
NOK 16.1m
▼ −4 %
Est. value
NOK 12.6m

Financial health · 2025

Liquidity
318.56
Very good
Current assets ÷ current liabilities
Profitability
7.5%
Satisfactory
Return on total assets
Solidity
99.7%
Very good
Equity as a share of total capital

Who owns LILLEVIK HOLDING AS?

LILLEVIK HOLDING AS
NOK 7,000 rev. · NOK −91,000 profit

LILLEVIK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LILLEVIK HOLDING AS own?

LILLEVIK HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about LILLEVIK HOLDING AS

Who owns LILLEVIK HOLDING AS?

Håvard Lillevik is the largest registered owner, with 100.0%.

What is the revenue of LILLEVIK HOLDING AS?

LILLEVIK HOLDING AS had revenue of NOK 7,000 in 2025.

Where is LILLEVIK HOLDING AS based?

LILLEVIK HOLDING AS has its business address in Oslo.

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.