biztrac. BETA
COMPANY REGISTER PROFILE
984358946 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

PRIMHOVDA SØR AS

Org. no. 984358946 Limited company (AS) Ål Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK −126,000
Equity NOK 5.1m
Incorporated 2002
Share capital NOK 1.5m

Signals

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

PRIMHOVDA SØR AS is registered as a limited company in Ål, Buskerud with organisation number 984358946. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2002. Registered share capital is NOK 1.5m, divided into 14861 shares. The company's stated purpose is: “Utvikling, prosjektering, utbygging og drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK −126,000 in operating profit.

Former names: ØVRE-ÅLSÅSEN UTVIKLING AS

Key figures · 2025

Revenue
NOK 4.6m
▼ −25 %
Operating profit
NOK −126,000
▼ −107 %
Equity
NOK 5.1m
▼ −4 %
Est. value
NOK 4.4m

Financial health · 2025

Liquidity
15.38
Very good
Current assets ÷ current liabilities
Profitability
-1.0%
Not satisfactory
Return on total assets
Solidity
40.9%
Very good
Equity as a share of total capital

Who owns PRIMHOVDA SØR AS?

PRIMHOVDA SØR AS has 14 registered shareholders:

All shareholders and roles →

Which companies does PRIMHOVDA SØR AS own?

PRIMHOVDA SØR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PRIMHOVDA SØR AS

Who owns PRIMHOVDA SØR AS?

Olav Andres Ådnegard is the largest registered owner, with 19.7%.

What is the revenue of PRIMHOVDA SØR AS?

PRIMHOVDA SØR AS had revenue of NOK 4.6m in 2025.

Where is PRIMHOVDA SØR AS based?

PRIMHOVDA SØR AS has its business address in Ål.

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.