BIZTRAC BETA
Security activities n.e.c.

K2 SECURITY AS

Org. no. 923311483 Limited company (AS) Ørland Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 826,000
Operating profit NOK 144,000
Equity NOK −205,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−205k kr).

K2 SECURITY AS is registered as a limited company in Ørland, Trøndelag with organisation number 923311483. The business is classified under security activities n.e.c. (NACE 80.090). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rådgivning, tjenester og produkter innen kommando, kontroll, overvåkning, alarm og dronetjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 826,000 in revenue and NOK 144,000 in operating profit.

Key figures · 2025

Revenue
NOK 826,000
Operating profit
NOK 144,000
Equity
NOK −205,000
Est. value
NOK 805,000

Financial health · 2025

Liquidity
0.35
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-75.5%
Weak
Equity as a share of total capital

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

Who owns K2 SECURITY AS?

TOR ERIK AUNE BRUNSVIK
K2 SECURITY AS
NOK 826,000 rev. · NOK 144,000 profit

K2 SECURITY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about K2 SECURITY AS

Who owns K2 SECURITY AS?

TOR ERIK AUNE BRUNSVIK is the largest registered owner, with 100.0%.

What is the revenue of K2 SECURITY AS?

K2 SECURITY AS had revenue of NOK 826,000 in 2025.

Who is the general manager of K2 SECURITY AS?

Tor Erik Aune Brunsvik is registered as general manager of K2 SECURITY AS.

Where is K2 SECURITY AS based?

K2 SECURITY AS has its business address in Brekstad.

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.