BIZTRAC BETA
Non-specialised wholesale trade

EXTON INVEST AS

Org. no. 926051318 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK −597
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−597 kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

EXTON INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 926051318. The business is classified under non-specialised wholesale trade (NACE 46.900). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringer og deltagelse i andre selskaper, forretningsmessig tjenesteyting og handel med aksjer og verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK −597

Financial health · 2025

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

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

Who owns EXTON INVEST AS?

REXTOR AS
EXTON INVEST AS
NOK 0 rev. · NOK −6,000 profit

EXTON INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EXTON INVEST AS

Who owns EXTON INVEST AS?

REXTOR AS is the largest registered owner, with 70.0%.

What is the revenue of EXTON INVEST AS?

EXTON INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of EXTON INVEST AS?

Mikael Arne Ekblom is registered as general manager of EXTON INVEST AS.

Where is EXTON INVEST AS based?

EXTON INVEST AS has its business address in Bekkestua.

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.