BIZTRAC BETA
Repair and maintenance of civilian ships and boats

NAUSTVIK SLIPP & BÅTBYGGERI AS

Org. no. 915047653 Limited company (AS) Stavanger Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 299,000
Equity NOK 211,000
Incorporated 2015
Share capital NOK 30,000

NAUSTVIK SLIPP & BÅTBYGGERI AS is registered as a limited company in Stavanger, Rogaland with organisation number 915047653. The business is classified under repair and maintenance of civilian ships and boats (NACE 33.150). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Slipp og båtbyggeri.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 299,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 299,000
Equity
NOK 211,000
Est. value
NOK 1.0m

Financial health · 2024

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

Who owns NAUSTVIK SLIPP & BÅTBYGGERI AS?

JACOB HUNSBETH
NAUSTVIK SLIPP & BÅTBYGGERI AS
NOK 1.2m rev. · NOK 299,000 profit

NAUSTVIK SLIPP & BÅTBYGGERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NAUSTVIK SLIPP & BÅTBYGGERI AS

Who owns NAUSTVIK SLIPP & BÅTBYGGERI AS?

JACOB HUNSBETH is the largest registered owner, with 100.0%.

What is the revenue of NAUSTVIK SLIPP & BÅTBYGGERI AS?

NAUSTVIK SLIPP & BÅTBYGGERI AS had revenue of NOK 1.2m in 2024.

Who is the general manager of NAUSTVIK SLIPP & BÅTBYGGERI AS?

Jacob Hunsbeth is registered as general manager of NAUSTVIK SLIPP & BÅTBYGGERI AS.

Where is NAUSTVIK SLIPP & BÅTBYGGERI AS based?

NAUSTVIK SLIPP & BÅTBYGGERI AS has its business address in Hundvåg.

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.