BIZTRAC BETA
COMPANY REGISTER PROFILE
983414060 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Historical site and monument activities

RAGNHILD OG CLAUS HELBERGS STIFTELSE

Org. no. 983414060 Foundation (STI) Oslo Incorporated 2000 Active
Ownership graph ↗
Operating profit NOK −54,000
Equity NOK 1.3m
Incorporated 2000
Share capital NOK 342,000

Signals

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

RAGNHILD OG CLAUS HELBERGS STIFTELSE is registered as a foundation in Oslo, Oslo with organisation number 983414060. The business is classified under historical site and monument activities (NACE 91.220). The company was incorporated in 2000. Registered share capital is NOK 342,000.

Former names: CLAUS HELBERGS STIFTELSE

Key figures · 2025

Operating profit
NOK −54,000
Equity
NOK 1.3m
Est. value
NOK 650,000

Financial health · 2025

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

Who owns RAGNHILD OG CLAUS HELBERGS STIFTELSE?

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

Frequently asked questions about RAGNHILD OG CLAUS HELBERGS STIFTELSE

Where is RAGNHILD OG CLAUS HELBERGS STIFTELSE based?

RAGNHILD OG CLAUS HELBERGS STIFTELSE has its business address in Oslo.

Property

Business address c/o Den Norske Turistforening Youngstorget 1, 0181 Oslo
Cadastral unit 301-208/835/0/0

14 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.