BIZTRAC BETA
Rental and operating of own or leased real estate

ARILDS EIENDOM AS

Org. no. 946706523 Limited company (AS) Froland Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 3.2m
Operating profit NOK 606,000
Equity NOK 1.7m
Incorporated 1988
Share capital NOK 170,000

ARILDS EIENDOM AS is registered as a limited company in Froland, Agder with organisation number 946706523. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1988. Registered share capital is NOK 170,000, divided into 100 shares. The company's stated purpose is: “Utleie, kjøp og salg av fast eiendom, samt investering i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.2m in revenue and NOK 606,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.2m
Operating profit
NOK 606,000
Equity
NOK 1.7m
Est. value
NOK 2.5m

Financial health · 2024

Liquidity
0.78
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.7%
Weak
Equity as a share of total capital

Who owns ARILDS EIENDOM AS?

ARILD DALE KJEMPEKJENN
ARILDS EIENDOM AS
NOK 3.2m rev. · NOK 606,000 profit

ARILDS EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does ARILDS EIENDOM AS own?

ARILDS EIENDOM AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about ARILDS EIENDOM AS

Who owns ARILDS EIENDOM AS?

ARILD DALE KJEMPEKJENN is the largest registered owner, with 80.0%.

What is the revenue of ARILDS EIENDOM AS?

ARILDS EIENDOM AS had revenue of NOK 3.2m in 2024.

Who is the general manager of ARILDS EIENDOM AS?

Arild Dale Kjempekjenn is registered as general manager of ARILDS EIENDOM AS.

Where is ARILDS EIENDOM AS based?

ARILDS EIENDOM AS has its business address in Froland.

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.