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

LEGATA I VÅGÅ KOMMUNE STI

Org. no. 892668892 Foundation (STI) Vågå Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −36,000
Equity NOK 1.5m
Incorporated 2008
Share capital NOK 1.1m

Signals

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

LEGATA I VÅGÅ KOMMUNE STI is registered as a foundation in Vågå, Innlandet with organisation number 892668892. 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.1m.

Former names: MAGNA KRISTINE OG EINAR WILHELM BALLESTADS STIFTELSE

Key figures · 2025

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

Financial health · 2025

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

Who owns LEGATA I VÅGÅ KOMMUNE STI?

No shareholders are registered for LEGATA I VÅGÅ KOMMUNE STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LEGATA I VÅGÅ KOMMUNE STI

Where is LEGATA I VÅGÅ KOMMUNE STI based?

LEGATA I VÅGÅ KOMMUNE STI has its business address in Vågå.

Property

Business address Edvard Storms veg 2, 2680 Vågå
Cadastral unit 3435-66/276/0/0
Building Kontor- og administrasjonsbygning, rådhus · 2 units

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