BIZTRAC BETA
Security activities n.e.c.

CORE SECURITY AS

Org. no. 912714756 Limited company (AS) Asker Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 19.6m
Operating profit NOK −31,000
Equity NOK 736,000
Incorporated 2013
Employees 15
Share capital NOK 100,000

Signals

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

CORE SECURITY AS is registered as a limited company in Asker, Akershus with organisation number 912714756. The business is classified under security activities n.e.c. (NACE 80.090). The company was incorporated in 2013 and has 15 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Ytelse av konsulenttjenster og salg og utleie av sikkerhetssystemer samt investering i aksjer og andre investeringsobjekter inklusive fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 19.6m in revenue and NOK −31,000 in operating profit.

Key figures · 2024

Revenue
NOK 19.6m
Operating profit
NOK −31,000
Equity
NOK 736,000
Est. value
NOK 9.8m

Financial health · 2024

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

Who owns CORE SECURITY AS?

SMILODON AS
CORE SECURITY AS
NOK 19.6m rev. · NOK −31,000 profit

CORE SECURITY AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about CORE SECURITY AS

Who owns CORE SECURITY AS?

SMILODON AS is the largest registered owner, with 45.0%.

What is the revenue of CORE SECURITY AS?

CORE SECURITY AS had revenue of NOK 19.6m in 2024.

Who is the general manager of CORE SECURITY AS?

Christopher Landmark Naas is registered as general manager of CORE SECURITY AS.

Where is CORE SECURITY AS based?

CORE SECURITY AS has its business address in Nesbru.

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.