biztrac. BETA
COMPANY REGISTER PROFILE
933487458 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Investigation and private security activities

AK SIKKERHET AS

Org. no. 933487458 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 194,000
Operating profit NOK 34,000
Equity NOK 39,000
Incorporated 2024
Share capital NOK 30,000

AK SIKKERHET AS is registered as a limited company in Oslo, Oslo with organisation number 933487458. The business is classified under investigation and private security activities (NACE 80.010). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Sikkerhet - sikkerhetstjeneste - vaktholdtjeneste - vektertjenester - overvåkning.”. The most recent filed accounts, for the 2025 financial year, show NOK 194,000 in revenue and NOK 34,000 in operating profit.

Key figures · 2025

Revenue
NOK 194,000
▲ +0 %
Operating profit
NOK 34,000
▲ +0 %
Equity
NOK 39,000
▲ +1559 %
Est. value
NOK 100,000

Financial health · 2025

Liquidity
1.38
Satisfactory
Current assets ÷ current liabilities
Profitability
23.5%
Very good
Return on total assets
Solidity
15.7%
Weak
Equity as a share of total capital

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

Who owns AK SIKKERHET AS?

AK SIKKERHET AS
NOK 194,000 rev. · NOK 34,000 profit

AK SIKKERHET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AK SIKKERHET AS

Who owns AK SIKKERHET AS?

Muneeb Ahmad is the largest registered owner, with 50.0%.

What is the revenue of AK SIKKERHET AS?

AK SIKKERHET AS had revenue of NOK 194,000 in 2025.

Who is the general manager of AK SIKKERHET AS?

Muneeb Ahmad is registered as general manager of AK SIKKERHET AS.

Where is AK SIKKERHET AS based?

AK 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 03.10.2026.

Report a problem

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