BIZTRAC BETA
Repair and maintenance of civilian ships and boats

SKJÆRHALDEN BÅTSENTER AS

Org. no. 927080109 Limited company (AS) Hvaler Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 467,000
Equity NOK 820,000
Incorporated 2021
Share capital NOK 30,000

SKJÆRHALDEN BÅTSENTER AS is registered as a limited company in Hvaler, Østfold with organisation number 927080109. The business is classified under repair and maintenance of civilian ships and boats (NACE 33.150). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Vinteropplag og klargjøring av båt. Enkel service på båtmotorer.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 467,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 467,000
Equity
NOK 820,000
Est. value
NOK 2.0m

Financial health · 2024

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

Who owns SKJÆRHALDEN BÅTSENTER AS?

MICHAEL EMIL TUNSLI LORENTZEN
SKJÆRHALDEN BÅTSENTER AS
NOK 2.0m rev. · NOK 467,000 profit

SKJÆRHALDEN BÅTSENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKJÆRHALDEN BÅTSENTER AS

Who owns SKJÆRHALDEN BÅTSENTER AS?

MICHAEL EMIL TUNSLI LORENTZEN is the largest registered owner, with 100.0%.

What is the revenue of SKJÆRHALDEN BÅTSENTER AS?

SKJÆRHALDEN BÅTSENTER AS had revenue of NOK 2.0m in 2024.

Who is the general manager of SKJÆRHALDEN BÅTSENTER AS?

Michael Emil Tunsli Lorentzen is registered as general manager of SKJÆRHALDEN BÅTSENTER AS.

Where is SKJÆRHALDEN BÅTSENTER AS based?

SKJÆRHALDEN BÅTSENTER AS has its business address in Skjærhalden.

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.