BIZTRAC BETA
Investigation and private security activities

LEGATUS AS

Org. no. 998636248 Limited company (AS) Våler Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 4,000
Incorporated 2012
Share capital NOK 30,000

LEGATUS AS is registered as a limited company in Våler, Innlandet with organisation number 998636248. The business is classified under investigation and private security activities (NACE 80.010). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utøve tjenester med fokus på sikkerhet og etterforskning. Selskapet skal sikre eiendeler og personer, samt drive oppsøkende virksomhet, utredning, avdekking, oppsporing og overvåking. En del psykiske, fysiske og logiske tjenester kan også tilbys med bl.a. tanke på IT.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 4,000
Est. value
NOK 72,000

Financial health · 2025

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

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

Who owns LEGATUS AS?

HÅVARD ELVBAKKEN
LEGATUS AS
NOK 0 rev. · NOK 0 profit

LEGATUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEGATUS AS

Who owns LEGATUS AS?

HÅVARD ELVBAKKEN is the largest registered owner, with 100.0%.

What is the revenue of LEGATUS AS?

LEGATUS AS had revenue of NOK 0 in 2025.

Who is the general manager of LEGATUS AS?

Håvard Elvbakken is registered as general manager of LEGATUS AS.

Where is LEGATUS AS based?

LEGATUS AS has its business address in Våler I Solør.

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.