BIZTRAC BETA
Rental and operating of own or leased real estate

STORHALLE INVEST AS

Org. no. 989121561 Limited company (AS) Lier Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 96,000
Operating profit NOK −116,000
Equity NOK 22.9m
Incorporated 2005
Share capital NOK 100,000

Signals

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

STORHALLE INVEST AS is registered as a limited company in Lier, Buskerud with organisation number 989121561. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Investerings- og holdingsvirksomhet samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 96,000 in revenue and NOK −116,000 in operating profit.

Key figures · 2025

Revenue
NOK 96,000
Operating profit
NOK −116,000
Equity
NOK 22.9m
Est. value
NOK 25.4m

Financial health · 2025

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

Who owns STORHALLE INVEST AS?

ERIK WØLLO
STORHALLE INVEST AS
NOK 96,000 rev. · NOK −116,000 profit

STORHALLE INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STORHALLE INVEST AS own?

STORHALLE INVEST AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about STORHALLE INVEST AS

Who owns STORHALLE INVEST AS?

ERIK WØLLO is the largest registered owner, with 100.0%.

What is the revenue of STORHALLE INVEST AS?

STORHALLE INVEST AS had revenue of NOK 96,000 in 2025.

Where is STORHALLE INVEST AS based?

STORHALLE INVEST AS has its business address in Gullaug.

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.