BIZTRAC BETA
COMPANY REGISTER PROFILE
924927119 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

AABØE EIENDOM AS

Org. no. 924927119 Limited company (AS) Kragerø Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 4.9m
Operating profit NOK 3.1m
Equity NOK 12.4m
Incorporated 2020
Share capital NOK 54,000

AABØE EIENDOM AS is registered as a limited company in Kragerø, Telemark with organisation number 924927119. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 54,000, divided into 90 shares. The company's stated purpose is: “Eie, drift og utleie av fast eiendom, eie aksjer i andre selskap, investering i aksjer og andre verdipapirer, samt annen virksomhet som står i nær sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.9m in revenue and NOK 3.1m in operating profit.

Former names: NYE AABØE EIENDOM AS

Key figures · 2025

Revenue
NOK 4.9m
▲ +7 %
Operating profit
NOK 3.1m
▲ +5 %
Equity
NOK 12.4m
▼ −10 %
Est. value
NOK 12.1m

Financial health · 2025

Liquidity
0.51
Weak
Current assets ÷ current liabilities
Profitability
5.7%
Weak
Return on total assets
Solidity
22.2%
Good
Equity as a share of total capital

Who owns AABØE EIENDOM AS?

AABØE EIENDOM AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about AABØE EIENDOM AS

Who owns AABØE EIENDOM AS?

JSAA HOLDING AS is the largest registered owner, with 32.2%.

What is the revenue of AABØE EIENDOM AS?

AABØE EIENDOM AS had revenue of NOK 4.9m in 2025.

Who is the general manager of AABØE EIENDOM AS?

Geir Kristian Aabøe is registered as general manager of AABØE EIENDOM AS.

Where is AABØE EIENDOM AS based?

AABØE EIENDOM AS has its business address in Sannidal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.