BIZTRAC BETA
COMPANY REGISTER PROFILE
823367902 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

LI-LI HOLDING AS

Org. no. 823367902 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 28,000
Operating profit NOK 28,000
Equity NOK 128,000
Incorporated 2019
Share capital NOK 113,000

LI-LI HOLDING AS is registered as a limited company in Asker, Akershus with organisation number 823367902. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 113,000, divided into 1000 shares. The company's stated purpose is: “Eie aksjer i ett eller flere selskaper, og forvalte avkastningen av disse.”. The most recent filed accounts, for the 2025 financial year, show NOK 28,000 in revenue and NOK 28,000 in operating profit.

Key figures · 2025

Revenue
NOK 28,000
Operating profit
NOK 28,000
Equity
NOK 128,000
Est. value
NOK 167,000

Financial health · 2025

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

Who owns LI-LI HOLDING AS?

PÅL EUGEN BERGET
LI-LI HOLDING AS
NOK 28,000 rev. · NOK 28,000 profit

LI-LI HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LI-LI HOLDING AS own?

LI-LI HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LI-LI HOLDING AS

Who owns LI-LI HOLDING AS?

PÅL EUGEN BERGET is the largest registered owner, with 100.0%.

What is the revenue of LI-LI HOLDING AS?

LI-LI HOLDING AS had revenue of NOK 28,000 in 2025.

Who is the general manager of LI-LI HOLDING AS?

Pål Eugen Berget is registered as general manager of LI-LI HOLDING AS.

Where is LI-LI HOLDING AS based?

LI-LI HOLDING AS has its business address in Nesøya.

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.