biztrac. BETA
COMPANY REGISTER PROFILE
926403931 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other tour operator activities

LAJAMO INVEST AS

Org. no. 926403931 Limited company (AS) Askøy Incorporated 2021 Active
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 671,000
Incorporated 2021
Share capital NOK 100,000

Signals

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

LAJAMO INVEST AS is registered as a limited company in Askøy, Vestland with organisation number 926403931. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Erverve, eie og forvalte aksjer og andeler i andre selskaper samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
▼ −8 %
Equity
NOK 671,000
▲ +109 %
Est. value
NOK 3.1m

Financial health · 2025

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

Who owns LAJAMO INVEST AS?

LAJAMO INVEST AS
NOK 0 rev. · NOK −4,000 profit

LAJAMO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAJAMO INVEST AS

Who owns LAJAMO INVEST AS?

DUCK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LAJAMO INVEST AS?

LAJAMO INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of LAJAMO INVEST AS?

André Dyrøy is registered as general manager of LAJAMO INVEST AS.

Where is LAJAMO INVEST AS based?

LAJAMO INVEST AS has its business address in Florvåg.

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.