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

ROLAND OG MARIE PETERSENS LEGAT STI

Org. no. 987394838 Foundation (STI) Stavanger Incorporated 1918 Active
Ownership graph ↗
Operating profit NOK −28,000
Equity NOK 1.2m
Incorporated 1918
Share capital NOK 200,000

Signals

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

ROLAND OG MARIE PETERSENS LEGAT STI is registered as a foundation in Stavanger, Rogaland with organisation number 987394838. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 1918. Registered share capital is NOK 200,000.

Key figures · 2025

Operating profit
NOK −28,000
Equity
NOK 1.2m
Est. value
NOK 838,000

Financial health · 2025

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

Who owns ROLAND OG MARIE PETERSENS LEGAT STI?

No shareholders are registered for ROLAND OG MARIE PETERSENS LEGAT STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ROLAND OG MARIE PETERSENS LEGAT STI

Where is ROLAND OG MARIE PETERSENS LEGAT STI based?

ROLAND OG MARIE PETERSENS LEGAT STI has its business address in Stavanger.

Property

Business address Wessels gate 51, 4008 Stavanger
Cadastral unit 1103-58/308/0/0
Building Annet sykehjem · 1 unit

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