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

EVENRUDS STIFTELSE

Org. no. 983494129 Foundation (STI) Oslo Incorporated 2000 Active
Ownership graph ↗
Operating profit NOK −1.1m
Equity NOK 29.2m
Incorporated 2000
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,1 mill kr).

EVENRUDS STIFTELSE is registered as a foundation in Oslo, Oslo with organisation number 983494129. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 2000. Registered share capital is NOK 100,000.

Key figures · 2025

Operating profit
NOK −1.1m
Equity
NOK 29.2m
Est. value
NOK 30.5m

Financial health · 2025

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

Who owns EVENRUDS STIFTELSE?

No shareholders are registered for EVENRUDS STIFTELSE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about EVENRUDS STIFTELSE

Who is the general manager of EVENRUDS STIFTELSE?

Arne Jensen is registered as general manager of EVENRUDS STIFTELSE.

Where is EVENRUDS STIFTELSE based?

EVENRUDS STIFTELSE has its business address in Oslo.

Property

Business address Karvesvingen 1, 0579 Oslo
Cadastral unit 301-124/241/0/0
Building Annen kontorbygning · 1 unit

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.