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

APOTEKER LUDVIG KREFTING LINAAE OG HUSTRU EMMAS LEGAT STI

Org. no. 977120292 Foundation (STI) Oslo Incorporated 1946 Active
Operating profit NOK −807,000
Equity NOK 40.6m
Incorporated 1946
Share capital NOK 5.0m

Signals

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

APOTEKER LUDVIG KREFTING LINAAE OG HUSTRU EMMAS LEGAT STI is registered as a foundation in Oslo, Oslo with organisation number 977120292. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 1946. Registered share capital is NOK 5.0m.

Former names: APOTEKER LUDVIG KREFTING LINAAE OG HUSTRU EMMAS LEGAT, Ä

Key figures · 2025

Operating profit
NOK −807,000
▼ −110 %
Equity
NOK 40.6m
▲ +12 %
Est. value
NOK 51.9m

Financial health · 2025

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

Who owns APOTEKER LUDVIG KREFTING LINAAE OG HUSTRU EMMAS LEGAT STI?

No shareholders are registered for APOTEKER LUDVIG KREFTING LINAAE OG HUSTRU EMMAS LEGAT STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does APOTEKER LUDVIG KREFTING LINAAE OG HUSTRU EMMAS LEGAT STI own?

APOTEKER LUDVIG KREFTING LINAAE OG HUSTRU EMMAS LEGAT STI holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about APOTEKER LUDVIG KREFTING LINAAE OG HUSTRU EMMAS LEGAT STI

Where is APOTEKER LUDVIG KREFTING LINAAE OG HUSTRU EMMAS LEGAT STI based?

APOTEKER LUDVIG KREFTING LINAAE OG HUSTRU EMMAS LEGAT STI has its business address in Oslo.

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.