BIZTRAC BETA
COMPANY REGISTER PROFILE
883391462 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Scheduled long distance passenger transport in coastal waters

MOSKENES SHIPPING AS

Org. no. 883391462 Limited company (AS) Moskenes Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 8.1m
Operating profit NOK 214,000
Equity NOK 2.9m
Incorporated 2001
Employees 9
Share capital NOK 100,000

MOSKENES SHIPPING AS is registered as a limited company in Moskenes, Nordland with organisation number 883391462. The business is classified under scheduled long distance passenger transport in coastal waters (NACE 50.102). The company was incorporated in 2001 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Rederiverksemd og handel, tjenesteytelse og eiendomsbesittelse forutan anna verksemd som naturleg fell inn.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.1m in revenue and NOK 214,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.1m
▲ +3 %
Operating profit
NOK 214,000
▼ −92 %
Equity
NOK 2.9m
▼ −37 %
Est. value
NOK 4.4m

Financial health · 2025

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

Who owns MOSKENES SHIPPING AS?

MOSKENES SHIPPING AS
NOK 8.1m rev. · NOK 214,000 profit

MOSKENES SHIPPING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MOSKENES SHIPPING AS

Who owns MOSKENES SHIPPING AS?

RASMUS JOHANNES KIBSGÅRD is the largest registered owner, with 78.0%.

What is the revenue of MOSKENES SHIPPING AS?

MOSKENES SHIPPING AS had revenue of NOK 8.1m in 2025.

Where is MOSKENES SHIPPING AS based?

MOSKENES SHIPPING AS has its business address in Sørvågen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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