BIZTRAC BETA
Other captive investment companies

INVERSE AS

Org. no. 919417587 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 35,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).

INVERSE AS is registered as a limited company in Oslo, Oslo with organisation number 919417587. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder delta som eier, långiver og garantist i andre selskaper. Selskapet skal også kunne drive vanlig handelsvirksomhet, kjøp og salg av valuta og andre verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 35,000
Est. value
NOK 32,000

Financial health · 2025

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

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

Who owns INVERSE AS?

BJARTE SEBASTIAN HANSEN
INVERSE AS
NOK 0 rev. · NOK −14,000 profit

INVERSE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does INVERSE AS own?

INVERSE AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about INVERSE AS

Who owns INVERSE AS?

BJARTE SEBASTIAN HANSEN is the largest registered owner, with 100.0%.

What is the revenue of INVERSE AS?

INVERSE AS had revenue of NOK 0 in 2025.

Where is INVERSE AS based?

INVERSE 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 15.06.2026.

Report a problem

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