BIZTRAC BETA
Retail sale of pleasure boats and equipment

GRIDSVÅG BÅT MOTOR AS

Org. no. 984413793 Limited company (AS) Aure Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 23.8m
Operating profit NOK 968,000
Equity NOK 4.7m
Incorporated 2002
Employees 12
Share capital NOK 100,000

GRIDSVÅG BÅT MOTOR AS is registered as a limited company in Aure, Møre og Romsdal with organisation number 984413793. The business is classified under retail sale of pleasure boats and equipment (NACE 47.632). The company was incorporated in 2002 and has 12 registered employees. Registered share capital is NOK 100,000, divided into 10 shares. The company's stated purpose is: “Salg, rep, service, import, export, av båter, biler og alt som står i forbindelse med dette. Samt delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 23.8m in revenue and NOK 968,000 in operating profit.

Key figures · 2024

Revenue
NOK 23.8m
Operating profit
NOK 968,000
Equity
NOK 4.7m
Est. value
NOK 5.4m

Financial health · 2024

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.2%
Good
Equity as a share of total capital

Who owns GRIDSVÅG BÅT MOTOR AS?

LARS EINAR GRIDSVÅG
GRIDSVÅG BÅT MOTOR AS
NOK 23.8m rev. · NOK 968,000 profit

GRIDSVÅG BÅT MOTOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRIDSVÅG BÅT MOTOR AS

Who owns GRIDSVÅG BÅT MOTOR AS?

LARS EINAR GRIDSVÅG is the largest registered owner, with 100.0%.

What is the revenue of GRIDSVÅG BÅT MOTOR AS?

GRIDSVÅG BÅT MOTOR AS had revenue of NOK 23.8m in 2024.

Who is the general manager of GRIDSVÅG BÅT MOTOR AS?

Lars Einar Gridsvåg is registered as general manager of GRIDSVÅG BÅT MOTOR AS.

Where is GRIDSVÅG BÅT MOTOR AS based?

GRIDSVÅG BÅT MOTOR AS has its business address in Lesund.

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.