biztrac. BETA
COMPANY REGISTER PROFILE
914764424 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of charities which distribute means themselves

STIFTELSEN VÅLERENGA FOTBALL SAMFUNN

Org. no. 914764424 Foundation (STI) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 6.1m
Operating profit NOK 12,000
Equity NOK 997,000
Incorporated 2014
Employees 9
Share capital NOK 100,000

STIFTELSEN VÅLERENGA FOTBALL SAMFUNN is registered as a foundation in Oslo, Oslo with organisation number 914764424. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 2014 and has 9 registered employees. Registered share capital is NOK 100,000. The most recent filed accounts, for the 2025 financial year, show NOK 6.1m in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.1m
▲ +3 %
Operating profit
NOK 12,000
▲ +102 %
Equity
NOK 997,000
▲ +10 %
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
2.89
Very good
Current assets ÷ current liabilities
Profitability
5.7%
Weak
Return on total assets
Solidity
65.4%
Very good
Equity as a share of total capital

Who owns STIFTELSEN VÅLERENGA FOTBALL SAMFUNN?

No shareholders are registered for STIFTELSEN VÅLERENGA FOTBALL SAMFUNN in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STIFTELSEN VÅLERENGA FOTBALL SAMFUNN

What is the revenue of STIFTELSEN VÅLERENGA FOTBALL SAMFUNN?

STIFTELSEN VÅLERENGA FOTBALL SAMFUNN had revenue of NOK 6.1m in 2025.

Who is the general manager of STIFTELSEN VÅLERENGA FOTBALL SAMFUNN?

Jannicke Aas is registered as general manager of STIFTELSEN VÅLERENGA FOTBALL SAMFUNN.

Where is STIFTELSEN VÅLERENGA FOTBALL SAMFUNN based?

STIFTELSEN VÅLERENGA FOTBALL SAMFUNN has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.