BIZTRAC BETA
Electrical installation

SAFE AT SEA AS

Org. no. 818871082 Limited company (AS) Øygarden Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 6.7m
Operating profit NOK 2.0m
Equity NOK 1.7m
Incorporated 2017
Share capital NOK 30,000

SAFE AT SEA AS is registered as a limited company in Øygarden, Vestland with organisation number 818871082. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Fremstilling/salg av brannsikringstjenester og utstyr og andre produkter som naturlig faller sammen med dette, samt utleie av arbeidskraft. herunder og delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.7m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 6.7m
Operating profit
NOK 2.0m
Equity
NOK 1.7m
Est. value
NOK 6.8m

Financial health · 2024

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

Who owns SAFE AT SEA AS?

KAI EDVARD HALDORSEN
SAFE AT SEA AS
NOK 6.7m rev. · NOK 2.0m profit

SAFE AT SEA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SAFE AT SEA AS

Who owns SAFE AT SEA AS?

KAI EDVARD HALDORSEN is the largest registered owner, with 90.0%.

What is the revenue of SAFE AT SEA AS?

SAFE AT SEA AS had revenue of NOK 6.7m in 2024.

Who is the general manager of SAFE AT SEA AS?

Kai Edvard Haldorsen is registered as general manager of SAFE AT SEA AS.

Where is SAFE AT SEA AS based?

SAFE AT SEA AS has its business address in Glesvær.

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.