BIZTRAC BETA
Rental and operating of own or leased real estate

AVEN EIENDOM KRAGERØ AS

Org. no. 919785497 Limited company (AS) Kragerø Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 168,000
Operating profit NOK 20,000
Equity NOK 628,000
Incorporated 2017
Share capital NOK 500,000

AVEN EIENDOM KRAGERØ AS is registered as a limited company in Kragerø, Telemark with organisation number 919785497. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Investere i real- og finansobjekter samt annet som er naturlig i den forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 168,000 in revenue and NOK 20,000 in operating profit.

Key figures · 2025

Revenue
NOK 168,000
Operating profit
NOK 20,000
Equity
NOK 628,000
Est. value
NOK 471,000

Financial health · 2025

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.8%
Good
Equity as a share of total capital

Who owns AVEN EIENDOM KRAGERØ AS?

AVEN HOLDING KRAGERØ AS
AVEN EIENDOM KRAGERØ AS
NOK 168,000 rev. · NOK 20,000 profit

AVEN EIENDOM KRAGERØ AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AVEN EIENDOM KRAGERØ AS

Who owns AVEN EIENDOM KRAGERØ AS?

AVEN HOLDING KRAGERØ AS is the largest registered owner, with 60.0%.

What is the revenue of AVEN EIENDOM KRAGERØ AS?

AVEN EIENDOM KRAGERØ AS had revenue of NOK 168,000 in 2025.

Who is the general manager of AVEN EIENDOM KRAGERØ AS?

Stig Yngve Knutsen is registered as general manager of AVEN EIENDOM KRAGERØ AS.

Where is AVEN EIENDOM KRAGERØ AS based?

AVEN EIENDOM KRAGERØ AS has its business address in Kragerø.

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.