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

KREFTING STIFTELSEN

Org. no. 830492232 Foundation (STI) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −1.5m
Equity NOK 2.6m
Incorporated 2022
Share capital NOK 100,000

Signals

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

KREFTING STIFTELSEN is registered as a foundation in Oslo, Oslo with organisation number 830492232. 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 100,000.

Key figures · 2025

Operating profit
NOK −1.5m
Equity
NOK 2.6m
Est. value
NOK 3.4m

Financial health · 2025

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

Who owns KREFTING STIFTELSEN?

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

Which companies does KREFTING STIFTELSEN own?

KREFTING STIFTELSEN holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KREFTING STIFTELSEN

Where is KREFTING STIFTELSEN based?

KREFTING STIFTELSEN has its business address in Oslo.

Property

Business address Fridtjof Nansens plass 4, 0160 Oslo
Cadastral unit 301-209/144/0/0

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