biztrac. BETA
COMPANY REGISTER PROFILE
935428300 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

LASKA INVEST AS

Org. no. 935428300 Limited company (AS) Oslo Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK −17
Equity NOK 50,000
Incorporated 2025
Share capital NOK 50,000

Signals

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

LASKA INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 935428300. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Investeringer i aksjer og andeler, deltakelse og konsulentvirksomhet knyttet til selskapets investeringer og interesser.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −17 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −17
Equity
NOK 50,000
Est. value
NOK 59,000

Financial health · 2025

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

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

Who owns LASKA INVEST AS?

LASKA INVEST AS
NOK 0 rev. · NOK −17 profit

LASKA INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LASKA INVEST AS

Who owns LASKA INVEST AS?

Christopher Adam Laska is the largest registered owner, with 100.0%.

What is the revenue of LASKA INVEST AS?

LASKA INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of LASKA INVEST AS?

Christopher Adam Laska is registered as general manager of LASKA INVEST AS.

Where is LASKA INVEST AS based?

LASKA 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 03.10.2026.

Report a problem

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