biztrac. BETA
COMPANY REGISTER PROFILE
934626699 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

EKSE HOLDING AS

Org. no. 934626699 Limited company (AS) Elverum Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −15,000
Equity NOK 3.0m
Incorporated 2024
Share capital NOK 287,000

Signals

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

EKSE HOLDING AS is registered as a limited company in Elverum, Innlandet with organisation number 934626699. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 287,000, divided into 100 shares. The company's stated purpose is: “Investering i næringsvirksomhet, herunder aksjer og andeler, samt deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −15,000
▼ −1446 %
Equity
NOK 3.0m
▲ +20 %
Est. value
NOK 8.2m

Financial health · 2025

Liquidity
129.99
Very good
Current assets ÷ current liabilities
Profitability
36.5%
Very good
Return on total assets
Solidity
99.6%
Very good
Equity as a share of total capital

Who owns EKSE HOLDING AS?

EKSE HOLDING AS
NOK 0 rev. · NOK −15,000 profit

EKSE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EKSE HOLDING AS own?

EKSE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EKSE HOLDING AS

Who owns EKSE HOLDING AS?

Anders Martin Ekse is the largest registered owner, with 100.0%.

What is the revenue of EKSE HOLDING AS?

EKSE HOLDING AS had revenue of NOK 0 in 2025.

Where is EKSE HOLDING AS based?

EKSE HOLDING AS has its business address in Elverum.

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.