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

GROSCH & TONSTADFONDET STI

Org. no. 980059790 Foundation (STI) Oslo Incorporated 1994 Active
Ownership graph ↗
Operating profit NOK −13,000
Equity NOK 981,000
Incorporated 1994
Share capital NOK 954,000

Signals

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

GROSCH & TONSTADFONDET STI is registered as a foundation in Oslo, Oslo with organisation number 980059790. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 1994. Registered share capital is NOK 954,000.

Key figures · 2025

Operating profit
NOK −13,000
Equity
NOK 981,000
Est. value
NOK 507,000

Financial health · 2025

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

Who owns GROSCH & TONSTADFONDET STI?

No shareholders are registered for GROSCH & TONSTADFONDET STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about GROSCH & TONSTADFONDET STI

Where is GROSCH & TONSTADFONDET STI based?

GROSCH & TONSTADFONDET STI has its business address in Oslo.

Property

Business address Nasjonalmuseet for kunst, arkitektur & design Brynjulf Bulls plass 3, 0250 Oslo
Cadastral unit 301-209/40/0/0
Building Museum, kunstgalleri · 5 units

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