BIZTRAC BETA
Other passenger transport in coastal waters

VEGA SAILING AS

Org. no. 988970808 Limited company (AS) Asker Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 7.8m
Operating profit NOK 532,000
Equity NOK 3.0m
Incorporated 2005
Employees 13
Share capital NOK 100,000

VEGA SAILING AS is registered as a limited company in Asker, Akershus with organisation number 988970808. The business is classified under other passenger transport in coastal waters (NACE 50.109). The company was incorporated in 2005 and has 13 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er utleie, drift, bygging, vedlikehold av båter, fartøy og passasjerskip, rederivirksomhet, entreprenørvirksomhet, transport og dykking, kjøp/salg av utstyr, konsulentvirksomhet, prosjektledelse i andre selskaper og investeringer i verdipapirer, eiendom samt deltagelse i virksomhet med samme formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.8m in revenue and NOK 532,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.8m
Operating profit
NOK 532,000
Equity
NOK 3.0m
Est. value
NOK 3.3m

Financial health · 2024

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

Who owns VEGA SAILING AS?

VEGA NORDEN AS
VEGA SAILING AS
NOK 7.8m rev. · NOK 532,000 profit

VEGA SAILING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VEGA SAILING AS

Who owns VEGA SAILING AS?

VEGA NORDEN AS is the largest registered owner, with 100.0%.

What is the revenue of VEGA SAILING AS?

VEGA SAILING AS had revenue of NOK 7.8m in 2024.

Where is VEGA SAILING AS based?

VEGA SAILING AS has its business address in Båtstø.

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.