BIZTRAC BETA
COMPANY REGISTER PROFILE
856566102 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Operation of sports facilities

STIFTELSEN LEIKVANG IDRETTSPARK

Org. no. 856566102 Foundation (STI) Bergen Incorporated 1990 Active
Ownership graph ↗
Operating profit NOK −65,000
Equity NOK 1.0m
Incorporated 1990
Share capital NOK 650,000

Signals

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

STIFTELSEN LEIKVANG IDRETTSPARK is registered as a foundation in Bergen, Vestland with organisation number 856566102. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 1990. Registered share capital is NOK 650,000.

Former names: STIFTELSEN BERGEN IDRETTSPARK LEIKVANG

Key figures · 2025

Operating profit
NOK −65,000
Equity
NOK 1.0m
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns STIFTELSEN LEIKVANG IDRETTSPARK?

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

Frequently asked questions about STIFTELSEN LEIKVANG IDRETTSPARK

Where is STIFTELSEN LEIKVANG IDRETTSPARK based?

STIFTELSEN LEIKVANG IDRETTSPARK has its business address in Breistein.

Property

Business address Leikvangvegen 31, 5111 Breistein
Cadastral unit 4601-170/222/0/0
Building Tribune og idrettsgarderobe · 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.