BIZTRAC BETA
Investigation and private security activities

TRYGG SIKKERHET AS

Org. no. 828824082 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −48,000
Equity NOK 64,000
Incorporated 2022
Employees 7
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−48k kr).

TRYGG SIKKERHET AS is registered as a limited company in Oslo, Oslo with organisation number 828824082. The business is classified under investigation and private security activities (NACE 80.010). The company was incorporated in 2022 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Vaktvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −48,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −48,000
Equity
NOK 64,000
Est. value
NOK 744,000

Financial health · 2025

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

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

Who owns TRYGG SIKKERHET AS?

MERSAD RIZVANOVIC
TRYGG SIKKERHET AS
NOK 1.1m rev. · NOK −48,000 profit

TRYGG SIKKERHET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRYGG SIKKERHET AS

Who owns TRYGG SIKKERHET AS?

MERSAD RIZVANOVIC is the largest registered owner, with 100.0%.

What is the revenue of TRYGG SIKKERHET AS?

TRYGG SIKKERHET AS had revenue of NOK 1.1m in 2025.

Who is the general manager of TRYGG SIKKERHET AS?

Enver Rizvanovic is registered as general manager of TRYGG SIKKERHET AS.

Where is TRYGG SIKKERHET AS based?

TRYGG SIKKERHET 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 15.06.2026.

Report a problem

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