BIZTRAC BETA
COMPANY REGISTER PROFILE
913185803 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Activities of charities which distribute means themselves

EILIF HOLTE LEGAT STI

Org. no. 913185803 Foundation (STI) Oslo Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −39,000
Equity NOK 2.7m
Incorporated 2012
Share capital NOK 1.5m

Signals

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

EILIF HOLTE LEGAT STI is registered as a foundation in Oslo, Oslo with organisation number 913185803. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 2012. Registered share capital is NOK 1.5m.

Key figures · 2025

Operating profit
NOK −39,000
Equity
NOK 2.7m
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns EILIF HOLTE LEGAT STI?

No shareholders are registered for EILIF HOLTE LEGAT STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about EILIF HOLTE LEGAT STI

Who is the general manager of EILIF HOLTE LEGAT STI?

Eilif Holte is registered as general manager of EILIF HOLTE LEGAT STI.

Where is EILIF HOLTE LEGAT STI based?

EILIF HOLTE LEGAT STI has its business address in Oslo.

Property

Business address Ullevålsveien 31, 0171 Oslo
Cadastral unit 301-208/768/0/0
Building Videregående skole · 2 units

17 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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