BIZTRAC BETA
Development of building projects

ÅNESØYAN STORHALL AS

Org. no. 919824441 Limited company (AS) Heim Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 3.3m
Operating profit NOK 744,000
Equity NOK 28,000
Incorporated 2017
Share capital NOK 30,000

ÅNESØYAN STORHALL AS is registered as a limited company in Heim, Trøndelag with organisation number 919824441. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Å legge til rette for kultur og idrettsaktivitet gjennom utbygging og drift av anlegg for slikt formål. Selskapet er uten eget økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.3m in revenue and NOK 744,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.3m
Operating profit
NOK 744,000
Equity
NOK 28,000
Est. value
NOK 1.1m

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ÅNESØYAN STORHALL AS?

KIL/HEMNE FOTBALL
ÅNESØYAN STORHALL AS
NOK 3.3m rev. · NOK 744,000 profit

ÅNESØYAN STORHALL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ÅNESØYAN STORHALL AS

Who owns ÅNESØYAN STORHALL AS?

KIL/HEMNE FOTBALL is the largest registered owner, with 80.0%.

What is the revenue of ÅNESØYAN STORHALL AS?

ÅNESØYAN STORHALL AS had revenue of NOK 3.3m in 2024.

Who is the general manager of ÅNESØYAN STORHALL AS?

Erik Snekvik is registered as general manager of ÅNESØYAN STORHALL AS.

Where is ÅNESØYAN STORHALL AS based?

ÅNESØYAN STORHALL AS has its business address in Kyrksæterøra.

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.