BIZTRAC BETA
Rental and operating of own or leased real estate

ÅGEDAL HOLDING AS

Org. no. 989051342 Limited company (AS) Drammen Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 955,000
Operating profit NOK 287,000
Equity NOK 93.8m
Incorporated 2005
Share capital NOK 17.1m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ÅGEDAL HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 989051342. 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 17.1m, divided into 50 shares. The company's stated purpose is: “Investeringer i verdipapirer og fast eiendom. ”. The most recent filed accounts, for the 2025 financial year, show NOK 955,000 in revenue and NOK 287,000 in operating profit.

Key figures · 2025

Revenue
NOK 955,000
Operating profit
NOK 287,000
Equity
NOK 93.8m
Est. value
NOK 70.6m

Financial health · 2025

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

Who owns ÅGEDAL HOLDING AS?

NILS BJARTE ÅGEDAL
ÅGEDAL HOLDING AS
NOK 955,000 rev. · NOK 287,000 profit

ÅGEDAL HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ÅGEDAL HOLDING AS own?

ÅGEDAL HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about ÅGEDAL HOLDING AS

Who owns ÅGEDAL HOLDING AS?

NILS BJARTE ÅGEDAL is the largest registered owner, with 74.0%.

What is the revenue of ÅGEDAL HOLDING AS?

ÅGEDAL HOLDING AS had revenue of NOK 955,000 in 2025.

Where is ÅGEDAL HOLDING AS based?

ÅGEDAL HOLDING AS has its business address in Drammen.

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.