BIZTRAC BETA
Other passenger transport in coastal waters

GALEASEN LOYAL AS

Org. no. 916013736 Limited company (AS) Kinn Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK −686,000
Equity NOK 62,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−686k kr).

GALEASEN LOYAL AS is registered as a limited company in Kinn, Vestland with organisation number 916013736. The business is classified under other passenger transport in coastal waters (NACE 50.109). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Organisere og drive båtturer, seilopplæring og navigasjonsteknikk, samt annen aktivitet som hører innunder den maritime tradisjon, i tillegg til å kunne investere i andre selskaper med beslektet formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK −686,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK −686,000
Equity
NOK 62,000
Est. value
NOK 942,000

Financial health · 2024

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

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

Who owns GALEASEN LOYAL AS?

SAO INVEST AS
GALEASEN LOYAL AS
NOK 2.9m rev. · NOK −686,000 profit

GALEASEN LOYAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GALEASEN LOYAL AS

Who owns GALEASEN LOYAL AS?

SAO INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of GALEASEN LOYAL AS?

GALEASEN LOYAL AS had revenue of NOK 2.9m in 2024.

Where is GALEASEN LOYAL AS based?

GALEASEN LOYAL AS has its business address in Florø.

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.