biztrac. BETA
COMPANY REGISTER PROFILE
926732625 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

KEEN EIENDOM AS

Org. no. 926732625 Limited company (AS) Stavanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 982,000
Operating profit NOK 736,000
Equity NOK 592,000
Incorporated 2021
Share capital NOK 30,000

KEEN EIENDOM AS is registered as a limited company in Stavanger, Rogaland with organisation number 926732625. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, utvikling og salg av fast eiendom til boligformål, samt alt som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 982,000 in revenue and NOK 736,000 in operating profit.

Former names: FØNIKS BOLIG AS

Key figures · 2025

Revenue
NOK 982,000
▲ +47 %
Operating profit
NOK 736,000
▲ +54 %
Equity
NOK 592,000
▲ +122 %
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
175.39
Very good
Current assets ÷ current liabilities
Profitability
10.8%
Good
Return on total assets
Solidity
23.0%
Good
Equity as a share of total capital

Who owns KEEN EIENDOM AS?

KEEN EIENDOM AS
NOK 982,000 rev. · NOK 736,000 profit

KEEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KEEN EIENDOM AS own?

KEEN EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KEEN EIENDOM AS

Who owns KEEN EIENDOM AS?

VIRGINIA EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of KEEN EIENDOM AS?

KEEN EIENDOM AS had revenue of NOK 982,000 in 2025.

Where is KEEN EIENDOM AS based?

KEEN EIENDOM AS has its business address in Stavanger.

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.