BIZTRAC BETA
Repair and maintenance of civilian ships and boats

JOHANSEN SLIP EIENDOM AS

Org. no. 974371685 Limited company (AS) Kinn Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK 1.0m
Equity NOK 6.8m
Incorporated 1995
Share capital NOK 225,000

JOHANSEN SLIP EIENDOM AS is registered as a limited company in Kinn, Vestland with organisation number 974371685. The business is classified under repair and maintenance of civilian ships and boats (NACE 33.150). The company was incorporated in 1995. Registered share capital is NOK 225,000. The company's stated purpose is: “Eie og drive eiendommer og hva hermed står i forbindelse, herunder evt. å erverve aksjer/ andeler i lignende virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK 1.0m
Equity
NOK 6.8m
Est. value
NOK 6.0m

Financial health · 2024

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

Who owns JOHANSEN SLIP EIENDOM AS?

I. A. JOHANSEN HOLDING AS
JOHANSEN SLIP EIENDOM AS
NOK 2.3m rev. · NOK 1.0m profit

JOHANSEN SLIP EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Which companies does JOHANSEN SLIP EIENDOM AS own?

JOHANSEN SLIP EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JOHANSEN SLIP EIENDOM AS

Who owns JOHANSEN SLIP EIENDOM AS?

I. A. JOHANSEN HOLDING AS is the largest registered owner, with 42.7%.

What is the revenue of JOHANSEN SLIP EIENDOM AS?

JOHANSEN SLIP EIENDOM AS had revenue of NOK 2.3m in 2024.

Where is JOHANSEN SLIP EIENDOM AS based?

JOHANSEN SLIP EIENDOM AS has its business address in Raudeberg.

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.