BIZTRAC BETA
COMPANY REGISTER PROFILE
922746141 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

LAKA AS

Org. no. 922746141 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −63,000
Equity NOK 754,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

LAKA AS is registered as a limited company in Oslo, Oslo with organisation number 922746141. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringer i andre selskaper og alt som står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −63,000
Equity
NOK 754,000
Est. value
NOK 593,000

Financial health · 2025

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

Who owns LAKA AS?

LAKA AS
· NOK −63,000 profit

LAKA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LAKA AS own?

LAKA AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about LAKA AS

Who owns LAKA AS?

KATJA IVARSON is the largest registered owner, with 100.0%.

Where is LAKA AS based?

LAKA AS has its business address in Oslo.

Property

Business address Graahbakken 10B, 0286 Oslo
Cadastral unit 301-2/1153/0/0
Building Tomannsbolig, vertikal · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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