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

KL1 INVEST AS

Org. no. 932882175 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 50,000
Operating profit NOK 25,000
Equity NOK −259,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−259k kr).

KL1 INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 932882175. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av finansielle instrumenter, eiendom og det som naturlig tilfaller dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 50,000 in revenue and NOK 25,000 in operating profit.

Key figures · 2025

Revenue
NOK 50,000
Operating profit
NOK 25,000
Equity
NOK −259,000
Est. value
NOK 113,000

Financial health · 2025

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

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

Who owns KL1 INVEST AS?

KIM-ALEXANDER LAM
KL1 INVEST AS
NOK 50,000 rev. · NOK 25,000 profit

KL1 INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KL1 INVEST AS own?

KL1 INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KL1 INVEST AS

Who owns KL1 INVEST AS?

KIM-ALEXANDER LAM is the largest registered owner, with 100.0%.

What is the revenue of KL1 INVEST AS?

KL1 INVEST AS had revenue of NOK 50,000 in 2025.

Where is KL1 INVEST AS based?

KL1 INVEST 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.