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

FONDET FOR KARKIRURGISK FORSKNING STI

Org. no. 957559468 Foundation (STI) Trondheim Incorporated 1989 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK 401,000
Incorporated 1989
Share capital NOK 323,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).

FONDET FOR KARKIRURGISK FORSKNING STI is registered as a foundation in Trondheim, Trøndelag with organisation number 957559468. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 1989. Registered share capital is NOK 323,000.

Key figures · 2024

Operating profit
NOK −9,000
Equity
NOK 401,000
Est. value
NOK 222,000

Financial health · 2024

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 FONDET FOR KARKIRURGISK FORSKNING STI?

No shareholders are registered for FONDET FOR KARKIRURGISK FORSKNING STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about FONDET FOR KARKIRURGISK FORSKNING STI

Where is FONDET FOR KARKIRURGISK FORSKNING STI based?

FONDET FOR KARKIRURGISK FORSKNING STI has its business address in Trondheim.

Property

Business address c/o Torbjørn Dahl Oscar Wistings vei 60C, 7020 Trondheim
Cadastral unit 5001-422/196/0/0
Building Rekkehus · 1 unit

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.