BIZTRAC BETA
Rental and operating of own or leased real estate

EYVIND HOLT AS

Org. no. 923653058 Limited company (AS) Bærum Incorporated 1973 Active
Ownership graph ↗
Revenue 2024 NOK 344,000
Operating profit NOK −524,000
Equity NOK 117.5m
Incorporated 1973
Share capital NOK 600,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−524k kr).

EYVIND HOLT AS is registered as a limited company in Bærum, Akershus with organisation number 923653058. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1973. Registered share capital is NOK 600,000, divided into 120000 shares. The company's stated purpose is: “Produksjon, handel og eiendoms- kjøp/salg og forvaltning.”. The most recent filed accounts, for the 2024 financial year, show NOK 344,000 in revenue and NOK −524,000 in operating profit.

Key figures · 2024

Revenue
NOK 344,000
Operating profit
NOK −524,000
Equity
NOK 117.5m
Est. value
NOK 81.0m

Financial health · 2024

Liquidity
1.66
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
97.5%
Very good
Equity as a share of total capital

Who owns EYVIND HOLT AS?

ULMI INVEST AS
EYVIND HOLT AS
NOK 344,000 rev. · NOK −524,000 profit

EYVIND HOLT AS has 3 registered shareholders:

All shareholders and roles →

Which companies does EYVIND HOLT AS own?

EYVIND HOLT AS holds stakes in 20 companies:

See the full ownership structure →

Group structure

EYVIND HOLT AS er morselskap for 1 datterselskap:

Frequently asked questions about EYVIND HOLT AS

Who owns EYVIND HOLT AS?

ULMI INVEST AS is the largest registered owner, with 33.3%.

What is the revenue of EYVIND HOLT AS?

EYVIND HOLT AS had revenue of NOK 344,000 in 2024.

Where is EYVIND HOLT AS based?

EYVIND HOLT AS has its business address in Blommenholm.

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.