BIZTRAC BETA
COMPANY REGISTER PROFILE
977154502 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Holiday and other short-stay accommodation

SKJØRSANDSTIFTELSEN

Org. no. 977154502 Foundation (STI) Askøy Incorporated 1979 Active
Ownership graph ↗
Operating profit NOK −78,000
Equity NOK 1.1m
Incorporated 1979
Share capital NOK 4.2m

Signals

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

SKJØRSANDSTIFTELSEN is registered as a foundation in Askøy, Vestland with organisation number 977154502. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 1979. Registered share capital is NOK 4.2m.

Former names: SKJØRSAND LEIRSTED

Key figures · 2025

Operating profit
NOK −78,000
Equity
NOK 1.1m
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns SKJØRSANDSTIFTELSEN?

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

Frequently asked questions about SKJØRSANDSTIFTELSEN

Who is the general manager of SKJØRSANDSTIFTELSEN?

Are Matthiesen is registered as general manager of SKJØRSANDSTIFTELSEN.

Where is SKJØRSANDSTIFTELSEN based?

SKJØRSANDSTIFTELSEN has its business address in Erdal.

Property

Business address c/o Are Matthiesen Vardane 47, 5306 Erdal
Cadastral unit 4627-4/756/0/0
Building Enebolig · 2 units

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