biztrac. BETA
COMPANY REGISTER PROFILE
992355352 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of charities which distribute means themselves

OVERLEGE ULFERT LIED, OVERLEGE KNUD NICOLAYSEN OG OLAF RØMCKES MINNEFOND FOR DRAMMEN SYKEHUS STI

Org. no. 992355352 Foundation (STI) Drammen Incorporated 2004 Active
Operating profit NOK −29,000
Equity NOK 1.2m
Incorporated 2004
Share capital NOK 996,000

Signals

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

OVERLEGE ULFERT LIED, OVERLEGE KNUD NICOLAYSEN OG OLAF RØMCKES MINNEFOND FOR DRAMMEN SYKEHUS STI is registered as a foundation in Drammen, Buskerud with organisation number 992355352. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 2004. Registered share capital is NOK 996,000.

Key figures · 2025

Operating profit
NOK −29,000
▼ −3 %
Equity
NOK 1.2m
Est. value
NOK 955,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 OVERLEGE ULFERT LIED, OVERLEGE KNUD NICOLAYSEN OG OLAF RØMCKES MINNEFOND FOR DRAMMEN SYKEHUS STI?

No shareholders are registered for OVERLEGE ULFERT LIED, OVERLEGE KNUD NICOLAYSEN OG OLAF RØMCKES MINNEFOND FOR DRAMMEN SYKEHUS STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about OVERLEGE ULFERT LIED, OVERLEGE KNUD NICOLAYSEN OG OLAF RØMCKES MINNEFOND FOR DRAMMEN SYKEHUS STI

Where is OVERLEGE ULFERT LIED, OVERLEGE KNUD NICOLAYSEN OG OLAF RØMCKES MINNEFOND FOR DRAMMEN SYKEHUS STI based?

OVERLEGE ULFERT LIED, OVERLEGE KNUD NICOLAYSEN OG OLAF RØMCKES MINNEFOND FOR DRAMMEN SYKEHUS STI has its business address in Drammen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.