BIZTRAC BETA
Investigation and private security activities

S O S SECURITY AS

Org. no. 988613525 Limited company (AS) Larvik Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK −9,000
Equity NOK 633,000
Incorporated 2005
Employees 6
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).

S O S SECURITY AS is registered as a limited company in Larvik, Vestfold with organisation number 988613525. The business is classified under investigation and private security activities (NACE 80.010). The company was incorporated in 2005 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Virksomhet innenfor alarm- og sikkerhetstjenster.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK −9,000
Equity
NOK 633,000
Est. value
NOK 401,000

Financial health · 2024

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

Who owns S O S SECURITY AS?

SKJOLD HOLDING AS
S O S SECURITY AS
NOK 1.4m rev. · NOK −9,000 profit

S O S SECURITY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about S O S SECURITY AS

Who owns S O S SECURITY AS?

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

What is the revenue of S O S SECURITY AS?

S O S SECURITY AS had revenue of NOK 1.4m in 2024.

Who is the general manager of S O S SECURITY AS?

Jon Sigurd Jacobsen is registered as general manager of S O S SECURITY AS.

Where is S O S SECURITY AS based?

S O S SECURITY AS has its business address in Larvik.

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.