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

TUVA STIFTELSEN

Org. no. 930750468 Foundation (STI) Bergen Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −405,000
Equity NOK 26.9m
Incorporated 2022
Share capital NOK 5.3m

Signals

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

TUVA STIFTELSEN is registered as a foundation in Bergen, Vestland with organisation number 930750468. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 2022. Registered share capital is NOK 5.3m.

Key figures · 2025

Operating profit
NOK −405,000
Equity
NOK 26.9m
Est. value
NOK 18.1m

Financial health · 2025

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

Who owns TUVA STIFTELSEN?

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

Which companies does TUVA STIFTELSEN own?

TUVA STIFTELSEN holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TUVA STIFTELSEN

Where is TUVA STIFTELSEN based?

TUVA STIFTELSEN has its business address in Nesttun.

Property

Business address c/o Paul Christian Rieber Skjoldvegen 76, 5221 Nesttun
Cadastral unit 4601-40/1439/0/0
Building Enebolig · 1 unit

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