BIZTRAC BETA
Computer programming activities

SECURE PRACTICE AS

Org. no. 919420197 Limited company (AS) Trondheim Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 10.0m
Operating profit NOK 3.2m
Equity NOK 8.5m
Incorporated 2017
Employees 17
Share capital NOK 30,000

SECURE PRACTICE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 919420197. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2017 and has 17 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utvikling og salg av produkter og tjenester for sikker praksis gjennom samspill mellom IT, sikkerhet og folk.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.0m in revenue and NOK 3.2m in operating profit.

Key figures · 2024

Revenue
NOK 10.0m
Operating profit
NOK 3.2m
Equity
NOK 8.5m
Est. value
NOK 17.5m

Financial health · 2024

Liquidity
1.63
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
40.4%
Very good
Equity as a share of total capital

Who owns SECURE PRACTICE AS?

OPEGGEN HOLDING AS
SECURE PRACTICE AS
NOK 10.0m rev. · NOK 3.2m profit

SECURE PRACTICE AS has 3 registered shareholders:

All shareholders and roles →

Group structure

SECURE PRACTICE AS er morselskap for 1 datterselskap:

Frequently asked questions about SECURE PRACTICE AS

Who owns SECURE PRACTICE AS?

OPEGGEN HOLDING AS is the largest registered owner, with 96.0%.

What is the revenue of SECURE PRACTICE AS?

SECURE PRACTICE AS had revenue of NOK 10.0m in 2024.

Who is the general manager of SECURE PRACTICE AS?

Erlend Andreas Gjære is registered as general manager of SECURE PRACTICE AS.

Where is SECURE PRACTICE AS based?

SECURE PRACTICE AS has its business address in Trondheim.

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.