BIZTRAC BETA
Other technical consultancy

NES MARITIME AS

Org. no. 911683423 Limited company (AS) Karmøy Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK −395,000
Equity NOK 352,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−395k kr).

NES MARITIME AS is registered as a limited company in Karmøy, Rogaland with organisation number 911683423. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å drive maritime konsulenttjenester innenfor oljeindustrien, aksje-og eiendomsforvaltning, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK −395,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK −395,000
Equity
NOK 352,000
Est. value
NOK 766,000

Financial health · 2025

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

Who owns NES MARITIME AS?

KARSTEN NES
NES MARITIME AS
NOK 1.4m rev. · NOK −395,000 profit

NES MARITIME AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NES MARITIME AS

Who owns NES MARITIME AS?

KARSTEN NES is the largest registered owner, with 100.0%.

What is the revenue of NES MARITIME AS?

NES MARITIME AS had revenue of NOK 1.4m in 2025.

Who is the general manager of NES MARITIME AS?

Karsten Nes is registered as general manager of NES MARITIME AS.

Where is NES MARITIME AS based?

NES MARITIME AS has its business address in Åkrehamn.

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.