BIZTRAC BETA
COMPANY REGISTER PROFILE
933646076 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

LUNSOL AS

Org. no. 933646076 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −2,000
Equity NOK 98,000
Incorporated 2024
Share capital NOK 100,000

Signals

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

LUNSOL AS is registered as a limited company in Oslo, Oslo with organisation number 933646076. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i norske unoterte aksjeselskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 98,000
Est. value
NOK 115,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LUNSOL AS?

CHRISTOFFER LUND SOLLI
LUNSOL AS
NOK 0 rev. · NOK −2,000 profit

LUNSOL AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LUNSOL AS own?

LUNSOL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LUNSOL AS

Who owns LUNSOL AS?

CHRISTOFFER LUND SOLLI is the largest registered owner, with 50.0%.

What is the revenue of LUNSOL AS?

LUNSOL AS had revenue of NOK 0 in 2024.

Who is the general manager of LUNSOL AS?

Johan Mathias Lund Solli is registered as general manager of LUNSOL AS.

Where is LUNSOL AS based?

LUNSOL 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.