BIZTRAC BETA
Repair and maintenance of machinery

DAHLS MARITIME SERVICE AS

Org. no. 998067782 Limited company (AS) Vågan Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 279,000
Equity NOK 1.3m
Incorporated 2012
Share capital NOK 30,000

DAHLS MARITIME SERVICE AS is registered as a limited company in Vågan, Nordland with organisation number 998067782. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg, reparasjon og vedlikehold av verktøy, maskiner, og motorer, med tilhørende virksomhet herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 279,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 279,000
Equity
NOK 1.3m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns DAHLS MARITIME SERVICE AS?

CHRISTOPHER DAHL
DAHLS MARITIME SERVICE AS
NOK 1.2m rev. · NOK 279,000 profit

DAHLS MARITIME SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DAHLS MARITIME SERVICE AS

Who owns DAHLS MARITIME SERVICE AS?

CHRISTOPHER DAHL is the largest registered owner, with 100.0%.

What is the revenue of DAHLS MARITIME SERVICE AS?

DAHLS MARITIME SERVICE AS had revenue of NOK 1.2m in 2025.

Who is the general manager of DAHLS MARITIME SERVICE AS?

Christopher Dahl is registered as general manager of DAHLS MARITIME SERVICE AS.

Where is DAHLS MARITIME SERVICE AS based?

DAHLS MARITIME SERVICE AS has its business address in Svolvær.

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.