biztrac. BETA
COMPANY REGISTER PROFILE
997831705 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of financing conduits

VALKYRIE INVEST AS

Org. no. 997831705 Limited company (AS) Oslo Incorporated 2012 Active
Revenue 2025 NOK 5.7m
Operating profit NOK 5.6m
Equity NOK 30.1m
Incorporated 2012
Share capital NOK 120,000

VALKYRIE INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 997831705. The business is classified under activities of financing conduits (NACE 64.220). The company was incorporated in 2012. Registered share capital is NOK 120,000, divided into 100 shares. The company's stated purpose is: “Investeringsvirksomhet innenfor noterte og unoterte verdipapirer, og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.7m in revenue and NOK 5.6m in operating profit.

Key figures · 2025

Revenue
NOK 5.7m
▲ +7625 %
Operating profit
NOK 5.6m
▲ +3727 %
Equity
NOK 30.1m
▲ +23 %
Est. value
NOK 27.9m

Financial health · 2025

Liquidity
266.46
Very good
Current assets ÷ current liabilities
Profitability
20.5%
Very good
Return on total assets
Solidity
99.7%
Very good
Equity as a share of total capital

Who owns VALKYRIE INVEST AS?

ÅGE HENRY LØNNING DK
VALKYRIE INVEST AS
NOK 5.7m rev. · NOK 5.6m profit

VALKYRIE INVEST AS has 1 registered shareholder:

  • ÅGE HENRY LØNNING 100.0%
All shareholders and roles →

Which companies does VALKYRIE INVEST AS own?

VALKYRIE INVEST AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about VALKYRIE INVEST AS

Who owns VALKYRIE INVEST AS?

ÅGE HENRY LØNNING is the largest registered owner, with 100.0%.

What is the revenue of VALKYRIE INVEST AS?

VALKYRIE INVEST AS had revenue of NOK 5.7m in 2025.

Where is VALKYRIE INVEST AS based?

VALKYRIE INVEST AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.