biztrac. BETA
COMPANY REGISTER PROFILE
932140225 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Supply and other sea transport offshore services

VEGA MARINE AS

Org. no. 932140225 Limited company (AS) Asker Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −2,000
Equity NOK 42,000
Incorporated 2023
Share capital NOK 50,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VEGA MARINE AS is registered as a limited company in Asker, Akershus with organisation number 932140225. The business is classified under supply and other sea transport offshore services (NACE 50.203). The company was incorporated in 2023. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Eie, utleie, drift av båter, fartøy og passasjerskip, rederivirksomhet, entreprenørvirksomhet, vedlikehold av båter. Prosjektdeltakelse i andre selskaper og investering eiendom.”.

Key figures · 2025

Operating profit
NOK −2,000
▲ +47 %
Equity
NOK 42,000
▼ −8 %
Est. value
NOK 45,000

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.0%
Not satisfactory
Return on total assets
Solidity
0.9%
Weak
Equity as a share of total capital

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

Who owns VEGA MARINE AS?

VEGA MARINE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VEGA MARINE AS own?

VEGA MARINE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VEGA MARINE AS

Who owns VEGA MARINE AS?

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

Where is VEGA MARINE AS based?

VEGA MARINE 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.