biztrac. BETA
COMPANY REGISTER PROFILE
933774694 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Wholesale of other household goods

SJØ PROTECTION AS

Org. no. 933774694 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 54,000
Equity NOK 9,000
Incorporated 2024
Share capital NOK 30,000

SJØ PROTECTION AS is registered as a limited company in Oslo, Oslo with organisation number 933774694. The business is classified under wholesale of other household goods (NACE 46.490). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikle og selge beskyttelsesutstyr innen vannsport. Første produkt er en surfehjelm.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 54,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
▲ +4214 %
Operating profit
NOK 54,000
▲ +185 %
Equity
NOK 9,000
▲ +122 %
Est. value
NOK 258,000

Financial health · 2025

Liquidity
0.96
Weak
Current assets ÷ current liabilities
Profitability
16.6%
Very good
Return on total assets
Solidity
1.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SJØ PROTECTION AS?

SJØ PROTECTION AS
NOK 1.4m rev. · NOK 54,000 profit

SJØ PROTECTION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SJØ PROTECTION AS

Who owns SJØ PROTECTION AS?

KLINGENBERG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SJØ PROTECTION AS?

SJØ PROTECTION AS had revenue of NOK 1.4m in 2025.

Who is the general manager of SJØ PROTECTION AS?

Thomas Olav Klingenberg is registered as general manager of SJØ PROTECTION AS.

Where is SJØ PROTECTION AS based?

SJØ PROTECTION AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.