BIZTRAC BETA
Other real estate activities on a fee or contract basis

NØRVEBANA AS

Org. no. 914633532 Limited company (AS) Ålesund Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 445,000
Operating profit NOK 16,000
Equity NOK 1.3m
Incorporated 2014
Share capital NOK 1.0m

NØRVEBANA AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 914633532. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2014. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Inngå festeavtale med Ålesund kommune på minimum 30 år for Nørvabanens arealer, eie, vedlikeholde og drive Nørvebana Kunstgressbane for å øke tilbudet til breddefotballen for barn og ungdom i bynære områder. Selskapet er uten eget økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 445,000 in revenue and NOK 16,000 in operating profit.

Key figures · 2025

Revenue
NOK 445,000
Operating profit
NOK 16,000
Equity
NOK 1.3m
Est. value
NOK 933,000

Financial health · 2025

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

Who owns NØRVEBANA AS?

GUARD SPORTSKLUBBEN
NØRVEBANA AS
NOK 445,000 rev. · NOK 16,000 profit

NØRVEBANA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NØRVEBANA AS

Who owns NØRVEBANA AS?

GUARD SPORTSKLUBBEN is the largest registered owner, with 100.0%.

What is the revenue of NØRVEBANA AS?

NØRVEBANA AS had revenue of NOK 445,000 in 2025.

Who is the general manager of NØRVEBANA AS?

Foad Saidali is registered as general manager of NØRVEBANA AS.

Where is NØRVEBANA AS based?

NØRVEBANA AS has its business address in Ålesund.

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

Report a problem

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