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

FRELSESARMEENS STORBYSTIFTELSE

Org. no. 993194204 Foundation (STI) Oslo Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −2.5m
Equity NOK 49.8m
Incorporated 2008
Share capital NOK 1.5m

Signals

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

FRELSESARMEENS STORBYSTIFTELSE is registered as a foundation in Oslo, Oslo with organisation number 993194204. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 2008. Registered share capital is NOK 1.5m.

Former names: FRELSESARMEENS STORBYLEGAT STI

Key figures · 2025

Operating profit
NOK −2.5m
Equity
NOK 49.8m
Est. value
NOK 42.8m

Financial health · 2025

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

Who owns FRELSESARMEENS STORBYSTIFTELSE?

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

Frequently asked questions about FRELSESARMEENS STORBYSTIFTELSE

Where is FRELSESARMEENS STORBYSTIFTELSE based?

FRELSESARMEENS STORBYSTIFTELSE has its business address in Oslo.

Property

Business address Ensjøveien 23A, 0661 Oslo
Cadastral unit 301-133/42/0/0
Building Annen kontorbygning · 6 units

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