BIZTRAC BETA
Marine fishing

GALAASEN AS

Org. no. 928031640 Limited company (AS) Sør-Varanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 417,000
Operating profit NOK −302,000
Equity NOK −357,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−357k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−302k kr).

GALAASEN AS is registered as a limited company in Sør-Varanger, Finnmark with organisation number 928031640. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Fiske i åpen kvote, kjøp og salg av diverse varer, agentur av båter.”. The most recent filed accounts, for the 2024 financial year, show NOK 417,000 in revenue and NOK −302,000 in operating profit.

Key figures · 2024

Revenue
NOK 417,000
Operating profit
NOK −302,000
Equity
NOK −357,000

Financial health · 2024

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

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

Who owns GALAASEN AS?

MATHIAS INGLEBERG RØTVOLD GALAASEN
GALAASEN AS
NOK 417,000 rev. · NOK −302,000 profit

GALAASEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GALAASEN AS

Who owns GALAASEN AS?

MATHIAS INGLEBERG RØTVOLD GALAASEN is the largest registered owner, with 100.0%.

What is the revenue of GALAASEN AS?

GALAASEN AS had revenue of NOK 417,000 in 2024.

Who is the general manager of GALAASEN AS?

Mathias Ingleberg Røtvold Galaasen is registered as general manager of GALAASEN AS.

Where is GALAASEN AS based?

GALAASEN AS has its business address in Kirkenes.

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.