BIZTRAC BETA
Computer programming activities

AWARENESS SECURITY AS

Org. no. 913224531 Limited company (AS) Nesodden Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 50,000
Operating profit NOK 4,000
Equity NOK 86,000
Incorporated 2014
Share capital NOK 30,000

AWARENESS SECURITY AS is registered as a limited company in Nesodden, Akershus with organisation number 913224531. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å sikkerhetsteste IT-systemer og å holde kurs, utvikle verktøy, samt annen virksomhet som er knyttet til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 50,000 in revenue and NOK 4,000 in operating profit.

Key figures · 2025

Revenue
NOK 50,000
Operating profit
NOK 4,000
Equity
NOK 86,000
Est. value
NOK 80,000

Financial health · 2025

Liquidity
10.58
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
90.5%
Weak
Equity as a share of total capital

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

Who owns AWARENESS SECURITY AS?

ASBJØRN REGLUND THORSEN
AWARENESS SECURITY AS
NOK 50,000 rev. · NOK 4,000 profit

AWARENESS SECURITY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AWARENESS SECURITY AS

Who owns AWARENESS SECURITY AS?

ASBJØRN REGLUND THORSEN is the largest registered owner, with 100.0%.

What is the revenue of AWARENESS SECURITY AS?

AWARENESS SECURITY AS had revenue of NOK 50,000 in 2025.

Who is the general manager of AWARENESS SECURITY AS?

Asbjørn Reglund Thorsen is registered as general manager of AWARENESS SECURITY AS.

Where is AWARENESS SECURITY AS based?

AWARENESS SECURITY AS has its business address in Nesodden.

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.