BIZTRAC BETA
Supply and other sea transport offshore services

SPESIALFARTØY AS

Org. no. 993947520 Limited company (AS) Bokn Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 9.3m
Operating profit NOK 727,000
Equity NOK 19.4m
Incorporated 2009
Share capital NOK 1.2m

SPESIALFARTØY AS is registered as a limited company in Bokn, Rogaland with organisation number 993947520. The business is classified under supply and other sea transport offshore services (NACE 50.203). The company was incorporated in 2009. Registered share capital is NOK 1.2m, divided into 1000 shares. The company's stated purpose is: “Eie og drive arbeidsbåt/slepebåt, utføre reparasjon og konsulenttjenester, samt deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.3m in revenue and NOK 727,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.3m
Operating profit
NOK 727,000
Equity
NOK 19.4m
Est. value
NOK 13.3m

Financial health · 2025

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

Who owns SPESIALFARTØY AS?

EINAR VÅGE
SPESIALFARTØY AS
NOK 9.3m rev. · NOK 727,000 profit

SPESIALFARTØY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SPESIALFARTØY AS own?

SPESIALFARTØY AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SPESIALFARTØY AS

Who owns SPESIALFARTØY AS?

EINAR VÅGE is the largest registered owner, with 100.0%.

What is the revenue of SPESIALFARTØY AS?

SPESIALFARTØY AS had revenue of NOK 9.3m in 2025.

Who is the general manager of SPESIALFARTØY AS?

Einar Våge is registered as general manager of SPESIALFARTØY AS.

Where is SPESIALFARTØY AS based?

SPESIALFARTØY AS has its business address in Bokn.

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.