biztrac. BETA
COMPANY REGISTER PROFILE
931162098 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Compulsory dissolution UPDATED 03.10.2026
⚠NNS NORGES NASJONALE SIKKERHETSTJENESTE AS is registered as “Compulsory dissolution” with the Brønnøysund Register Centre.
Investigation and private security activities

NNS NORGES NASJONALE SIKKERHETSTJENESTE AS

Org. no. 931162098 Limited company (AS) Oslo Incorporated 2023 Compulsory dissolution
Equity NOK 30,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Tvangsoppløsning Selskapet er under tvangsoppløsning.

NNS NORGES NASJONALE SIKKERHETSTJENESTE AS is registered as a limited company in Oslo, Oslo with organisation number 931162098. The business is classified under investigation and private security activities (NACE 80.010). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Vakt og sikring.”.

Key figures · 2024

Equity
NOK 30,000
▲ +0 %

Financial health · 2024

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns NNS NORGES NASJONALE SIKKERHETSTJENESTE AS?

NNS NORGES NASJONALE SIKKERHETSTJENESTE AS

NNS NORGES NASJONALE SIKKERHETSTJENESTE AS has 1 registered shareholder:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Frequently asked questions about NNS NORGES NASJONALE SIKKERHETSTJENESTE AS

Who owns NNS NORGES NASJONALE SIKKERHETSTJENESTE AS?

Lee Frivold is the largest registered owner, with 100.0%.

Where is NNS NORGES NASJONALE SIKKERHETSTJENESTE AS based?

NNS NORGES NASJONALE SIKKERHETSTJENESTE 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.