BIZTRAC BETA
Activities of agents involved in the wholesale of machinery, industrial equipment, ships and aircraft

LARKOLLEN BÅT AS

Org. no. 920491235 Limited company (AS) Moss Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 175,000
Operating profit NOK 74,000
Equity NOK 90,000
Incorporated 2018
Share capital NOK 30,000

LARKOLLEN BÅT AS is registered as a limited company in Moss, Østfold with organisation number 920491235. The business is classified under activities of agents involved in the wholesale of machinery, industrial equipment, ships and aircraft (NACE 46.140). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av båt, motor, bil og andre kjøretøy.”. The most recent filed accounts, for the 2024 financial year, show NOK 175,000 in revenue and NOK 74,000 in operating profit.

Key figures · 2024

Revenue
NOK 175,000
Operating profit
NOK 74,000
Equity
NOK 90,000
Est. value
NOK 296,000

Financial health · 2024

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

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

Who owns LARKOLLEN BÅT AS?

KENNETH ISAKSEN
LARKOLLEN BÅT AS
NOK 175,000 rev. · NOK 74,000 profit

LARKOLLEN BÅT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LARKOLLEN BÅT AS

Who owns LARKOLLEN BÅT AS?

KENNETH ISAKSEN is the largest registered owner, with 100.0%.

What is the revenue of LARKOLLEN BÅT AS?

LARKOLLEN BÅT AS had revenue of NOK 175,000 in 2024.

Who is the general manager of LARKOLLEN BÅT AS?

Kenneth Isaksen is registered as general manager of LARKOLLEN BÅT AS.

Where is LARKOLLEN BÅT AS based?

LARKOLLEN BÅT AS has its business address in Larkollen.

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.